Skip to main content
The Placematic MCP Server lets an AI agent call the Placematic Spatial API directly. It is a thin layer: each tool maps to one endpoint you could call yourself over REST, with your own credential, and returns what that endpoint returns.
Beta. The MCP Server is in beta and is excluded from the availability commitments in the Placematic SLA. The Placematic API services it calls remain covered.

​
Endpoint

Transport is Streamable HTTP. The server targets MCP revision 2026-07-28 and remains compatible with clients on 2025-11-25. Both connect to the same endpoint — you do not select a version.

​
What it does

Four tools are available today: Full argument schemas and response shapes: Tool reference.

​
What it does not do

Read this before you design against it. No write operations. Every tool is a query. No write, update or delete operation exists in the schema — the capability is absent, not disabled. No batch calls. One tool call answers one question. Batching an agent’s work into fewer calls is your concern, not the server’s.

​
What you need

An access token issued by Placematic. Placematic USA LLC is the contracting party — you do not open a HERE account, negotiate a HERE contract, or manage a HERE key.

Request access

Issued within one business day. No credit card, no demo call.

​
Next

Quickstart

Connect Cursor, Claude Code, Claude or ChatGPT.

Authentication

Header auth, connector URLs, and how to handle the token.

Tool reference

Arguments, response shapes, and error behaviour for all four tools.

Troubleshooting

Every failure mode we hit while building this, and what causes it.