Koskamo

Zippendo MCP

An official remote MCP server provided by Zippendo that allows AI agents to manage shipping operations. It enables users to create, split, send, and track shipments, read orders, manage carriers and addresses, and handle webhooks and automations through natural language interactions, leveraging the same permissions and API infrastructure as the main Zippendo application.

Visit Zippendo ApS

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Zippendo MCP logo, by Zippendo ApSVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Zippendo ApS
You need:A Zippendo account with access to at least one organization.An MCP client that supports remote connectors.
MCP endpoint (Streamable HTTP)
https://api.zippendo.com/mcp
Vendor documentation

What you can do with it

  • Create, split, send, and track shipments
  • Read orders imported from order channels
  • List connected carriers and look up service points
  • Manage sender addresses and shipping rules

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: com.zippendo/mcp@1.0.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
512 ms
95th percentile latency
512 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 512 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http zippendo-mcp https://api.zippendo.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add zippendo-mcp --url https://api.zippendo.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable zippendo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "zippendo-mcp": {
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "zippendo-mcp": {
      "type": "streamableHttp",
      "url": "https://api.zippendo.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start zippendo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "zippendo-mcp": {
      "type": "http",
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http zippendo-mcp https://api.zippendo.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "zippendo-mcp": {
      "url": "https://api.zippendo.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "zippendo-mcp": {
      "serverUrl": "https://api.zippendo.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Zippendo MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 1,056

Do you run Zippendo MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing