AI assistants
Claude & MCP
Use OpenGeocoding from a conversation. Our hosted Model Context Protocol (MCP) server uses OAuth: sign in, approve access, and start asking about places. No API key or local server required.
Connect Claude
- Create an OpenGeocoding account and complete email verification, or use an existing account.
- In Claude, open Customize → Connectors → Add → Add custom connector. Team and Enterprise users may need an owner to add the connector first.
- Name it OpenGeocoding and paste this remote MCP server URL: MCP server URL
https://opengeocoding.com/mcp - Choose OAuth sign-in. If Claude asks how to identify its OAuth client, choose Register automatically. Leave client ID, client secret and custom request headers empty.
- Connect, sign in to OpenGeocoding (including two-factor authentication if enabled), then review the permissions and select Allow access.
- Enable OpenGeocoding under the conversation’s connectors/tools menu and ask a question.
Claude’s labels and connector availability can change. See Claude’s custom connector guide for its current interface and organization requirements. This is a custom connector, not a claim of an official Anthropic integration.
Try asking
- “Find the coordinates for 10 Rue de Rivoli, Paris.”
- “What address is near latitude 55.6761, longitude 12.5683?”
- “Resolve the region for Copenhagen, Denmark.”
Available tools
| Tool | API reference |
|---|---|
| search | Search → |
| autocomplete | Autocomplete → |
| retrieve | Retrieve suggestion → |
| reverse | Reverse geocoding → |
| regions | List regions → |
| resolve_region | Resolve regions → |
Tool inputs and results use the same generated schemas as our JSON API. The assistant chooses when to call tools; verify important locations rather than treating model-generated text as a geocoding result.
Credits, permissions and privacy
MCP is included in your existing plan. The free tier includes 50,000 requests per month at up to 2 requests/second, shared across MCP and API keys. Successful search, retrieve, reverse and resolve-region calls each use one credit. Autocomplete and regions consume no credits, including at zero balance, but share the account rate limit. Initialization, tool discovery and failed geocoding operations are not billed. An assistant can make several calls for one message; there is no separate per-connection spending cap.
The geocoding:read scope permits geocoding and consumes
credits. It does not allow account, billing or API-key management. offline_access lets the client refresh its connection without asking
you to sign in each time. Addresses and results are sent to the assistant you authorize; its own privacy
policies also apply.
Review usage and revoke access in Dashboard → Connected apps. Disconnecting removes consent and refresh tokens. The edge normally blocks further geocoding within 5 seconds; during a database outage, existing access can continue until its short-lived access token expires (up to 5 minutes). Removing the connector in Claude alone is not a substitute for revoking access here.
Other MCP clients & troubleshooting
Use the same URL in a client supporting Streamable HTTP, OAuth authorization-code flow with PKCE, protected-resource discovery and dynamic client registration. This is a stateless server; legacy HTTP+SSE connections and local stdio configuration are not supported.
- Claude connects from its cloud infrastructure. The server must be publicly reachable over HTTPS; a localhost URL will not work in Claude’s remote connector.
- If the first tool call says access is not ready, wait a few seconds for the edge’s key sync and retry. Reconnect if access remains invalid.
- If credits or rate limits are reached, check your dashboard and slow down. Do not ask the assistant to retry in a loop.
- If authorization expired, was denied or was disconnected, reconnect from the client. Never paste a password, access token or API key into a chat.