Overview
AgentCat 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 AgentCat account. When you configure exporters, theproject_id parameter becomes optional:
'' as the project ID for telemetry only (null reads AGENTCAT_PROJECT_ID), and each exporter as an object of AgentCat\Exporters: OtlpExporter, DatadogExporter, SentryExporter or PostHogExporter, whose named arguments are the fields of its page.
In C#, pass "" as the project ID for telemetry only (null reads AGENTCAT_PROJECT_ID), and add each exporter to options.Exporters under a name of your choice: an OtlpExporter, DatadogExporter, SentryExporter or PostHogExporter of the AgentCat namespace. The required fields of its page are the constructor arguments, and the optional fields are properties.
The Rust SDK has no exporters yet, so the integrations on these pages have no Rust tab.
Supported Platforms
AgentCat 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
- PostHog - Send product analytics events to PostHog
Using Multiple Integrations
You can configure multiple integrations to send events to different platforms simultaneously:track() of a process that passes exporters sets them up for every server it tracks; the Laravel and Symfony bridges take them as arrays in their configuration.
In C#, the first WithAgentCat() or Track() of a process that adds exporters sets them up for every server of the process, in the order you added them. AgentCat ignores the exporters of later installs. An empty Exporters sets nothing up, so a later install can still add exporters. C# exporters lists the other C# rules.