Skip to content

MCP connector

The Plandata MCP connector

Ask an assistant which plan checks are waiting on a resubmittal, or have it log a delivery, against your real data and only within the scopes its token was given.

How a connection is authorised

The connector authenticates to the API with an MCP service token (prefix mcpsvc_). Platform staff mint tokens in the admin app, choose their scopes and an expiry of up to 90 days, and can revoke them. A token stops working as soon as the person who minted it is no longer platform staff.

The token goes in the connector’s environment (PLANDATA_MCP_TOKEN, with PLANDATA_MCP_API_URL) or a JSON config file. It is never printed: the CLI and the server redact anything shaped like a token from their output.

One scope per resource and verb

Scopes are written mcp:<resource>:read or mcp:<resource>:write. List and get need read; create, update and delete need write. The API checks the scope on every request, and an API test fails if any scope has no route that enforces it.

Every change made through the connector is attributed to the token and recorded as an audit event.

No business rules in the connector

Each tool forwards to the API and returns its answer. Validation and authorization stay in one place, and API errors come back as tool errors unchanged.

Tools