MCP · Tools
Tool catalog
Every MCP tool — one flat catalog generated from the OpenAPI spec. Lifecycle is a per-tool tag you can filter by.
Last updated
TL;DR. ~114 tools, generated from the OpenAPI spec into one flat, resource-first catalog. Lifecycle (Create / Manage / Exit / Platform) is a per-tool tag, not the catalog's structure — the per-phase pages (Create, Manage, Exit, Platform) are filtered views over the same flat catalog. What your agent sees is also filtered by token tier.
Every operation in the OpenAPI spec marked x-matter-mcp.exposed: true becomes an MCP tool at build time. The catalog is a single flat list of tools; the per-phase pages — Create, Manage, Exit, and Platform — are lifecycle filters over it. Generation follows the MCP tool descriptor format — every tool ships name, description, inputSchema, and annotations (readOnlyHint, destructiveHint, idempotentHint).
When to browse this page vs ask the agent
Browse this page when you're planning an integration — you want to know the full surface area. Ask the agent (e.g. "what matter tools do I have?") when you're using an integration — the agent's view is already filtered by your token's tier and policy, so it shows you what you can actually call right now.
What you actually see in your agent runtime is filtered by tier — tier-1 tokens see read-only tools only, tier-4 tokens see the full autonomous surface. The catalog pages below list the full set; your runtime lists only the tools your token is allowed to call.
Lifecycle is a filter tag
A tool's lifecycle tag (x-matter-lifecycle.primary) marks the phase where its underlying API operation is idiomatically invoked over the life of an entity — not the phase of its resource tag. It is metadata for filtering, not the catalog's organizing axis: a single resource (e.g., matter_*_filing) carries tools across several phases. The per-phase pages list the tools carrying each tag:
- Create — formation bundle: incorporation, founder stakeholders, initial cap table, formation documents, intent resolution, portfolio genesis.
- Manage — live-entity operations: cap-table maintenance, ongoing filings, resolutions, compliance, audit, authorizations, composite governance workflows.
- Exit — dissolution cascade and M&A envelope: mergers, acquisitions, asset and stock sales, reorganizations, and their composite workflows.
- Platform — lifecycle-orthogonal infrastructure: tokens, webhooks, events, support request lookup.
Tools are named matter_<verb>_<resource> (e.g., matter_create_entity, matter_dissolve_company). The phase is in each tool's metadata via x-matter-lifecycle.primary, not in the name itself — names stay generic so agents can reason about them across phases.
How tools map to API endpoints
Every MCP tool is a real /v1/* API endpoint. Clicking an entry in the catalog links to the full API reference (parameters, examples, response schemas). For composite flows — matter_form_company, matter_dissolve_company, matter_acquire_company, etc. — see Workflows.