Connect your agent
The server lives at a single URL:
https://mcp.zonio.tech/mcp
Add it to your client and it opens a Zonio page in your browser: sign in (or create an account), check which app is asking, and click Approve. The client stores the token and refreshes it on its own. There is no key to copy.
Claude.ai and Claude Desktop
- Open Add custom connector in Claude → (sign in to Claude if asked).
- Name it Zonio and paste
https://mcp.zonio.tech/mcpas the server URL. Leave Advanced settings empty and click Add. - Zonio now appears in your connectors. Click Connect: adding it doesn't sign you in on its own.
- A Zonio page opens. Sign in or create a free account, check that it says Recognised app: Claude, and click Approve. You're sent back to Claude.
Start a new chat and ask "What's the zoning of parcel 126101_1.0018.AR_1.100/1?" Claude asks permission the first time it calls a Zonio tool. The connector also works in Claude Desktop and the mobile apps once it's connected on claude.ai.
On a Team or Enterprise plan, an Owner may need to add the connector for the organization first; each member then clicks Connect and signs in with their own Zonio account.
Claude Code
claude mcp add --transport http zonio https://mcp.zonio.tech/mcpThen run /mcp, pick zonio and choose Authenticate. Add --scope project to share the server with your team through .mcp.json; each person signs in with their own account:
{
"mcpServers": {
"zonio": { "type": "http", "url": "https://mcp.zonio.tech/mcp" }
}
}Cursor
{
"mcpServers": {
"zonio": { "url": "https://mcp.zonio.tech/mcp" }
}
}Cursor shows Needs login next to the server; click it to sign in.
VS Code (GitHub Copilot)
{
"servers": {
"zonio": { "type": "http", "url": "https://mcp.zonio.tech/mcp" }
}
}Start the server and VS Code asks you to sign in.
Clients without remote-server support
The mcp-remote bridge exposes the server over stdio and runs the sign-in in your browser:
{
"mcpServers": {
"zonio": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.zonio.tech/mcp"] }
}
}Your own agent
Connect any MCP client over Streamable HTTP to https://mcp.zonio.tech/mcp. The server follows the MCP authorization spec: a 401 points to /.well-known/oauth-protected-resource, clients register themselves dynamically, and tokens are sent as Authorization: Bearer <token>.
Limit what the agent can do
Every signed-in account sees every tool. The project tools change the user's projects; all others are read-only. To expose fewer tools to a model, use your client's allowlist, for example Claude Code permissions.
Verify the connection
Ask your agent: "Use Zonio to tell me which layers are available." It should call list_layers and list ~45 layers. A 401 means the client hasn't signed in yet or its token was revoked; reconnect and approve again. If it can't see the tools, check that your client supports Streamable HTTP.