https://openai.github.io/openai-agents-python/mcp/ [ ] [ ] Skip to content logo OpenAI Agents SDK Model context protocol (MCP) [ ] Initializing search logo OpenAI Agents SDK * Intro * Quickstart * Examples * [*] Documentation Documentation + Agents + Running agents + Results + Streaming + Tools + [ ] Model context protocol (MCP) Model context protocol (MCP) Table of contents o MCP servers o Using MCP servers o Caching o End-to-end examples o Tracing + Handoffs + Tracing + Context management + Guardrails + Orchestrating multiple agents + Models + Configuring the SDK + Agent Visualization + [ ] Voice agents Voice agents o Quickstart o Pipelines and workflows o Tracing * [ ] API Reference API Reference + [ ] Agents Agents o Agents module o Agents o Runner o Tools o Results o Streaming events o Handoffs o Lifecycle o Items o Run context o Usage o Exceptions o Guardrails o Model settings o Agent output o Function schema o Model interface o OpenAI Chat Completions model o OpenAI Responses model o MCP Servers o MCP Util + [ ] Tracing Tracing o Tracing module o Creating traces/spans o Traces o Spans o Processor interface o Processors o Scope o Setup o Span data o Util + [ ] Voice Voice o Pipeline o Workflow o Input o Result o Pipeline Config o Events o Exceptions o Model o Utils o OpenAIVoiceModelProvider o OpenAI STT o OpenAI TTS + [ ] Extensions Extensions o Handoff filters o Handoff prompt Table of contents * MCP servers * Using MCP servers * Caching * End-to-end examples * Tracing Model context protocol (MCP) The Model context protocol (aka MCP) is a way to provide tools and context to the LLM. From the MCP docs: MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools. The Agents SDK has support for MCP. This enables you to use a wide range of MCP servers to provide tools to your Agents. MCP servers Currently, the MCP spec defines two kinds of servers, based on the transport mechanism they use: 1. stdio servers run as a subprocess of your application. You can think of them as running "locally". 2. HTTP over SSE servers run remotely. You connect to them via a URL. You can use the MCPServerStdio and MCPServerSse classes to connect to these servers. For example, this is how you'd use the official MCP filesystem server . async with MCPServerStdio( params={ "command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", samples_dir], } ) as server: tools = await server.list_tools() Using MCP servers MCP servers can be added to Agents. The Agents SDK will call list_tools() on the MCP servers each time the Agent is run. This makes the LLM aware of the MCP server's tools. When the LLM calls a tool from an MCP server, the SDK calls call_tool() on that server. agent=Agent( name="Assistant", instructions="Use the tools to achieve the task", mcp_servers=[mcp_server_1, mcp_server_2] ) Caching Every time an Agent runs, it calls list_tools() on the MCP server. This can be a latency hit, especially if the server is a remote server. To automatically cache the list of tools, you can pass cache_tools_list=True to both MCPServerStdio and MCPServerSse. You should only do this if you're certain the tool list will not change. If you want to invalidate the cache, you can call invalidate_tools_cache() on the servers. End-to-end examples View complete working examples at examples/mcp. Tracing Tracing automatically captures MCP operations, including: 1. Calls to the MCP server to list tools 2. MCP-related info on function calls MCP Tracing Screenshot