MCP (Model Context Protocol) Configuration

DeerFlow supports configurable MCP servers and skills to extend its capabilities, which are loaded from a dedicated extensions_config.json file in the project root directory.

Setup

Copy extensions_config.example.json to extensions_config.json in the project root directory.
bash
```
# Copy example configuration
cp extensions_config.example.json extensions_config.json
```
Enable the desired MCP servers or skills by setting "enabled": true.
Configure each server’s command, arguments, and environment variables as needed.
Restart the application to load and register MCP tools.

OAuth Support (HTTP/SSE MCP Servers)

For http and sse MCP servers, DeerFlow supports OAuth token acquisition and automatic token refresh.

Supported grants: client_credentials, refresh_token
Configure per-server oauth block in extensions_config.json
Secrets should be provided via environment variables (for example: $MCP_OAUTH_CLIENT_SECRET)

Example:

json

{
   "mcpServers": {
      "secure-http-server": {
         "enabled": true,
         "type": "http",
         "url": "https://api.example.com/mcp",
         "oauth": {
            "enabled": true,
            "token_url": "https://auth.example.com/oauth/token",
            "grant_type": "client_credentials",
            "client_id": "$MCP_OAUTH_CLIENT_ID",
            "client_secret": "$MCP_OAUTH_CLIENT_SECRET",
            "scope": "mcp.read",
            "refresh_skew_seconds": 60
         }
      }
   }
}

How It Works

MCP servers expose tools that are automatically discovered and integrated into DeerFlow’s agent system at runtime. Once enabled, these tools become available to agents without additional code changes.

Example Capabilities

MCP servers can provide access to:

File systems
Databases (e.g., PostgreSQL)
External APIs (e.g., GitHub, Brave Search)
Browser automation (e.g., Puppeteer)
Custom MCP server implementations

Learn More

For detailed documentation about the Model Context Protocol, visit:
https://modelcontextprotocol.io