How do AI agents use OpenCage through Open Connector?

Your user connects OpenCage once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes OpenCage tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a OpenCage MCP server?

Yes. Open Connector can serve OpenCage as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call OpenCage actions with credentials injected server-side.

Where do OpenCage credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

OpenCage integration

OpenCage integration for AI agents.

OpenCage integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves OpenCage tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real OpenCage actions, managed and audited.

Your user connects OpenCage once; your agent can then worldwide forward and reverse geocoding API. Affordable, predictable pricing. GDPR compliant, made with open data, trusted by thousands of developers — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants OpenCage access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported OpenCage tools.

4 tools are generated from the published OpenCage catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 4 tools. All published catalog entries are included in this page's server-rendered HTML.

request a GeoJSON geocoding response: Geocode (GeoJSON); GeocodingReverse Geocoding
request a JSON geocoding response: Geocode (JSON); GeocodingReverse Geocoding
check API health and connectivity: Health check endpoint to verify API availability; Health
request an XML geocoding response: Geocode (XML); GeocodingReverse Geocoding

FAQ

OpenCage integration, answered

How do AI agents use OpenCage through Open Connector?: Your user connects OpenCage once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes OpenCage tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a OpenCage MCP server?: Yes. Open Connector can serve OpenCage as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call OpenCage actions with credentials injected server-side.
Where do OpenCage credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents OpenCage — keep the keys.

Open source, self-hostable, with OpenCage credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →