customs.dog MCP server

Connect your AI assistant to customs.dog — your pets' travel documents and border trip-readiness checks. Ask "is Stormey cleared to fly to Mexico next month?" and get a cleared / caution / blocked verdict with the exact paperwork that's missing.

customs.dog is a hosted remote MCP server. This package is a thin launcher that bridges a local stdio MCP client (Claude Desktop, Cursor, etc.) to it.

Tools

Setup

1. Get an API key — sign in at customs.dog → Settings → API keys. One key = one household (read-only).
2. Add it to your MCP client.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "customs-dog": {
      "command": "npx",
      "args": ["-y", "@capitalthought/customs-dog-mcp"],
      "env": { "CUSTOMS_DOG_API_KEY": "cdk_your_key_here" }
    }
  }
}

Any client that speaks remote MCP

Point it straight at the endpoint — no launcher needed:

https://customs.dog/mcp
Authorization: Bearer cdk_your_key_here

How it works

This package shells out to mcp-remote, pointing it at https://customs.dog/mcp (streamable-HTTP, JSON-RPC 2.0) with your key as a Bearer header. Override the URL with CUSTOMS_DOG_MCP_URL if needed.

Links

• 🌐 customs.dog · 🤖 Agent contract · 📇 MCP server card · 📄 llms.txt

customs.dog is a preparation assistant operated by Capital Thought, LLC (Texas) — not legal, veterinary, or immigration advice. Only the border authority decides admission. MIT licensed.