Connect via MCP

Server URL

https://api.zillo.app/mcp

OAuth 2.0 + PKCE. The first request triggers a consent flow on dashboard.zillo.app/oauth/authorize where you pick a store and the scopes the client should have.

Claude

Works in claude.ai on the web and in the Claude desktop app.

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Name it Zillo, paste the server URL https://api.zillo.app/mcp, and continue.
4. Sign in to Zillo, choose which store to grant access to, and pick the scopes.
5. You're back in Claude. Try “List my recent orders.”

Claude's connectors UI moves occasionally — if the menu has changed, the canonical path is Anthropic's custom connectors guide.

Cursor

Cursor reads MCP servers from a JSON config — either the global one at ~/.cursor/mcp.json or a per-project .cursor/mcp.json at the workspace root.

{
  "mcpServers": {
    "zillo": {
      "url": "https://api.zillo.app/mcp"
    }
  }
}

1. Open Settings → Cursor Settings → MCP.
2. Click Add new MCP server and paste the JSON above (or edit ~/.cursor/mcp.json directly).
3. Cursor opens the Zillo consent page in your browser the first time it calls a tool. Approve and you're live.

Zed

Zed exposes MCP via its context servers setting. Add the Zillo entry to your settings.json:

{
  "context_servers": {
    "zillo": {
      "source": "custom",
      "command": null,
      "url": "https://api.zillo.app/mcp"
    }
  }
}

1. Open the command palette (cmd-shift-p / ctrl-shift-p) → run zed: open settings.
2. Paste the snippet above into your settings.json.
3. Restart Zed's assistant panel. The first tool call kicks off the Zillo consent flow.

Continue

Continue lives in VS Code / JetBrains and reads MCP servers from ~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "zillo",
      "transport": {
        "type": "streamableHttp",
        "url": "https://api.zillo.app/mcp"
      }
    }
  ]
}

1. Open the Continue panel → click the gear → choose Edit config.json.
2. Paste the snippet above (merge with any existing keys).
3. Save the file. Continue picks the change up on the next prompt and opens the Zillo consent page when it first calls a Zillo tool.

Goose

Goose (the Block-built MCP agent) registers servers as Extensions. Use the CLI:

goose configure
# → Add Extension
# → Remote Extension (Streamable HTTP)
# Name:  zillo
# URL:   https://api.zillo.app/mcp

Or edit ~/.config/goose/config.yaml directly:

extensions:
  zillo:
    type: streamable_http
    uri: https://api.zillo.app/mcp
    enabled: true

Start a session with goose session; the first Zillo tool call opens the consent page in your browser.

Other MCP clients

Any client that speaks the MCP Streamable HTTP transport plus OAuth 2.0 + PKCE works. Point it at https://api.zillo.app/mcp; the client will read https://api.zillo.app/.well-known/oauth-authorization-server for the auth endpoints automatically.

New client? If it speaks the MCP spec, it works — open an issue with the connection details and we'll add it here.

Try it

Once connected, prompt the AI: “List my recent orders”, “Redeem this gift card by $15”, or “Summarise this week's revenue”.

Scopes & tool surface

Tools are scoped by what you grant at install time — read-only by default, with explicit opt-in for write operations like redeem_gift_card. See Available tools for the full list and their required scopes.

Revoking access

OAuth tokens minted for an MCP install appear under Developers → API keys alongside your API keys. Revoke from there — the client immediately stops being able to act on your behalf.