​
Overview

MCPcat can integrate with your existing observability platforms, allowing you to monitor your MCP servers using familiar tools. You can use these integrations with or without an MCPcat account. When you configure exporters, the project_id parameter becomes optional: 
// Forward to OTLP without an MCPcat account
mcpcat.track(server, null, {
  exporters: {
    otlp: {
      type: "otlp",
      endpoint: "http://localhost:4318/v1/traces"
    }
  }
})

​
Supported Platforms

MCPcat currently supports integration with the following observability platforms:
  • OpenTelemetry (OTLP) - Connect to any OTLP-compatible backend (Jaeger, Tempo, New Relic, etc.)
  • Datadog - Send logs and metrics to Datadog
  • Sentry - Track errors and logs in Sentry

​
Using Multiple Integrations

You can configure multiple integrations to send events to different platforms simultaneously: 
mcpcat.track(server, "proj_YOUR_ID", {
  exporters: {
    otlp: {
      type: "otlp",
      endpoint: "http://localhost:4318/v1/traces"
    },
    datadog: {
      type: "datadog",
      apiKey: process.env.DD_API_KEY,
      site: "datadoghq.com",
      service: "my-mcp-server"
    },
    sentry: {
      type: "sentry",
      dsn: process.env.SENTRY_DSN,
      environment: "production"
    }
  }
})

​
Performance

Platform integrations are non-blocking and asynchronous. Integration failures are logged but won’t interrupt your MCP server’s operation or affect performance.