Use CDXZipStream right inside Claude
Connect Claude to CDXZipStream's geographic tools with a single URL. Ask for ZIP lookups, demographics, geocoding, routing, and address verification in plain language — no spreadsheet, no copy-paste. Works in claude.ai (web), Claude Cowork, Claude Desktop, Claude Code, and the Claude API — no Claude Team or Enterprise plan required.
https://mcp.cdxzipstream.com/mcpWhat Claude can do with it
ZIP & postal lookup
City, county, state, lat/long, and population for U.S. ZIP and international postal codes — singly or in bulk.
Distance, radius & nearest
Great-circle distance between codes, every ZIP within a radius, and the N closest ZIPs to any point.
Census & ACS demographics
Population, income, age, education, and housing for any ZIP — straight from U.S. Census and ACS data.
Geocoding & reverse geocoding
Turn addresses into coordinates, coordinates back into addresses, and resolve U.S. Census tract (GEOID).
Routing & route optimization
Driving distance and time between stops, plus multi-stop route optimization for delivery and field work.
Address verification
Validate and standardize U.S. mailing addresses to USPS form (ZIP+4, deliverability).
Batch & account tools
Run mixed operations over large lists in one call, and check pricing or your remaining credits any time.
16 tools, all read-only
Every tool is read-only and metered against your account's shared credit pool — per item, per row returned (radius, closest, find), or per stop (optimize_route).
Step 1 — Get your API key
- 1. Create a free account and activate a plan — the Free plan works to start.
- 2. Open Account → API Keys and copy your
cdx_live_…key. - 3. Use it as a Bearer token when you connect (below). Keep it secret — it spends your credits.
Authorization: Bearer cdx_live_YOUR_KEYConnecting from claude.ai in the browser? You don't use a header there — you paste the key once on the CDXZipStream sign-in page (see Step 2). Don't have a key yet? View plans — free to start.
Step 2 — Connect to Claude
Pick how you use Claude — the same connector URL works everywhere. In claude.ai you authorize once on the CDXZipStream sign-in page; in Claude Desktop, Claude Code, and the API you pass your key as a Bearer token (replace cdx_live_YOUR_KEY with your own).
claude.ai (web browser)
Connect with OAuth — Claude registers itself, and you authorize it by pasting your key once on the CDXZipStream sign-in page. No Team or Enterprise plan needed.
- 1. In claude.ai, open Settings → Connectors → Add custom connector.
- 2. Set the URL to
https://mcp.cdxzipstream.com/mcp. - 3. Leave OAuth Client ID and OAuth Client Secret blank — Claude registers itself. Don't paste your key here.
- 4. Click Connect — you'll be taken to the CDXZipStream sign-in page.
- 5. Paste your
cdx_live_key there and click Allow. Done — the tools are now available in your chats.
Claude Cowork
Cowork uses the same custom connector as claude.ai (web) — add it once, then turn it on for a Cowork session. The connection is made from Claude's cloud, so there's nothing to install locally.
- 1. Add the connector exactly as in claude.ai (web) above — Settings → Connectors → Add custom connector, URL
https://mcp.cdxzipstream.com/mcp, OAuth fields blank, Connect, then paste yourcdx_live_key on the CDXZipStream sign-in page and click Allow. (Team/Enterprise orgs add it under Organization settings → Connectors; members then enable it for themselves.) - 2. Open a Cowork session, click the + (lower-left) → Connectors, and toggle CDXZipStream on. The tools are now available to that session.
localhost or LAN-only address won't work in Cowork (it does work for Claude Desktop and Claude Code, which connect from your machine).Claude Desktop
Add CDXZipStream to your Claude Desktop config (Settings → Developer → Edit Config → claude_desktop_config.json). The mcp-remote bridge connects to our server and passes your key as a Bearer header. Add the block below with your key, save, and restart Claude Desktop.
{
"mcpServers": {
"cdxzipstream-geo": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://mcp.cdxzipstream.com/mcp",
"--header", "Authorization: Bearer cdx_live_YOUR_KEY"
]
}
}
}Claude Code (CLI)
Add the connector over HTTP with your key in one command, then run claude and use /mcp to confirm it's connected.
claude mcp add --transport http cdxzipstream-geo \
https://mcp.cdxzipstream.com/mcp \
--header "Authorization: Bearer cdx_live_YOUR_KEY"Claude API (developers)
Pass the connector in the mcp_servers array of a Messages API request, with your key as the authorization_token. The MCP connector is a beta feature — send the current MCP-connector beta header (anthropic-beta) alongside the request; check Anthropic's MCP connector docs for the latest header value.
{
"model": "claude-opus-4-8",
"max_tokens": 1024,
"mcp_servers": [
{
"type": "url",
"url": "https://mcp.cdxzipstream.com/mcp",
"name": "cdxzipstream-geo",
"authorization_token": "cdx_live_YOUR_KEY"
}
],
"messages": [
{ "role": "user", "content": "Look up ZIP code 80401." }
]
}Try these in Claude
Each call meters credits from your account. The pricing and account_balance tools are free — ask Claude to check costs or your balance any time. See plans & credits.
Frequently asked questions
What is the CDXZipStream MCP connector?
It's a remote MCP (Model Context Protocol) server at https://mcp.cdxzipstream.com/mcp that gives Claude direct access to CDXZipStream's geographic tools — ZIP lookups, distance and radius, Census/ACS demographics, geocoding, routing, and USPS address verification — so you can ask for them in plain language instead of pasting data into a spreadsheet.
How do I authenticate?
Authentication uses your CDXZipStream API key as a Bearer token: Authorization: Bearer cdx_live_…. Create a free account, activate a plan (Free works to start), then copy your cdx_live_ key from Account → API Keys.
Which Claude apps work with it?
All MCP-capable Claude surfaces: claude.ai (web), Claude Cowork, Claude Desktop, Claude Code, and the Claude API. In claude.ai and Cowork you connect via OAuth and paste your key once on the CDXZipStream sign-in page (Cowork shares the same custom connector — enable it per session from the + → Connectors menu); Claude Desktop (mcp-remote bridge), Claude Code (claude mcp add), and the API (mcp_servers) send your key directly as a Bearer token. Same connector URL everywhere: https://mcp.cdxzipstream.com/mcp. Note: claude.ai and Cowork reach the server from Claude's cloud, so the URL must be publicly reachable; Claude Desktop and Claude Code connect from your own machine.
Do I need a Claude Team or Enterprise plan?
No. This is a private custom connector that works on any Claude account, including Free/Pro/Max. A Team or Enterprise org is only needed to publish a public listing in Claude's connector directory — that's a separate, optional step.
How does the OAuth connection and revoking work?
When you connect from claude.ai, the OAuth sign-in is simply pasting your cdx_live_ key once on the CDXZipStream consent screen. Claude then stores a short-lived token (not your raw key) that spends the same account credits. Revoking the key — or suspending the account — on the CDXZipStream side immediately disconnects Claude; you can also remove the connector from claude.ai's Connectors settings.
How is usage billed?
Each tool call meters credits from your account's shared pool — most lookups are 1 credit per item, and provider-backed tools like geocoding, routing, and address verification cost more. A few tools are not priced per call: radius, closest, and find charge by the rows they return (1 credit per 25 rows, so the limit you set is the cost control), and optimize_route charges by the number of stops, scaled by the optimization method you choose. The pricing and account_balance tools are always free, so you can check the live rates and your balance any time.
Do I need to write any code?
No. In claude.ai or Claude Desktop you paste a URL and your key — no code required. Developers can also wire it into the Claude API with a few lines of JSON.
Bring geo data into your Claude workflow
Start free, grab your key, and connect in minutes.
