Trace MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_schemasC | Extract MCP tool definitions (ProducerSchemas) from server source code. Scans for server.tool() calls and parses their Zod schemas. |
| extract_fileB | Extract MCP tool definitions from a single TypeScript file. |
| trace_usageB | Trace how client code uses MCP tools. Finds callTool() invocations and tracks which properties are accessed on results. |
| trace_fileC | Trace MCP tool usage in a single TypeScript file. |
| compareC | Full analysis pipeline: extract producer schemas, trace consumer usage, and compare them to find mismatches. Returns a detailed report. |
| scaffold_consumerA | Generate consumer code from a producer schema. Creates TypeScript functions, React hooks, or Zustand actions that correctly call MCP tools. |
| scaffold_producerA | Generate producer schema stub from consumer usage. Creates MCP tool definition based on how client code calls it. |
| comment_contractB | Add cross-reference comments to validated producer/consumer pairs. Documents the contract relationship in both files. |
| init_projectC | Initialize a trace project with .trace-mcp config directory. Creates project structure for watch mode and caching. |
| watchB | 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_statusB | 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Mnehmos/trace-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server