Nice to MCP you

I do almost all my 3B building via 3B's platform MCP server these days, using Codex CLI inside a tmux session in Ghostty. I love that it gives me access to 3B from the agent setup I’ve already customized, alongside my existing tools and context, without switching between different applications.

Initially when building this feature, we opted for a small number of tools for external agents to use. These essentially only let an external agent remotely guide the 3B agent itself.

While this worked, the extra handoff slowed the feedback loop and felt clunky in practice. Exposing the workflow-building tools directly worked much better, though it also meant giving external agents enough guidance to understand how 3B actually works.

We addressed that with an introduction to 3B when clients connect, guidance in the tool descriptions, and access to the same built-in skills the 3B agent uses. That gives external agents a solid starting point and a way to look up more detailed guidance as they build.

I find this especially handy for debugging. I can ask my agent to investigate a failed run, inspect its logs, edit the workflow, test the change, and publish the fix, all from the same conversation in the application I already spend most of my time in.

If you want to find out more about the 3B MCP server, check out our docs.