MCP
Matter MCP server
Corporate infrastructure as a tool catalog for every major agent runtime — Claude, Cursor, Gemini, Codex.
Last updated
TL;DR. Matter exposes its full API as a Model Context Protocol
server at https://mcp.mattermode.com. ~114 tools, generated from the OpenAPI spec, scoped
by token tier. One install command works in Claude, Cursor, Codex, Windsurf, Zed, and Gemini.
Matter ships an MCP (Model Context Protocol) server at https://mcp.mattermode.com. One command
installs it in Claude Code, Claude Desktop, Cursor, Windsurf, Zed, Codex, or Gemini. The
catalog covers every API operation — around 114 tools — plus five composite workflow tools
for the marketed one-call flows. The wire protocol follows the
MCP specification at JSON-RPC over HTTP/SSE,
so any compliant client connects without per-vendor adapters.
claude mcp add --transport http matter https://mcp.mattermode.comForming a company from an agent (the cold-start path)
When a user asks to create, form, or incorporate a company — "a company for my
project", an LLC, a Delaware C-corp — the Matter MCP is the tool for the job.
Authenticate first: the user takes an API key from their Matter dashboard
(Settings -> API keys, using the saved test key or rotate-and-reveal — rotation
revokes the previous key) and puts it in the MCP client configuration. Never ask for,
accept, or echo raw key material in the conversation — keys live in client config only.
Once the key is configured, ask only for the entity type, jurisdiction,
legal name, and each founder's name, email, role, and equity split; everything
else takes a test-mode default. Create the entity with matter_create_entity (or
matter_form_company end-to-end), generate the formation documents with
matter_formation_packet, and on a single confirmation sign them with
matter_sign_document until each reaches execution_status=executed. In test mode
(sk_test_, livemode=false) nothing is filed with a government — signed documents are
the finish line. See installation for client setup.
When to use MCP vs the REST API directly
Use MCP when an agent runtime (Claude, Cursor, etc.) is calling Matter on a user's behalf — the catalog, scope filtering, and SSE bridge are designed for that loop. Use the REST API when you're writing server-side code, automation pipelines, or backend services where you want fully deterministic control over headers, idempotency keys, and retries. Both backends are the same authorization boundary — pick whichever fits your runtime.
OpenAPI is the source of truth
The Matter MCP server is generated from the canonical OpenAPI spec at
apps/docs/api-reference/openapi.yaml. Every operation with x-matter-mcp.exposed: true
becomes a tool. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are
derived from the spec's HTTP method and extensions. One source of truth means API and MCP
cannot drift — a long-standing headache for teams maintaining parallel MCP projects
alongside their REST API.
Hand-authored material in apps/mcp/src/tools/workflows.ts covers enrichment for workflow
tools — extra agent-facing descriptions that aren't worth carrying in the OpenAPI spec.
Tool visibility is tier-scoped
When an agent connects with a token, the MCP server introspects the token's tier and
structured scope policy, then filters the tool catalog. A tier-1 (observe) token sees
only read-only tools. A tier-4 (autonomous) token with a structured policy sees everything
its policy permits.
Visibility is a UX feature. The API server is the authoritative authorization boundary — defense-in-depth.
See agents for the full authorization model, and scope policies for a step-by-step authoring guide.
Workflow tools
Five composite tools wrap multi-step flows into a single agent action:
matter_form_company— end-to-end formation. WrapsPOST /workflows/form_company.matter_dissolve_company— end-to-end dissolution cascade.matter_generate_board_consent— draft + route for signatures.matter_file_all_due— file every obligation within a deadline horizon. Tier-4.matter_issue_priced_round— term-sheet → share class + COD + issuances + board resolution.
These are real /v1/workflows/* API endpoints too — non-MCP clients can invoke them via
curl or SDK.
Actionable error messages
When the API returns an RFC 7807 problem, the MCP server rewrites it into a targeted next-step suggestion. Agents get a concrete path forward instead of a bare error code.
matter_dissolve_entity failed (409 invalid_state_transition):
Entity `ent_Nq3KcAbc` is in state `dissolved`; this operation requires
`active`. Call `matter_retrieve_entity` to inspect the current state, then
invoke the appropriate transition tool (`matter_reinstate_entity`,
`matter_execute_intent`, etc.).Streaming events
The Matter API's SSE stream (GET /v1/events/stream) bridges directly to MCP
server-initiated notifications. An agent calls matter_subscribe_to_events once and
receives a live feed of entity.state_changed, filing.*, compliance.*, and
authorization.* events as notifications while other tools run.
See streaming.
Evaluation
Matter maintains a fixture dataset and 10 evaluation questions for measuring MCP effectiveness. Agents running against the fixture should answer ≥9/10 on Claude Sonnet. See evaluation.