This repository demonstrates LLM Agents using tools from Model Context Protocol (MCP) servers with several frameworks:
- Google Agent Development Kit (ADK)
- LangGraph Agents
- OpenAI Agents
- Pydantic-AI Agents
Both single and multiple MCP server examples are demonstrated
- Agent with a single MCP server
- Agent with multiple MCP servers
- Also includes Agent evaluations
The repo also includes a Python MCP Server run_server.py
based on MCP Python SDK Quickstart
- Modified to include a datetime tool and run as a server invoked by Agents
Tracing is done through Pydantic Logfire.
cp .env.example .env
- Add
GEMINI_API_KEY
and/orOPENAI_API_KEY
- Individual scripts can be adjusted to use models from any provider supported by the specific framework
- By default only basic_mcp_use/oai-agent_mcp.py requires
OPENAI_API_KEY
- All other scripts require
GEMINI_API_KEY
(Free tier key can be created at https://aistudio.google.com/apikey)
- By default only basic_mcp_use/oai-agent_mcp.py requires
- Individual scripts can be adjusted to use models from any provider supported by the specific framework
- [Optional] Add
LOGFIRE_TOKEN
to visualise evaluations in Logfire web ui
Run an Agent framework script e.g.:
-
uv run agents_mcp_usage/basic_mcp/basic_mcp_use/pydantic_mcp.py
- Requires
GEMINI_API_KEY
by default
- Requires
-
uv run agents_mcp_usage/basic_mcp/basic_mcp_use/oai-agent_mcp.py
- Requires
OPENAI_API_KEY
by default
- Requires
Check console or Logfire for output
This project aims to teach:
- How to use MCP with multiple LLM Agent frameworks
- How to see traces LLM Agents with Logfire
- How to evaluate LLMs with PydanticAI evals
-
agents_mcp_usage/basic_mcp/ - Single MCP server integration examples
-
basic_mcp_use/ - Contains basic examples of single MCP usage:
adk_mcp.py
- Example of using MCP with Google's Agent Development Kit (ADK)langgraph_mcp.py
- Example of using MCP with LangGraphoai-agent_mcp.py
- Example of using MCP with OpenAI Agentspydantic_mcp.py
- Example of using MCP with Pydantic-AI
-
eval_basic_mcp_use/ - Contains evaluation examples for single MCP usage:
evals_adk_mcp.py
- Evaluation of MCP with Google's ADKevals_langchain_mcp.py
- Evaluation of MCP with LangGraphevals_pydantic_mcp.py
- Evaluation of MCP with Pydantic-AI
-
-
agents_mcp_usage/multi_mcp/ - Advanced multi-MCP server integration examples
- multi_mcp_use/ - Contains examples of using multiple MCP servers simultaneously:
pydantic_mcp.py
- Example of using multiple MCP servers with Pydantic-AI Agent
- eval_multi_mcp/ - Contains evaluation examples for multi-MCP usage:
evals_pydantic_mcp.py
- Example of evaluating the use of multiple MCP servers with Pydantic-AI
- multi_mcp_use/ - Contains examples of using multiple MCP servers simultaneously:
-
Demo Python MCP Server
run_server.py
- Simple MCP server that runs locally, implemented in Python
The basic_mcp
directory demonstrates how to integrate a single MCP server with different agent frameworks. Each example follows a similar pattern:
- Environment Setup: Loading environment variables and configuring logging
- Server Connection: Establishing a connection to the local MCP server
- Agent Configuration: Setting up an agent with the appropriate model
- Execution: Running the agent with a query and handling the response
The MCP server in these examples provides:
- An addition tool (
add(a, b)
) - A time tool (
get_current_time()
) - A dynamic greeting resource (
greeting://{name}
)
graph LR
User((User)) --> |"Run script<br>(e.g., pydantic_mcp.py)"| Agent
subgraph "Agent Frameworks"
Agent[Agent]
ADK["Google ADK<br>(adk_mcp.py)"]
LG["LangGraph<br>(langgraph_mcp.py)"]
OAI["OpenAI Agents<br>(oai-agent_mcp.py)"]
PYD["Pydantic-AI<br>(pydantic_mcp.py)"]
Agent --> ADK
Agent --> LG
Agent --> OAI
Agent --> PYD
end
subgraph "Python MCP Server"
MCP["Model Context Protocol Server<br>(run_server.py)"]
Tools["Tools<br>- add(a, b)<br>- get_current_time()"]
Resources["Resources<br>- greeting://{name}"]
MCP --- Tools
MCP --- Resources
end
subgraph "LLM Providers"
OAI_LLM["OpenAI Models"]
GEM["Google Gemini Models"]
OTHER["Other LLM Providers..."]
end
Logfire[("Logfire<br>Tracing")]
ADK --> MCP
LG --> MCP
OAI --> MCP
PYD --> MCP
MCP --> OAI_LLM
MCP --> GEM
MCP --> OTHER
ADK --> Logfire
LG --> Logfire
OAI --> Logfire
PYD --> Logfire
LLM_Response[("Response")] --> User
OAI_LLM --> LLM_Response
GEM --> LLM_Response
OTHER --> LLM_Response
# Google ADK example
uv run agents_mcp_usage/basic_mcp/basic_mcp_use/adk_mcp.py
# LangGraph example
uv run agents_mcp_usage/basic_mcp/basic_mcp_use/langgraph_mcp.py
# OpenAI Agents example
uv run agents_mcp_usage/basic_mcp/basic_mcp_use/oai-agent_mcp.py
# Pydantic-AI example
uv run agents_mcp_usage/basic_mcp/basic_mcp_use/pydantic_mcp.py
More details on basic MCP implementation can be found in the basic_mcp README.
The multi_mcp
directory demonstrates advanced techniques for connecting to and coordinating between multiple specialised MCP servers simultaneously. This approach offers several advantages:
- Domain Separation: Each MCP server can focus on a specific domain or set of capabilities
- Modularity: Add, remove, or update capabilities without disrupting the entire system
- Scalability: Distribute load across multiple servers for better performance
- Specialisation: Optimise each MCP server for its specific use case
graph LR
User((User)) --> |"Run script<br>(e.g., pydantic_mcp.py)"| Agent
subgraph "Agent Framework"
Agent["Pydantic-AI Agent<br>(pydantic_mcp.py)"]
end
subgraph "MCP Servers"
PythonMCP["Python MCP Server<br>(run_server.py)"]
NodeMCP["Node.js MCP Server<br>(mermaid-validator)"]
Tools["Tools<br>- add(a, b)<br>- get_current_time()"]
Resources["Resources<br>- greeting://{name}"]
MermaidValidator["Mermaid Diagram<br>Validation Tools"]
PythonMCP --- Tools
PythonMCP --- Resources
NodeMCP --- MermaidValidator
end
subgraph "LLM Providers"
LLMs["PydanticAI LLM call"]
end
Logfire[("Logfire<br>Tracing")]
Agent --> PythonMCP
Agent --> NodeMCP
PythonMCP --> LLMs
NodeMCP --> LLMs
Agent --> Logfire
LLM_Response[("Response")] --> User
LLMs --> LLM_Response
# Run the Pydantic-AI multi-MCP example
uv run agents_mcp_usage/multi_mcp/multi_mcp_use/pydantic_mcp.py
# Run the multi-MCP evaluation
uv run agents_mcp_usage/multi_mcp/eval_multi_mcp/evals_pydantic_mcp.py
More details on multi-MCP implementation can be found in the multi_mcp README.
The Model Context Protocol allows applications to provide context for LLMs in a standardised way, separating the concerns of providing context from the actual LLM interaction.
Learn more: https://modelcontextprotocol.io/introduction
By defining clear specifications for components like resources (data exposure), prompts (reusable templates), tools (actions), and sampling (completions), MCP simplifies the development process and fosters consistency.
A key advantage highlighted is flexibility; MCP allows developers to more easily switch between different LLM providers without needing to completely overhaul their tool and data integrations. It provides a structured approach, potentially reducing the complexity often associated with custom tool implementations for different models. While frameworks like Google Agent Development Kit, LangGraph, OpenAI Agents, or libraries like PydanticAI facilitate agent building, MCP focuses specifically on standardising the interface between the agent's reasoning (the LLM) and its capabilities (tools and data), aiming to create a more interoperable ecosystem.
- Clone this repository
- Install required packages:
make install
- Set up your environment variables in a
.env
file:LOGFIRE_TOKEN=your_logfire_token GEMINI_API_KEY=your_gemini_api_key OPENAI_API_KEY=your_openai_api_key
- Run any of the sample scripts as shown in the examples above
Logfire is an observability platform from the team behind Pydantic that makes monitoring AI applications straightforward. Features include:
- Simple yet powerful dashboard
- Python-centric insights, including rich display of Python objects
- SQL-based querying of your application data
- OpenTelemetry support for leveraging existing tooling
- Pydantic integration for analytics on validations
Logfire gives you visibility into how your code is running, which is especially valuable for LLM applications where understanding model behaviour is critical.