Connect

The Connect pillar is where you wire data sources into axonpush and connect a coding agent. It has two tabs: Integrations and MCP.

Integrations

The Integrations page (/integrations) generates the credentials, endpoints, headers and copy-paste snippets for every way to get data in, from one place:

• SDK — Python, TypeScript and .NET clients, with framework integrations. See the SDK docs.
• OpenTelemetry (OTLP/HTTP) — point any collector or language exporter at axonpush. Logs go to /v1/logs, traces to /v1/traces; authenticate with X-API-Key: ak_… or X-Public-Token: pt_… (plus X-Axonpush-Environment and, for a public token, X-Axonpush-Channel). The page emits both a Collector .yaml block and the OTEL_EXPORTER_OTLP_* environment variables. See OTLP.
• Sentry DSN — repoint an existing Sentry client by changing one variable. See Sentry ingest.
• Webhooks — deliver every matching event to your own HTTPS endpoint, optionally signed with a shared secret.

MCP

Wire a coding agent to axonpush over the Model Context Protocol. Claude Code, Cursor, Claude Desktop and any other MCP client can provision an app and channel, hand your project an ingest key, and read the traces that land back, without leaving the editor.

The server lives at https://api.axonpush.xyz/mcp and is a projection of the REST API: every operation becomes a tool. Authenticate one of two ways:

• Browser OAuth through Better Auth — no token to paste. The client discovers the authorization server from the protected-resource metadata at https://api.axonpush.xyz/.well-known/oauth-protected-resource, then signs you in and consents on the dashboard.
• API key — point the client at the URL with an Authorization: Bearer ak_… header and skip OAuth entirely.

Open the MCP tab (or /connect-mcp), pick your client, and follow the prompt.

Related

• OTLP · Sentry ingest · SDK
• MCP guide, connecting each client and the safety model
• MCP reference, every tool, by category