Also verified: mcp 1.24.0 with instrumentor 2.0.10. The extra no longer installs that older instrumentor. See supported frameworks for how verification works.
In code
Calltracing.init(), attach the framework instrumentor to the provider it returns, and wrap the work in tracing.turn() and tracing.agent().
In this sample an LLM, through the OpenAI SDK, calls a tool on an MCP server running in the same process. The
[mcp] extra traces the MCP client and server, and [openai] traces the LLM calls.1
Install
terminal
2
Add the code
app.py
3
Run
terminal
BOTGAUGE_API_KEY, OPENAI_API_KEY, OPENAI_MODEL. Set OPENAI_BASE_URL too if your LLM isn’t api.openai.com.Zero-code
Leave your app unchanged and start it withbotgauge instrument. The sample still wraps the work in tracing.turn() and tracing.agent() so spans carry session and agent ids.
In this sample an LLM, through the OpenAI SDK, calls a tool on an MCP server running in the same process. The
[mcp] extra traces the MCP client and server, and [openai] traces the LLM calls.1
Install
terminal
2
Add the code
app.py
3
Run
terminal
BOTGAUGE_API_KEY, OPENAI_API_KEY, OPENAI_MODEL. Set OPENAI_BASE_URL too if your LLM isn’t api.openai.com.View MCP spans live
Watch your MCP client, server, and LLM tool calls appear in BotGauge.
.png?fit=max&auto=format&n=rExdh2xAS2_ywWU5&q=85&s=2336659947d2543be68f95bf2d539b85)