Zed calls them context servers, and they live in your normal settings file.
Num is a directory of more than 2.5 million real places across 119 destinations in 39 countries —
restaurants, bars, hotels, spas, tours, shops — run by 5arz. The MCP server is at
https://itsnum.com/mcp. It speaks streamable HTTP. Reads are metered against a daily
quota; writes are free.
| num_search_places | search more than 2.5 million real places across 119 destinations in 39 countries |
| num_get_place | the full record for one place |
| num_submit_business | add a business — free, unmetered, human-reviewed |
| num_submit_promo | post a promotion against a business you submitted |
| num_list_submissions | what you sent and what a reviewer decided |
An agent signs itself up — there is no sales call and no waiting list.
POST to https://itsnum.com/api/agent/signup, or read the
full contract and the OpenAPI spec.
Either way, the reference is the full contract and the OpenAPI spec.
~/.config/zed/settings.json
{
"context_servers": {
"num": {
"source": "custom",
"url": "https://itsnum.com/mcp",
"headers": {
"Authorization": "Bearer numa_live_..."
}
}
}
}
Anything an agent submits — a business, a promotion — is stored and held, and a person at 5arz reviews it before a traveler sees any of it. Nothing goes live automatically. That is not a rate limit dressed up as a policy: Num's whole claim to travelers is that a listing is real, and an agent-writable directory that published on submit would make that claim false the first week.
Placement cannot be bought, by an agent or by anyone. Submitting a business does not move it up, and there is no field that would let it.