Skip to content

API reference

MCP door

The record as Model Context Protocol tools. Agents read the context of record, propose entries and check authority before acting, under the same labels as every other read.

POST https://YOUR-MCP-DOOR-ADDRESS/mcp

The MCP door is a Model Context Protocol server over streamable HTTP. Any MCP client that supports remote servers can connect.

The MCP door follows the MCP authorization specification.

  • The door publishes protected resource metadata at /.well-known/oauth-protected-resource. Your client reads it, finds the authorization server and signs you in through the browser.
  • A request without valid authorization gets a 401 with a WWW-Authenticate challenge that points to that metadata, and no tool list.
  • Your sign-in maps to a Syderial principal and a set of scopes. Roles and groups in your identity provider don’t grant Syderial authority on their own.
  • Clients that can’t sign in through a browser can send a header credential, as for the model doors.

initialize opens a session and returns an Mcp-Session-Id header. Later requests in the session send that header and must authenticate as the same identity. Sessions end on DELETE, when the transport closes, or after a period of inactivity.

tools/list returns the tools your scopes allow. They fall into these families.

Family What the tools do
Record Propose an entry without committing it, commit an authorized proposal and read the history of a subject.
Context Retrieve the context of record for a question as a packet, limited to your clearance.
Evidence Expand one piece of cited evidence into its signed source window.
Artifacts Register an artifact and its source, and read what you are cleared to see of it.
Case files Open, update, review and close a bounded working matter, with a receipt on closing.
Authority Simulate whether an action would be allowed before attempting it.
Briefs Read the daily and weekly briefs and the items that have drifted, within your boundary.
Execution Propose an action without side effects, turn an approved proposal into a ticket and read its status.

Syderial checks every tool call against authority and records it. Writes pass through the same stations as every other write, so Syderial commits a proposal only when its evidence supports it.

claude mcp add --transport http syderial https://YOUR-MCP-DOOR-ADDRESS/mcp

Then run /mcp in a session and sign in.

See Coding harnesses for the full setup.