Connect your agent

Add the URL below to your AI client as a custom MCP connector. The client runs the OAuth login and consent flow in your browser automatically — no install, no token to paste, and tokens refresh on their own.

Remote endpoint

https://api.zippendo.com/mcp

Because the server supports dynamic client registration, a compliant client needs only the URL — no client ID, no client secret, no pasted token. On first connect it discovers the login, registers itself, and opens your browser so you can sign in and approve access. See Authentication.

Jump to your client

Claude Code

Claude Desktop

Claude (web)

Cursor

VS Code

Windsurf

ChatGPT

Codex CLI

Gemini CLI

Any MCP client

Claude Code

Add the server with the CLI, then authenticate from inside a session.

Add the server

claude mcp add --transport http zippendo https://api.zippendo.com/mcp

Use --scope user to make it available in every project, or --scope project to commit it to the repo’s .mcp.json for your team (default is local, just for you in the current project).

Authenticate

Start Claude Code and run /mcp, select zippendo, and choose Authenticate. Your browser opens the Zippendo login and consent screen. Approve, and you’re connected. Re-run /mcp any time to check status or re-authenticate.

To share the server with your team, commit a project .mcp.json:

.mcp.json

{
  "mcpServers": {
    "zippendo": {
      "type": "http",
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

Manage the connection with claude mcp list, claude mcp get zippendo, and claude mcp remove zippendo.

Claude Desktop

Open Connectors

Go to Settings → Connectors and click Add custom connector.

Add the URL

Give it a name (e.g. Zippendo) and enter https://api.zippendo.com/mcp, then click Add.

Connect

Click Connect to open the browser OAuth flow, sign in, and approve access.

Custom connectors are available on Free, Pro, Max, Team, and Enterprise. Free plans allow one custom connector. On Team/Enterprise, an Owner adds the connector and each member connects individually.

Claude on the web

Same account, same flow as Claude Desktop.

Individual (Free/Pro/Max): Settings → Connectors → Add custom connector → enter a name and https://api.zippendo.com/mcp → Add → Connect.
Team / Enterprise: an Owner adds it once under Organization settings → Connectors → Add → Custom. Members then open Settings → Connectors, find the connector, and click Connect — access is scoped to each member individually.

Cursor

Add it in the UI or with a config file.

Open MCP settings

Cursor Settings → Tools & MCP → New MCP Server. This opens your mcp.json.

Add the server

mcp.json

{
  "mcpServers": {
    "zippendo": {
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

Global config lives at ~/.cursor/mcp.json; per-project config at .cursor/mcp.json.

A Login / Needs login control appears next to the server. Click it to run the browser OAuth flow.

One-click install: Add Zippendo to Cursor. Cursor shows an approval dialog and writes the entry for you.

VS Code (GitHub Copilot)

Requires VS Code 1.102+ with GitHub Copilot; use tools from Copilot Chat in Agent mode.

Add the server

Command Palette → MCP: Add Server → HTTP → paste https://api.zippendo.com/mcp → choose Workspace (writes .vscode/mcp.json) or Global.

Authenticate

An Auth action appears above the server entry in mcp.json; complete the browser sign-in.

The workspace config uses a top-level servers key (not mcpServers):

.vscode/mcp.json

{
  "servers": {
    "zippendo": {
      "type": "http",
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json (Cascade → MCP servers → edit raw config).

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "zippendo": {
      "serverUrl": "https://api.zippendo.com/mcp"
    }
  }
}

Windsurf uses serverUrl (not url) for Streamable HTTP servers. OAuth is supported, but if the browser login doesn’t trigger, update Windsurf to the latest version.

ChatGPT

Custom MCP connectors are added through Developer Mode (web UI only — no config file).

Enable Developer Mode

Settings → Connectors → Advanced → Developer Mode.

Add the connector

Back in Connectors, add a custom connector with the URL https://api.zippendo.com/mcp. A popup prompts you to sign in (OAuth) on first connect.

Developer Mode is beta and available on Plus, Pro, Business, Enterprise, and Edu. Full tool-calling (write actions like creating a shipment) is limited to Business, Enterprise, and Edu workspaces — Plus and Pro are effectively read-only. Write actions require per-action confirmation. Exact menu wording and availability may change.

OpenAI Codex CLI

Use a recent Codex CLI (older builds were stdio-only). Add via config or the CLI.

~/.codex/config.toml

[mcp_servers.zippendo]
url = "https://api.zippendo.com/mcp"

CLI

codex mcp add zippendo --url https://api.zippendo.com/mcp
codex mcp login zippendo   # opens the browser OAuth flow

If your Codex version lacks --url / codex mcp login, update to the latest Codex CLI.

Gemini CLI

Edit ~/.gemini/settings.json. Streamable HTTP servers use the httpUrl field.

~/.gemini/settings.json

{
  "mcpServers": {
    "zippendo": {
      "httpUrl": "https://api.zippendo.com/mcp"
    }
  }
}

Gemini CLI auto-discovers OAuth. In a session, run /mcp auth (or /mcp to see servers needing auth) to trigger the browser login.

Any other MCP client

Most clients accept the canonical remote shape — just the URL:

{
  "mcpServers": {
    "zippendo": {
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

If your client implements the MCP authorization spec, it will discover the login and run OAuth for you.

Troubleshooting

The agent can't see a tool it needs

Tools are filtered by the scopes you approved. Reconnect and grant the missing scope on the consent screen (for example, add write:shipments to create shipments). See Tools & scopes.

It's acting on the wrong organization

Each connection is bound to one organization. Disconnect and reconnect, choosing the correct org on the consent screen. See choosing an organization.

A config with only a url is rejected

Some clients require an explicit transport type. Add "type": "http" next to the url (Claude Code, VS Code), or use that client’s HTTP option when adding the server.

Remote endpoint

​Jump to your client

Claude Code

Claude Desktop

Claude (web)

Cursor

VS Code

Windsurf

ChatGPT

Codex CLI

Gemini CLI

Any MCP client

​Claude Code

​Claude Desktop

​Claude on the web

​Cursor

​VS Code (GitHub Copilot)

​Windsurf

​ChatGPT

​OpenAI Codex CLI

​Gemini CLI

​Any other MCP client

​Troubleshooting

Jump to your client

Claude Code

Claude Desktop

Claude on the web

Cursor

VS Code (GitHub Copilot)

Windsurf

ChatGPT

OpenAI Codex CLI

Gemini CLI

Any other MCP client

Troubleshooting