Developers MCP & API
Your network, inside every AI tool you use.
Connect Claude, ChatGPT, Cursor or any MCP client to Geocoupler. Your assistant can search features, read branches and run validation, with exactly the permissions you have.
Is phase-3 ready to merge? Check it against Live and tell me what will block review.
- geocoupler › diff_branch(branch: "phase-3")214 changes · 6 layers
- geocoupler › run_validation(branch: "phase-3")2 errors · 5 warnings
Not yet. Phase 3 changes 214 features across 6 layers, and two of them will block review:
- SC-2041has no upstream feed after the reroute.
- D-778goes over 90% fill on the Mill Road segment.
The 5 warnings are missing attributes on new poles. Want me to open a fix-up branch?
Works with the AI tools your team already uses
- Chat apps: Claude ChatGPT
- Editors & agents: Claude Code Cursor VS Code Windsurf Zed
- Your own: Any MCP client
What people build
Your network, wherever the work is
Once connected, any assistant can read features, branches, schemas and reviews. These are a few of the things teams ask for first.
Claude with Geocoupler connected
Write the crossing narrative for the Mill Road permit, using the design on phase-3.
get_branch search_features
Mill Road crossing — route description
The proposed duct crosses Mill Road at chainage 1+240 by directional bore, 1.2 m below finished road level, avoiding the existing gas main 3.4 m to the north.
Launch and reception pits sit in the verge on both sides; no lane closure is needed outside the 09:30–15:30 window.
Better together
Combine it with the rest of your stack
Most AI clients hold several connections at once. Pair Geocoupler with your tracker, chat and CRM, and one prompt can move work across all of them.
- Geocoupler Jira
Validation errors become tickets
“Open an issue for every error on phase-3 and assign it to the branch owner.”
- Geocoupler Slack
A merge digest every morning
“Post yesterday’s merges to #network-planning with a one-line summary each.”
- Geocoupler Notion
A rollout tracker that stays current
“Update the rollout tracker with homes passed per phase, straight from Live.”
- Geocoupler Google Sheets
A bill of materials, priced
“Pull the BOM for phase-3 and price it against this quarter’s supplier sheet.”
- Geocoupler Salesforce
Sales knows what’s serviceable
“Mark every account within 200 m of a live drop as serviceable.”
- Geocoupler Email
Contractors get the right pack
“Email crew B this week’s splice schedule with a map link for each site.”
Built for teams
Your permissions come along
Connecting an assistant doesn’t open a side door. It signs in as a person, inherits their role, and is held to the same review rules as everyone else.
The same access as the person signed in
An assistant only sees the layers, regions and branches that person’s role allows.
Read-only until an admin says otherwise
Write tools are off by default, and can be switched on per role.
Writes land on a branch, never on Live
Anything an assistant changes goes through review like every other edit.
Every call is on the record
Who asked, from which client, and exactly what it read or touched.
| Time | Who | Tool | Outcome |
|---|---|---|---|
| 09:42 | A. RiveraClaude · search_features | Read | |
| 09:44 | A. RiveraClaude · upsert_features | Branch write | |
| 10:03 | J. OkaforCursor · get_schema | Read | |
| 10:17 | Ops agentAPI key · merge_branch | Blocked | |
| 10:21 | M. LindqvistChatGPT · run_validation | Read |
Setup
Connected in three steps
No keys to manage for everyday use. Your client signs you in with OAuth, and an admin can revoke access at any time.
- 01 · Add
Add the server
Paste the Geocoupler URL into your client’s connector settings, or run one command.
- 02 · Sign in
Approve access
Sign in with your Geocoupler account. SSO works here the same as everywhere else.
- 03 · Ask
Ask about your network
Refer to branches, layers and features by name. The assistant finds the rest.
Settings → Connectors → Add custom connector
https://mcp.geocoupler.com/mcpFor developers
Build on the same API
MCP is the fastest way in. When something needs to run without a person in the loop, use the API underneath it.
REST API
Read and write features, branches, schemas and reviews. Every write is versioned.
Webhooks
Hear about commits, merges, approvals and failed validations the moment they happen.
SDK
A typed TypeScript client for internal tools, pipelines and scheduled jobs.
GET /v1/features
curl https://api.geocoupler.com/v1/features \
-G -d layer=poles -d branch=phase-3 \
-H "Authorization: Bearer $GEOCOUPLER_TOKEN"FAQ
Questions developers ask.
Something else? We’re happy to walk through your setup on a call.
The Model Context Protocol is an open standard that lets AI apps connect to outside tools and data. Geocoupler’s MCP server exposes your network as a set of tools — search features, read a branch, run validation — that your assistant can call when a question needs them.
No. Geocoupler AI is the assistant built into the map. MCP is for bringing your network to the assistant you already use, whether that’s a chat app, an editor or your own agent.
Only if an admin turns write tools on for that role. Even then, changes are made on a branch and go through review like any other edit. Nothing connected over MCP can write to Live directly.
Any client that supports remote MCP servers with OAuth sign-in, including Claude, ChatGPT, Claude Code, Cursor and VS Code. If yours isn’t listed, the setup is usually the same URL.
MCP and API access, rate limits and write tools depend on your plan. See pricing, or talk to us about higher limits and service accounts.
MCP & API
Put your network where the work happens
Connect a client in a couple of minutes, or talk to us about API access, service accounts and higher limits.