MCP server for AI agents
ParcelAPI has a hosted Model Context Protocol server, so Claude, Cursor and other MCP clients can search US parcels and building permits directly.
- Endpoint:
https://api.parcelapi.net/mcp(Streamable HTTP) - Auth: your API key as
Authorization: Bearer <key>(orX-API-Key) - Billing: the same as the REST API: 1 credit per record returned, minimum 1 credit per search; searches that time out are free. No owner names or contact data are ever returned.
Tools
query_parcels: parcels by state plus county, city prefix or address prefix (1 credit per record, min 1)query_permits: building permits by state plus city, county, address, type or dates (1 credit per record, min 1)get_credit_balance: your remaining credits (free)list_credit_packs: packs and prices (free)buy_credits: a Stripe Checkout link; a human pays (free)claim_api_key: get a new key after a keyless checkout (free)get_fetch_job: status of an on-demand area fetch (free)
Cursor
In ~/.cursor/mcp.json or .cursor/mcp.json:
{
"mcpServers": {
"parcelapi": {
"url": "https://api.parcelapi.net/mcp",
"headers": { "Authorization": "Bearer your-key-here" }
}
}
}
Claude Code
claude mcp add --transport http parcelapi https://api.parcelapi.net/mcp --header "Authorization: Bearer your-key-here"
Claude Desktop
Use the mcp-remote bridge in claude_desktop_config.json so the key is sent as a header:
{
"mcpServers": {
"parcelapi": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.parcelapi.net/mcp",
"--header", "Authorization: Bearer ${PARCELAPI_KEY}"],
"env": { "PARCELAPI_KEY": "your-key-here" }
}
}
}
No key yet?
Ask your agent to call list_credit_packs, then buy_credits with a pack name. Open the checkout link and pay, then have the agent call claim_api_key with the session_id. The key is shown once, so store it safely. See pricing.
REST and OpenAPI
OpenAPI: api.parcelapi.net/openapi.json · interactive docs: api.parcelapi.net/docs · summary for LLMs: /llms.txt