mcpadapt

What it does

MCPAdapt bridges Model Context Protocol servers to agentic frameworks. It converts any MCP server—deployed locally via stdio or remotely via SSE—into native tools for smolagents, langchain, crewAI, google-genai, and others. This lets you access 650+ published MCP servers without writing framework-specific integration code. Smolagents users get direct integration; others install framework-specific extras like mcpadapt[langchain], pass MCP server parameters to MCPAdapt, and receive tools as if they were authored for your framework natively.

Who it's for

Developers building agents who want to reuse existing MCP server implementations—filesystem operations, web search, database queries, domain-specific tools—across multiple frameworks. If you're writing in smolagents, langchain, or crewAI and want to plug community MCP servers without custom wrappers, this eliminates the glue code.

Common use cases

• Use an MCP filesystem server to let agents read and write files directly.
• Combine multiple MCP servers in a single crewAI workflow for integrated access to search, data, and APIs.
• Deploy an MCP server remotely and connect agents over SSE without modifying agent code.
• Publish a tool as an MCP server once and reuse it across smolagents, langchain, and crewAI without duplication.

Setup pitfalls

• Framework dependencies are optional. pip install mcpadapt alone fails; you need mcpadapt[langchain], mcpadapt[crewai], or similar depending on your framework.
• Stdio servers must be executable and on PATH. Misconfiguration silently fails at tool initialization time.
• README warns against untrusted MCP servers, especially over SSE—verify the source and security before connecting.
• Last commit 224 days ago; verify there are no outstanding blockers if you need recent MCP protocol updates.