Last updated:
Set Up MCP Integration
Connect Model Context Protocol (MCP) servers to extend Agent0's capabilities with custom tools and domain-specific context providers.
To create an MCP integration, navigate to Settings → Integrations, click + Add, and select MCP from the integration type list.
What is MCP?
Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data sources. MCP servers expose tools and context that AI models can use to perform actions and access information beyond their training data.
Use Cases
- Internal APIs: Connect Agent0 to internal APIs for querying business data.
- Custom Databases: Access proprietary databases or data warehouses.
- External Services: Integrate with third-party services not natively supported by Dash0.
- Domain Knowledge: Provide specialized context about your infrastructure, architecture, or business logic.
Prerequisites
Before setting up an MCP integration:
- MCP server endpoint (HTTP/HTTPS)
- Organization administrator role in Dash0
- MCP server credentials (if authentication is required)
Setup
Connect an MCP server to Dash0 to make custom tools available to Agent0.
Find a server in the HubRelease historyThis feature was introduced by MCP Catalogue on June 15, 2026.
Open the Hub and select Agent0 MCPs to browse available servers. Search for the service you want, open its entry, and click Connect.
What happens next depends on the server's authentication method and connection status:
- For an OAuth server with a single URL, Dash0 starts authorization directly.
- For other servers, Dash0 opens the MCP integration form. Where the catalog supplies a URL, the name, URL, and authentication type are pre-filled. Choose the appropriate endpoint when the service offers multiple regions, and supply any required credentials.
- If the server is already connected, Configure opens its existing integration instead.
Review the server's tools after connecting. You can still configure a server manually when it is not in the catalog.
Configuration Steps
- Navigate to Settings → Integrations.
- Click + Add and select MCP.
- Provide a display name for the MCP server.
- Enter the MCP server URL (must be HTTP or HTTPS).
- Select authentication type:
- No Authentication: No authentication required.
- Basic Authentication: Username and password or encoded credentials.
- Token Authentication: A token with the Bearer or ApiKey scheme.
- OAuth: OAuth 2.0 authorization.
- For Basic or Token authentication, enter the credentials described below.
- For OAuth, click Connect to authorize. If Dash0 requests manual client setup, follow Manual OAuth client setup.
- Optionally add custom HTTP headers.
- Click Validate to discover tools using the connection details in the form. OAuth authorization also loads tools after connecting.
- Review discovered tools and use their switches to enable the ones you want Agent0 to use.
- Click Save to save the integration and tool selection.
Configuration
Configure MCP server connection settings, authentication, and tool selection.
Display Name
Provide a descriptive name for the MCP server. This name helps identify the server in Agent0's tool selection interface.
Server URL
The HTTP/HTTPS endpoint of the MCP server. The URL must point to a valid MCP server that implements the Model Context Protocol specification.
Authentication
Choose the appropriate authentication method for your MCP server:
No Authentication
Select this only if the MCP server does not require authentication.
Basic Authentication
Select a Credential type:
- Username & password: Enter Username and Password. A username is required.
- Encoded credentials: Paste the encoded value after
Basicin an existing authorization header into Encoded credentials.
Dash0 sends the credentials using the Authorization: Basic <encoded-credentials> header.
Token Authentication
Select Bearer or ApiKey under Token type, then enter the credential in Token. Dash0 sends Authorization: Bearer <token> or Authorization: ApiKey <token> respectively. Bearer is the default.
When editing an existing integration, leave the token field empty to keep the existing token unchanged. If you change Token type, re-enter the token so Dash0 can save it with the new scheme.
OAuth 2.0Release historyThis feature was introduced by MCP OAuth Support on June 15, 2026.
OAuth-based authentication flow:
To authorize Dash0 to access an OAuth-enabled MCP server:
- Click Connect to initiate the OAuth flow.
- A popup window opens to the MCP server's authorization page.
- Grant Dash0 access to the MCP server.
- The popup closes automatically upon successful authorization.
- OAuth tokens are automatically refreshed when they expire.
Manual OAuth client setup
If the server requires a manually registered OAuth client, Dash0 displays additional fields after you click Connect. These fields also appear when you edit an integration that already uses manual registration.
- Register an OAuth client with the server's identity provider. Add the exact Redirect URI displayed by Dash0 to the client's allowed redirect URIs.
- Enter the registered Client ID in Dash0.
- If the provider issued a client without a secret, enable Public client (PKCE only). Otherwise, enter the Client secret.
- If Dash0 requests Authorization endpoint and Token endpoint, enter their URLs from the identity provider.
- Click Save & connect, then complete authorization in the popup.
Changes to manual OAuth client settings take effect through Save & connect, not the page's Save action.
Custom Headers
Add custom HTTP headers to MCP server requests:
- Header Name: HTTP header name
- Header Value: Header value (marked as secret if sensitive)
Use custom headers for:
- Additional authentication mechanisms
- Request routing or versioning
- Custom metadata
Tool Management
After connecting, review the discovered tools and control which ones Agent0 can use.
Tool groups and switches
The Tools section shows each tool's name and an enable switch. Tools are grouped into read-only and write/destructive groups. Use a tool's switch to enable or disable it, or the group's Enable all switch to change the whole group. Click Save to persist your selection.
The grouping uses the server's readOnlyHint annotation. Only tools with readOnlyHint: true appear in the read-only group; all others appear in the write/destructive group. These annotations are server-supplied hints, not permission checks or a guarantee that a tool is safe.
Discovery results and errors
Dash0 discovers tools when you open an existing integration and after saving connection changes. If discovery fails and a saved tool list is available, Dash0 displays that list with a warning that it may be stale. If no tools are available to display, it shows a load error and any error details returned by the server.
If the server returns no tools but Dash0 has a saved list, Dash0 keeps that list and shows a separate empty-list warning. A discovery failure or empty response does not erase the saved tools.
Manage the Integration
View MCP server status, update connection settings, and manage tool availability.
View Integration Status
Open the MCP integration in Settings → Integrations to review its connection settings, authentication, custom headers, and discovered tools. OAuth connections show whether authorization is connected. This page does not provide a bearer-token health indicator or a recent-invocation activity list. Discovery failures appear in the Tools section as described above.
Update Connection Settings
- Navigate to Settings → Integrations → MCP.
- Click Edit on the MCP server you want to modify.
- Update server URL, authentication, or headers.
- Click Save.
- Dash0 re-discovers tools from the updated server.
Removing the Integration
- Navigate to Settings → Integrations → MCP.
- Click Delete on the MCP server you want to remove.
- Confirm deletion.
- Agent0 can no longer invoke tools from this MCP server.
Troubleshooting
Common issues with MCP integrations and their solutions.
Connection Failed
- Server URL: Verify the MCP server URL is correct and accessible.
- Network Access: Ensure Dash0 can reach the MCP server endpoint (check firewall rules).
- Authentication: Verify bearer token or OAuth credentials are correct.
- Server Status: Check that the MCP server is running and responding.
Tools Not Discovered
- MCP Protocol: Verify the server implements the Model Context Protocol specification correctly.
- Tool Listing: Check that the MCP server exposes tools via the protocol's discovery endpoint.
- Server Logs: Review MCP server logs for errors during tool discovery.
Agent0 Cannot Invoke Tool
- Tool Enabled: Verify the tool is enabled in the MCP integration settings.
- Authentication: Check that authentication tokens are valid and not expired.
- Tool Permissions: Verify the authenticated user has permission to invoke the tool.
- Tool Group: Check both groups. Tools without an explicit read-only hint appear in the write/destructive group; the annotation itself does not restrict invocation.
Security
MCP integration security relies on encrypted credentials, access control, and audit logging.
Credential Security
- Encrypted Storage: Bearer tokens and OAuth credentials are encrypted at rest.
- Automatic Refresh: OAuth tokens are automatically refreshed before expiration.
- Secret Headers: Custom headers marked as secrets are encrypted and not visible in logs.
- Audit Trail: All MCP tool invocations from Agent0 are logged in Dash0 audit logs.
Access Control
- Tool Enablement: Only explicitly enabled tools can be invoked by Agent0.
- Read-Only Tools: Prefer read-only tools for safer Agent0 interactions.
- Destructive Tools: Carefully review tools marked as destructive before enabling them.
Data Privacy
- Tool Invocation Context: Agent0 only sends data relevant to the current investigation to MCP tools.
- Conversation History: MCP tool results can be stored in Agent0 conversation history. See the Dash0 Security and Compliance Overview for retention periods. Model-provider zero-retention terms are separate from Dash0's storage of conversation history.
- Open-World Tools: Be cautious with tools that can access external resources beyond your organization.
Further Reading
- Use MCP in Chat and Automations — How Agent0 uses MCP tools
- Model Context Protocol — Official MCP specification and documentation
- Integrations — All available Dash0 integrations
- Key Concepts — Reference terminology and mental model