How We Turned CrewForm Agents Into MCP Tools

Last month I shared how we built a visual workflow builder for AI agent teams. This time: how we made those agents callable from Claude Desktop, Cursor, and any other MCP client — without the agents knowing or caring. The idea CrewForm already supported MCP as a client — our agents could call external MCP tool servers (GitHub, Brave Search, Postgres, etc.). But MCP is a two-way standard. We wanted to flip it around: What if your CrewForm agents could BE the tools? Imagine configuring a "Content Writer" agent in CrewForm — with a specific model, system prompt, knowledge base, and tools — and then calling it from Claude Desktop as if it were any other MCP tool. No API wrappers. No custom integration code. Just add a URL to your claude_desktop_config.json and go. The protocol MCP (Model Context Protocol) uses JSON-RPC 2.0 over HTTP. A client connects, discovers tools, and calls them. The key methods: initialize — Handshake. Client sends its info, server responds with capabilities. tools/l