Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_schemas | Extract MCP tool definitions (ProducerSchemas) from server source code. Scans for server.tool() calls and parses their Zod schemas. |
| extract_file | Extract MCP tool definitions from a single TypeScript file. |
| trace_usage | Trace how client code uses MCP tools. Finds callTool() invocations and tracks which properties are accessed on results. |
| trace_file | Trace MCP tool usage in a single TypeScript file. |
| compare | Full analysis pipeline: extract producer schemas, trace consumer usage, and compare them to find mismatches. Returns a detailed report. |
| scaffold_consumer | Generate consumer code from a producer schema. Creates TypeScript functions, React hooks, or Zustand actions that correctly call MCP tools. |
| scaffold_producer | Generate producer schema stub from consumer usage. Creates MCP tool definition based on how client code calls it. |
| comment_contract | Add cross-reference comments to validated producer/consumer pairs. Documents the contract relationship in both files. |
| init_project | Initialize a trace project with .trace-mcp config directory. Creates project structure for watch mode and caching. |
| watch | Watch project files for changes and auto-revalidate contracts. Actions: start (begin watching), stop (end watching), status (check state), poll (get pending events). |
| get_project_status | Get the status of a trace project including config, cache state, and last validation result. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |