Hey MCP developers! Let’s talk about something broken 🧠🛠️ Agents are calling tools left and right. But what happens inside those tools? No traces. No visibility. No security. Just a black box. 🕋 The observability gap is real. Let's fix it together with observable[.]tools

We believe observability shouldn’t be a bolt-on. It should be a first-class citizen in the agent stack. So we’re launching initiative to bring full-stack tracing to MCP tools using OpenTelemetry. Think: from black boxes → glass boxes. ⎚

To achieve this, we propose a combining OTel (open telemetry) into the official MCP protocol via a spec RFC. Combining two vendor neutral, open protocols to enable easy observability for MCP developers and tool makers (both client and server). Full proposal details on Github:

We want to build this ecosystem together. W&B is extending an invitation to our friends from the observability industry. So... 👀 @LangChainAI, @braintrustdata, @pydantic, @arizeai, @rungalileo, @AgentOpsAI & others. Will you join this effort with us, to enable observability for the million incoming MCP developers?

Most importantly—this is a call to YOU, the MCP tool developers. ✅ Read the manifesto 💬 Weigh in on the spec RFC 🛠️ Start building tools with observability baked in The agentic future demands transparency. Let’s build it right at

Quantum computers can break today’s encryption in seconds.🔑 Quantum tech will reshape our digital lives. Governments & hackers are preparing for the quantum era. How about you?🛡️ Don’t get left behind!🧠 Cybersecurity Dictionary for Everyone can help:

Why wouldn’t MCP servers just use whatever observability stack the org who built/hosts the server is using? MCP is just a certain kind of API

Totally fair q, William. We believe agent developers need end-to-end visibility across tools. If each server logs to its own stack, there's no unified trace tree. Our approach keeps server setup simple and gives the client full control of observability.

Absolutely! Let's open those black boxes and bring transparency to AI tools. Count me in to tackle the observability gap!

🫡

Chain abstraction is a game-changer, but adoption is the real test! 🚀 Curious—how does @wandb plan to tackle scalability & cross-chain UX? Looking forward to seeing this evolve!

What do you think is the biggest barrier to adoption for this?

Hey Dylan, great question! We've outlined a few issues in the MCP RFC we posted, namely - While this isn't in the MCP spec, there isn't a standard way for clients and servers to show the developer a combined trace tree - For servers, authentication into Otel backends will be an issue, so we propose a way to have the Client receive and organize all the traces - As with every protocol, even if our proposal is accepted, adoption into the various SDKs (Python, TypeScript, C# etc) will take time But we are committed to make sure MCP will be fully observable!