Deep Agent now supports Model Context Protocols (MCPs), enabling seamless integration with external tools and data sources. MCP standardizes how AI agents interact with resources, making it easier to enhance Deep Agent's capabilities with real-time data, APIs, and services. This guide walks you through setting up and using MCPs in Deep Agent to create powerful, context-aware AI workflows.
The Model Context Protocol (MCP) is an open standard that connects AI models, like those in Deep Agent, to external systems via a client-server architecture. Think of MCP as a universal connector, allowing Deep Agent to access tools (e.g., GitHub, databases) and resources (e.g., files, APIs) without custom integrations. With MCP, you can enable Deep Agent to perform tasks like querying databases, fetching web content, or automating workflows.
Note: You can find a list of community-built MCP servers at Piperdream, GitHub and mcp.so. The MCP directory platforms will guide you on how to obtain the necessary tokens or API keys to configure your servers. Platforms like Pipedream support OAuth-based remote servers, making them easier to set up—so you can pick your favorite MCPs from there and get started quickly.
command
, args
, env
, etc."command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"], etc.
The example below shows the JSON configuration for two MCP servers: GitHub and Google Tasks.
github
and google_tasks
).{
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
},
"google_tasks": {
"url": "<REMOTE_SERVER_URL>"
}
}
{
"mcpServers": {
"<your server config json>"
}
}
Yes, Deep Agent supports adding up to 5 servers and supports up to 50 tools across the servers. Add each server in the Integrations settings, but limit active tools to avoid overwhelming the LLM.
Use MCP servers from trusted sources only and try to follow OAuth authentication in remote servers.