Geocode AI plugin

Website: geocodeai.dev

Administrative boundaries and areas for Claude Code, Codex, Cursor and any agent that reads Agent Skills: look up a country, state, county, city, district or postcode by name or point and get its polygon, list what is inside it, test points against it, merge several, or describe an area in plain language and get one validated polygon back.

Install

Claude Code, in one step:

/plugin install geocode --marketplace MeterApp/geocode-plugins

or add the marketplace first, then install from it:

/plugin marketplace add MeterApp/geocode-plugins
/plugin install geocode@geocode

Then use any tool: your agent opens a Geocode AI sign-in in the browser (free) and keeps the connection. In Claude Code, /mcp shows the connection and signs in again if needed. In Codex, run codex mcp login geocode once after installing (see below). Cursor and the Claude and ChatGPT apps sign in from their connector settings.

On a machine without a browser, sign in with npx @meterapp/geocode login, or add the server yourself with claude mcp add and your own key as shown at https://geocodeai.dev/docs/mcp#claude. For scripts, CI and code, create an API key in the dashboard and keep it as a secret in that environment; the plugin never uses it.

Codex

codex plugin marketplace add MeterApp/geocode-plugins
codex plugin add geocode@geocode
codex mcp login geocode

Codex does not start the sign-in on its own: until you run codex mcp login geocode, codex mcp list shows the server as "Not logged in" and Codex sessions start without the Geocode AI tools. The login opens the browser sign-in (free) and Codex keeps the connection.

Cursor and others: point the MCP config at https://geocodeai.dev/mcp/account, or run npx @meterapp/geocode install to configure Claude Code, Codex and Cursor at once.

What is inside

Skill	For
geocode-boundaries	Find boundaries, get polygons, reverse lookups, children, contains, union
geocode-areas	A polygon from a plain-language description or a contract clause
geocode-api	Writing code against the REST API, the CLI or MCP
geocode-billing	Prices, your plan and usage, checkout and billing-portal links to upgrade or manage it
geocode-feedback	Report bugs with the failing request attached, request features, upvote, follow up, and read or post reviews
geocode-teams	Your organization, its members and teams, and the shared file library: save a boundary export and share it with a team

Plus the hosted MCP server (.mcp.json), whose tools are the API's ops.

What it sends and fetches

The plugin has no local code: its skills are instructions, and every tool call goes to the hosted MCP server at https://geocodeai.dev/mcp over HTTPS. A call sends the tool's arguments (place names, boundary ids, coordinates, an area description) plus the sign-in token your agent holds, and returns boundary metadata, GeoJSON polygons, download links for exports, or account details.

• Boundary lookups are served from Geocode AI's cache of OpenStreetMap and Overture Maps data; the cache keeps no link to who asked. Points sent to contains_points are not stored.
• Area descriptions are sent to Anthropic's Claude API to plan the area and are not kept after the run.
• For each call the service records the operation, units used and timing against your account, for usage and billing.
• Account tools read or change only your own organization (API keys, files, feedback); billing tools return Stripe links that a person opens in a browser. No tool takes card details or charges a card.
• The plugin does no authentication of its own: the host signs you in with your browser and sends its own token to the Geocode MCP server.

Privacy policy: https://geocodeai.dev/privacy · Terms: https://geocodeai.dev/terms

Docs for agents: https://geocodeai.dev/llms.txt

This repository is generated from the Geocode AI source; pull requests here are overwritten on the next release, so please open an issue instead.