AI Agent Tools With MCP Support

49 of the 64 tools in our index document real support for the Model Context Protocol (MCP) today — as a client, a server, or both. Coding agents and frameworks lead; sales and marketing agents are the clear laggard.

MCP (the Model Context Protocol) is becoming the default way an AI agent reaches your tools and data instead of a bespoke integration per pair — see our full explainer for what it is and why it matters when you're picking an agent to build on. This collection answers the practical question that piece leaves open: which tools in our own index actually document it today. 49 of the 64 tools here do, spanning every one of our seven categories — some as a client (they can call out to any MCP server), some as a server (other agents can call into them), several as both — including Glean, which ships MCP in both directions today.

The split isn't even. Agent frameworks are unanimous (11 of 11 — Google ADK and Claude Agent SDK, both major-lab arrivals since the last count, keep the category perfect) and coding agents are close behind (16 of 19) — unsurprising, since MCP began as a developer-tooling protocol. Sales and marketing agents are the clear laggard: only Clay (a full MCP server) and 11x (one undetailed pricing-page bullet, the thinnest evidence in this set) document anything at all. Fourteen tools in the index are not included here — Aider, Lindy, GC AI, Artisan, Qualified, Rox, Decagon, Bland AI, Juggler, Zot, Unify, Moveworks, Undermind and Vecbase — either because they have confirmed they don't support it yet (Aider has an open, unresolved GitHub request since December 2024; Lindy's own blog says it isn't compatible yet; Moveworks' own blog still frames MCP as "in development," not shipped) or because no MCP claim appears anywhere in their own docs, site or changelog as of this check.

Why this collection

A tool earns a place here only when its own docs, GitHub repo, blog or changelog make an explicit MCP claim — as a client, a server, or both — not a generic "integrations" or "API" mention. 35 of the 49 here were confirmed in our original MCP census (see the full article for the per-tool sourcing); the other 14 — Warp, CodeRabbit, Salesforce Agentforce, Antigravity CLI, PolyAI, Mastra, Letta, Factory, Glean, Zed, Microsoft Agent Framework, Botsify, Google Agent Development Kit and Claude Agent SDK — were added to the index afterward. The first 9 of those 14 were independently re-verified against primary vendor docs on 2026-07-25, the same pass that checked Unify and Moveworks and confirmed neither supports MCP yet; Zed, Microsoft Agent Framework, Botsify, Google Agent Development Kit and Claude Agent SDK were each confirmed directly from their own already-Published, sourced listing fields (integrations and key-features), not a fresh vendor-docs pass — each already names MCP explicitly as a documented integration, not a generic API mention. Every one of these facts is also recorded on the tool's own listing (integrations + sourced citation), not stated here alone. MCP adoption is moving fast in 2026; treat this as a snapshot, not a ceiling, and check a specific vendor's current docs before relying on it for a real integration.