MCP Tool Integration
The Model Context Protocol (MCP) integration lets you connect external tool servers to DocsGPT. Your agents can then discover and call tools provided by those servers during conversations — for example, querying a CRM, running code, or accessing a database.
Setup
Step 1: Configure Environment Variables (Optional)
Only needed if your MCP servers use OAuth authentication:
MCP_OAUTH_REDIRECT_URI=https://yourdomain.com/api/mcp_server/callbackIf not set, falls back to API_URL/api/mcp_server/callback.
Step 2: Add an MCP Server
Go to Settings > Tools > Add Tool > MCP Server. Enter the server URL, select an auth type, and click Test Connection to verify, then Save.
Step 3: Enable for Your Agent
In your agent configuration, enable the MCP tools you want the agent to use.
Authentication Types
| Auth Type | Config Fields |
|---|---|
| None | — |
| Bearer | bearer_token |
| API Key | api_key, api_key_header (default: X-API-Key) |
| Basic | username, password |
| OAuth | oauth_scopes (optional) |
For OAuth in production, MCP_OAUTH_REDIRECT_URI must be a publicly accessible URL pointing to your DocsGPT backend.
API Endpoints
| Endpoint | Method | Description |
|---|---|---|
/api/mcp_server/test | POST | Test a connection without saving |
/api/mcp_server/save | POST | Save or update a server configuration |
/api/mcp_server/callback | GET | OAuth callback handler |
/api/mcp_server/oauth_status/<task_id> | GET | Poll OAuth flow status |
/api/mcp_server/auth_status | GET | Batch check auth status for all MCP tools |
Troubleshooting
- Connection refused — Verify the URL and that the server is reachable from your backend.
- 403 Forbidden — Check credentials and permissions.
- Timed out — Default is 30s; increase timeout in tool config (max 300s).
- OAuth “needs_auth” persists — Verify
MCP_OAUTH_REDIRECT_URIis correct and Redis is running.