# Give an agent tools from MCP servers

> Give an agent tools from MCP servers: 1 companies fully do it, 17 with a limit, 93 carry the tag. Every listing in Agent frameworks & SDKs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/frameworks.mcp-tools/
- Markdown: https://www.anchorterminal.com/niches/frameworks.mcp-tools/index.md (~1,900 tokens)
- Slim: https://www.anchorterminal.com/niches/frameworks.mcp-tools/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/frameworks.mcp-tools/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 17 | 93 | 12 | 9 |

## What counts as done

The agent lists and calls tools from two or more MCP servers at once, with name clashes handled, auth headers set per run or per user, tool errors passed to the model instead of crashing the run, and servers that fail to connect or need approval reported to the host.

Measured, for our own tests: connect time for 3 servers and run success with concurrency above one.

How agents ask for it: connect the GitHub MCP server to my agent; use these MCP servers from my Python agent; add per-user auth to the MCP calls; load tools from MCP as needed

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Claude Agent SDK (Anthropic, PBC)**: stdio, HTTP, SSE and in-process servers at once, tools namespaced mcp__server__tool, headers set per query, and the init message reports each server as connected, pending, failed or needs-auth. Measured connect time is the suite's.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Agno (Agno Inc.)**: MCPTools and MultiMCPTools take stdio, streamable HTTP and SSE, tool_name_prefix avoids clashes, and header_provider sets headers before each run. How a server that fails to connect is reported to the host isn't shown on the pages read.
- **BoxLang AI (Ortus Solutions, Corp.)**: mcpServers takes HTTP and stdio servers with a prefix against clashes, headers, bearer and OAuth. A server that fails to start is only written to the ai log and the agent carries on, so the host isn't told; the stdio allow-list is open by default.
- **CrewAI (CrewAI, Inc.)**: MCPServerAdapter aggregates stdio, SSE and streamable HTTP servers at once, but the page shows no tool-name prefix for clashes or per-run headers, and a failed server raises from the context manager.
- **Cursor Agent SDK (Anysphere, Inc.)**: Connections reach HTTP and stdio servers, with credential templates in headers and a per-session auth callback for HTTP. An account found servers needing approval vanish from the SDK with no event (forum 178033).
- **Docker Agent (Docker, Inc.)**: The mcp toolset takes local stdio, Docker MCP catalog and remote streamable HTTP or SSE servers, with OAuth handled automatically. The page shows no tool-name prefix for clashes or per-run headers for many users.
- **Agent Development Kit (ADK) (Google LLC)**: McpToolset takes stdio and HTTP connections with tool_filter. The MCP page read shows no name-prefix option, per-user headers or failure reporting, and the listing notes no error handling on the page.
- **guilds.run (Cigale AI)**: Connectors are remote MCP endpoints signed in per organisation, guild or agent with token or OAuth, plus custom headers. Only remote HTTPS endpoints are described, configured in the app rather than per run in code.
- **LangGraph (LangChain, Inc.)**: LangChain's MCP adapter connects several servers, prefixes each tool with its config key and mixes stdio and HTTP; the listing records langchain.mcp as beta. Failure reporting to the host isn't described on the connections page.
- **LlamaIndex Framework (LlamaIndex, Inc.)**: MCP tools load from existing servers into workflows and workflows can be served as MCP. The guide read gives no name-clash handling or failure reporting, and an account found no hook to set tool inputs from the authenticated user (#20386).
- **Mastra (Kepler Software, Inc.)**: MCPClient connects several servers; listTools() prefixes tools with the server name, but the per-user listToolsets() path uses raw names that can collide. Headers and OAuth are supported; how unreachable servers are reported to the host wasn't shown.
- **Microsoft Agent Framework (Microsoft Corporation)**: MCPStdioTool and MCPStreamableHTTPTool connect local and remote servers, headers can be set per run or through a header_provider, and approval_mode applies to MCP tools. Name-clash handling and failure reporting weren't shown on the page.
- **NitroStack (Nitrostack Inc.)**: Covers the reverse case: exposing the team's tools as an MCP server over STDIO and HTTP, with guards for JWTs and API keys. It is not an MCP client, so an agent can't use it to call other servers.
- **OpenAI Agents SDK (OpenAI OpCo, LLC)**: Hosted, streamable HTTP, SSE and stdio servers; include_server_in_tool_names prefixes tools (opt-in); failed servers are dropped and tracked in failed_servers with reconnect(). Headers are set when a server is created, so per-user auth (#1969) still needs one connection per user.
- **Pydantic AI (Pydantic Services Inc.)**: MCPToolset takes Streamable HTTP, SSE and stdio, .prefixed() avoids name clashes, tool errors go back to the model as ModelRetry by default, and headers or a custom http_client are set per toolset. An account hit a cancel-scope error with concurrency above one (pydantic-ai #2818).
- **smolagents (Hugging Face, Inc.)**: MCPClient loads tools from stdio or streamable HTTP servers, including several at once. The tools page shows no name-prefix option, per-run headers or failure reporting.
- **Strands Agents (Amazon Web Services, Inc.)**: MCPClient takes stdio and streamable HTTP (including OAuth or IAM), prefix_with_server_name for clashes, and tool_filters. Per-run headers and failure reporting weren't shown on the page.
- **AI SDK (Vercel Inc.)**: createMCPClient supports HTTP (recommended), SSE and stdio (local only), with headers in the transport. No name-prefix option for clashes appeared on the page, and an open account says prepareStep can't change the tool list per step (vercel/ai #9743).

- not this job: AgentOS (Framers Lab, Inc.): No MCP client page in the docs sitemap or llms.txt; tools come from the app, extensions or the forge.
- not this job: TradingAgents (Tauric Research): No MCP client or server; it is driven through Python or the CLI.

## What stops agents finishing

- two servers exposing the same tool name stop the agent
- headers fixed at start-up, so one server connection cannot serve many users
- no hook to set tool arguments from the authenticated user before a call
- long MCP tasks deleted by a TTL while still working
- no MCP client at all in some listings

## Around it

Before: agent-auth.connect-user-account. After: frameworks.tool-calling-agent.

## Where this comes from

Weight 12 of 100 in Agent frameworks & SDKs: 7 of 61 accounts have this as their main job (share 11.5, rounded by largest remainder to sum 100)

As data: https://www.anchorterminal.com/api/v1/use-cases/frameworks.mcp-tools.json, or the MCP tool get_use_case with id frameworks.mcp-tools. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
