API / MCP Docs

Connect to Locus Data

Use a remote MCP client that supports Streamable HTTP and OAuth authorization code with S256 PKCE. Ask Locus chat is optional. This release exposes MCP tools; a separate general-purpose REST query API is planned.

1. Add the server URL to your client’s remote MCP connections.
2. Sign in to Locus in the browser opened by your client. Review the client name and requested scopes before allowing access.
3. Call list_data_capabilities, then get_data_dictionary. Query only a geographic slice that has current records.

Manage or revoke your connections

Read tools

Every tool is read-only. Reads do not call a model, acquire new evidence, start research or spend credits.

Structured query examples

These are tool arguments for an authorized MCP client. Pilot results are limited observations, subject to their original expiry. An empty result cannot establish that a property, business or permit is absent.

{
  "name": "read_planning_context",
  "arguments": {
    "geography": "England:51.5407,-0.1464",
    "sourceId": "planning_constraints",
    "limit": 10
  }
}

{
  "name": "read_property",
  "arguments": {
    "geography": "NYC:1000010010",
    "sourceId": "nyc_pluto",
    "limit": 10
  }
}

Coverage and availability

The review seed contains four observations: one English conservation-area record and three NYC tax-lot/permit observations. No national UK or US coverage is implied. UPRN, parcel, Overture Places and workplace import adapters have no continuing national import. Other UK jurisdictions, US states and local planning authorities remain gaps.

The authenticated capability catalogue reports what is currently loaded and permitted. “Reviewed” below means a source projection passed review; it does not mean records are loaded or your connection can read them.

Access, limits and errors

data:public

Reviewed public extracts, subject to current plan access.

data:saved

Normalized saved evidence with reviewed external-AI rights. Legacy raw reports are withheld.

data:projects

Your permitted project metadata and candidate decisions. Private notes are excluded.

data:pulse

Reviewed normalized Pulse observations, subject to monitoring access. Legacy payloads are withheld.

data:briefs

Your saved tenant comparisons with separate, explicit per-report external-AI consent.

Scopes grant an upper bound. Each request also checks your current account, existing plan entitlement, ownership, source policy and evidence expiry. There is no separate MCP price or allowance. Reads never reset or renew an exhausted allocation.

• 60 authenticated requests per account per minute, shared across connections.
• 64 KiB request body; bounded query pages up to 100 rows; a 256 KiB total response ceiling.
• No arbitrary SQL, provider credentials, model calls, owner prospecting or research-execution tools.

available / unavailable

Permitted current rows exist / no permitted current rows in this slice. No new acquisition is triggered.

restricted / unsupported

Rights, scope or entitlement withholds this capability / the release does not support it.

HTTP 401 / 429

Authorize again if the connection expired or was revoked / wait for the next read window. Do not loop retries.

RESPONSE_TOO_LARGE

Reduce the query limit. Report readers return an error if the frozen publication exceeds the response ceiling.

For protocol details, see the official MCP authorization specification. For Locus evidence interpretation, see Data sources and Methodology.