trace-forge-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@trace-forge-mcpStart a trace for agent 'agent-007' doing market research"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
trace-forge-mcp
MCP server for writing structured traces, spans, and decisions. The only write-path observability MCP — all 9 existing observability MCPs are read-only.
Built for EU AI Act traceability compliance (Article 14, due August 2026).
Install
npx trace-forge-mcpClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"trace-forge": {
"command": "npx",
"args": ["trace-forge-mcp"]
}
}
}From source
git clone https://github.com/mdfifty50-boop/trace-forge-mcp.git
cd trace-forge-mcp
npm install
node src/index.jsRelated MCP server: Dominion Observatory
Tools
trace_start
Begin a new trace for an agent task.
Param | Type | Required | Description |
| string | yes | Unique agent identifier |
| string | yes | What the agent is doing |
| object | no | Optional metadata (model, department, priority) |
Returns: { trace_id, started_at }
trace_span
Create a span within a trace. Spans can be nested via parent_span_id.
Param | Type | Required | Description |
| string | yes | Trace to attach to |
| string | yes | Span name (e.g. "research", "validation") |
| string | no | Parent span for nesting |
| object | no | Optional span metadata |
Returns: { span_id, trace_id }
trace_tool_call
Log a tool call within a trace. Auto-calculates cost estimate from token count.
Param | Type | Required | Description |
| string | yes | Trace this belongs to |
| string | no | Span this belongs to |
| string | yes | Tool that was called |
| object | yes | Arguments passed |
| string | yes | Result preview (max 500 chars) |
| number | no | Token count (enables cost estimation) |
| number | yes | Call duration in milliseconds |
| string | yes |
|
Returns: { event_id, logged: true }
trace_decision
Log an agent decision point with reasoning and alternatives considered.
Param | Type | Required | Description |
| string | yes | Trace this belongs to |
| string | yes | Why the agent made this decision |
| string[] | yes | Other options evaluated |
| string | yes | What was decided |
| number | yes | Confidence 0.0 to 1.0 |
Returns: { event_id, logged: true }
trace_end
Complete a trace. Auto-calculates total duration, event counts, and span counts.
Param | Type | Required | Description |
| string | yes | Trace to complete |
| string | yes |
|
| string | no | Optional summary |
Returns: { trace_id, duration_ms, events_count, spans_count, tool_calls_count }
get_trace
Retrieve a complete trace tree with all spans, events, tool calls, and decisions.
Param | Type | Required | Description |
| string | yes | Trace ID to retrieve |
Returns: Full trace object with nested span tree, all events, and computed totals.
search_traces
Find traces by agent ID and/or status.
Param | Type | Default | Description |
| string | - | Filter by agent |
| string | - | Filter by status |
| number | 20 | Max results (1-100) |
Returns: Matching traces sorted by recency with summary stats.
Resources
URI | Description |
| Last 20 traces with summary |
| Aggregate statistics (total, avg duration, success rate) |
Usage Pattern
1. trace_start — when agent begins a task
2. trace_span — create logical work units (research, generation, validation)
3. During execution:
- trace_tool_call — after each tool invocation
- trace_decision — at each decision point
4. trace_end — when task completes
5. get_trace — retrieve full audit trail
6. search_traces — find traces by agent or statusEU AI Act Compliance
Article 14 of the EU AI Act requires high-risk AI systems to maintain traceability of decisions and actions. trace-forge-mcp provides:
Structured decision logging with reasoning and alternatives
Complete tool call audit trails with timing and cost
Hierarchical span trees for complex multi-step tasks
Agent identification and task attribution
License
MIT
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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/mdfifty50-boop/trace-forge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server