Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 5, 2026

Set Up MCP Integration

Connect MCP servers to extend Agent0 with custom tools and domain-specific capabilities.

Connect Model Context Protocol (MCP) servers to extend Agent0's capabilities with custom tools and domain-specific context providers.

Tip

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.

Configuration Steps

  1. Navigate to Settings → Integrations.
  2. Click + Add and select MCP.
  3. Provide a display name for the MCP server.
  4. Enter the MCP server URL (must be HTTP or HTTPS).
  5. Select authentication type:
    • None: No authentication required.
    • Bearer Token: Token-based authentication.
    • OAuth: OAuth 2.0 flow.
  6. If using bearer token, provide the token value.
  7. If using OAuth, click Connect to authorize.
  8. Optionally add custom HTTP headers.
  9. Click Save.
  10. Dash0 automatically discovers available tools from the server.
  11. Review discovered tools and enable the ones you want Agent0 to use.

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:

None

The MCP server does not require authentication. Use this for internal servers behind secure network boundaries.

Bearer Token

Token-based authentication using a bearer token:

  • Token: API token or access token (stored encrypted)
  • The token is sent in the Authorization: Bearer <token> header
Note

When editing an existing integration, leave the token field empty to keep the existing token unchanged.

OAuth 2.0

OAuth-based authentication flow:

  1. Click Connect to initiate the OAuth flow.
  2. A popup window opens to the MCP server's authorization page.
  3. Grant Dash0 access to the MCP server.
  4. The popup closes automatically upon successful authorization.
  5. OAuth tokens are automatically refreshed when they expire.

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 Information

Each tool displays:

  • Name: Tool identifier used by Agent0
  • Description: What the tool does and when to use it
  • Enabled Status: Whether Agent0 can invoke this tool
  • Annotations: Capability hints

Tool Annotations

MCP tools include annotations that indicate their capabilities:

  • Read-Only: Tool only reads data; it does not modify state.
  • Destructive: Tool modifies or deletes data; use with caution.
  • Idempotent: Tool can be safely called multiple times with the same result.
  • Open-World: Tool can access external resources or make outbound requests.

Enabling/Disabling Tools

  • Enable: Check the box to allow Agent0 to invoke this tool.
  • Disable: Uncheck the box to prevent Agent0 from using this tool.
  • Bulk Actions: Enable or disable multiple tools at once.

Manage the Integration

View MCP server status, update connection settings, and manage tool availability.

View Integration Status

Navigate to Settings → Integrations → MCP to view:

  • Connection Status: Whether the MCP server is reachable and responding.
  • Discovered Tools: List of tools exposed by the MCP server.
  • Authentication Status: OAuth token validity or bearer token status.
  • Recent Activity: List of recent Agent0 tool invocations.

Update Connection Settings

  1. Navigate to Settings → Integrations → MCP.
  2. Click Edit on the MCP server you want to modify.
  3. Update server URL, authentication, or headers.
  4. Click Save.
  5. Dash0 re-discovers tools from the updated server.

Removing the Integration

  1. Navigate to Settings → Integrations → MCP.
  2. Click Delete on the MCP server you want to remove.
  3. Confirm deletion.
  4. 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 Annotations: Check if the tool has annotations that restrict its usage.

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.
  • No Data Storage: Dash0 does not persistently store data returned by MCP tools.
  • Open-World Tools: Be cautious with tools that can access external resources beyond your organization.

Further Reading