Connect your agent

Connect your AI tool to Zippendo so it can work with your shipments, orders and carriers for you. Add the URL below to the tool as a custom MCP connector. The tool opens the Zippendo sign-in in your browser and keeps the connection fresh by itself: nothing to install and no token to paste.

Connector URL

https://api.zippendo.com/mcp

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

Set it up from the Zippendo app

The app walks you through the same steps for your tool:

Open the MCP card

Go to Apps & integrations → Catalog, find MCP (AI agents) and click Connect. The Connect an AI agent window opens.

Choose agent

Pick your AI tool. Any MCP client works; the list shows the ones with named instructions.

Add connector

Follow the steps for your tool. The Connector URL has a Copy button. When you have added it, click I’ve added it.

Approve access

Finish the sign-in your tool opened and approve the organization and permissions. The window updates by itself as soon as the connection is made. Click Done.

Every connected agent then appears on the MCP (AI agents) card with when it was last used and how many permissions it has. Click Disconnect to remove its access, or Connect another to add one more. The steps for each tool are also below.

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 (the default is local: just you, in the current project).

Authenticate

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

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

Name it Zippendo, enter https://api.zippendo.com/mcp and click Add.

Connect

Click Connect to open the browser sign-in, then approve the organization and permissions.

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

Claude on the web

Same account, same steps as Claude Desktop.

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

Cursor

Add it in the settings or with a config file.

Open MCP settings

Open 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"
    }
  }
}

The global config lives at ~/.cursor/mcp.json, the per-project config at .cursor/mcp.json.

A Login control appears next to the server. Click it to run the browser sign-in.

One-click install: Add Zippendo to Cursor. Cursor asks you to approve and writes the entry for you.

VS Code (GitHub Copilot)

Needs VS Code 1.102 or later with GitHub Copilot. Use the tools from Copilot Chat in Agent mode.

Add the server

Command Palette → MCP: Add Server → HTTP, paste https://api.zippendo.com/mcp, then 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 VS Code 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 sign-in doesn’t open, update Windsurf to the latest version.

ChatGPT

Custom MCP connectors are added through Developer Mode, in the web version only (no config file).

Enable Developer Mode

Turn on Settings → Connectors → Advanced → Developer Mode.

Add the connector

Back in Connectors, add a custom connector with the URL https://api.zippendo.com/mcp. ChatGPT asks you to sign in the first time you connect.

Developer Mode is in beta on Plus, Pro, Business, Enterprise and Edu. Full tool calling (write actions such as creating a shipment) is limited to Business, Enterprise and Edu. Plus and Pro are effectively read-only. Write actions need a confirmation each time. ChatGPT may change its menu names and availability.

OpenAI Codex CLI

Use a recent Codex CLI (older versions only supported local servers). Add the server in the config file or with 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 sign-in

If your Codex version has no --url or 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 finds the OAuth sign-in by itself. In a session, run /mcp auth (or /mcp to see which servers need it) to open the browser sign-in.

Any other MCP client

Most clients accept the standard remote setup, with just the URL:

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

If your client follows the MCP authorization spec, it finds the sign-in and runs OAuth for you. Then approve the organization and permissions on the Zippendo sign-in page it opens.

Troubleshooting

The agent can't see a tool it needs

Tools are filtered by the permissions you approved. Connect again and grant the missing permission on the consent screen (for example write:shipments to create shipments). See Tools & scopes.

It's working in the wrong organization

Each connection belongs to one organization. Disconnect, connect again, and choose the right organization on the consent screen. See Authentication.

A config with only a url is rejected

Some clients need the transport type spelled out. Add "type": "http" next to the url (Claude Code, VS Code), or use that client’s HTTP option when you add the server.

Overview

SDKs

MCP server

System

Tokens

Orgs

Brands

Addresses

Carriers

Rules

Quotes

Shipments

Orders

Order Channels

Carrier Catalog

Billing

Webhooks

Connect your agent

Connector URL

Set it up from the Zippendo app

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

Connector URL

​Set it up from the Zippendo app

​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

Set it up from the Zippendo app

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