Developers · Records MCP server
Give agents tenant-scoped validation context.
Expose validation, issue explanation, quality scores, and run comparison through a workspace-issued agent-tools key.
Available with Records deployments
Smallest useful example
Start from a deployment-issued scope.
The MCP process belongs to a Records deployment. Its key and tenant scope are provisioned before an agent can request validation or run context.
Start the MCP server
npm run --silent mcp:serveExpected contract
What comes back
Bounded tool responses for validation, issue explanation, quality context and comparison of existing runs—not workspace administration.
| Prerequisite | A Records deployment and workspace-issued agent-tools scope |
|---|---|
| Can read | Tenant-scoped validation, findings, quality scores and existing run comparison |
| Cannot change | Servers, settings, keys, baselines or the connected FHIR system |
Built for one clear integration job
The surface stays small; Records carries the wider operational loop when you need it.
Validate resources
Return normalized findings, counts, and a score for a request-local resource and profile.
Explain findings
Give the agent a bounded explanation, suggested fix, and specification links.
Read quality context
Query tenant-scoped scores and compare two existing Records runs without exposing administration.
Scope
The boundary
Know what this surface owns before you put it into a workflow.
What remains outside this surface
The agent-tools scope cannot create or delete servers, change settings, manage keys, establish baselines, or mutate the connected FHIR system.