Skip to main content
Telara

Integrations / Claude Code

Claude Code logo

Claude Code

Claude Code (Anthropic CLI) telemetry ingested via OpenTelemetry. Customers set CLAUDE_CODE_ENABLE_TELEMETRY=1 and point OTEL_EXPORTER_OTLP_ENDPOINT at mcp-gateway's OTLP receiver. Each LLM request span / log record is feeded through the same engine pipeline (billing → ratelimit → compliance → audit) as MCP tool calls. Reference: https://code.claude.com/docs/en/monitoring-usage

OTLP
Spend
AI estate
Actions

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI YesRuns actions YesReal-time events No

Before you connect

Prerequisites

Claude Code running where you can turn on telemetry.
Ability to run the Telara CLI on the machine (or CI) that should emit usage.

Vendor setup

Get the credential

1
Print the OTLP endpoint
Run `telara otlp`. It prints the endpoint and headers Telara expects. Do not paste an Anthropic API key on Connect — this connector is telemetry, not an admin key.
2
Point Claude Code at it
Enable Claude Code telemetry in the vendor product and send OpenTelemetry to that endpoint.

In Telara

Connect in Telara

OTLP

This connector does not take a vendor key in Settings → Integrations. Run `telara otlp` (or point the vendor’s OpenTelemetry exporter at the endpoint that command prints) so usage arrives as telemetry.

Telara has not published the exact form fields for this method yet. Complete whatever the Connect dialog shows.

API key

Anthropic Admin API key (sk-ant-admin01-...), created in Console > Settings > Organization > Admin API keys. Required for the Claude Code Analytics API. Auth shape verified at https://platform.claude.com/docs/en/manage-claude/claude-code-analytics-api

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API key

Spend

What gets measured

Resolution: Not published.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • input_tokens
    tokens
  • output_tokens
    tokens
  • cache_read_tokens
    tokens
  • cache_creation_tokens
    tokens
  • session_count
    count
  • lines_of_code_modified
    count
  • pull_requests_created
    count
  • commits_created
    count

AI estate

What gets discovered

Config paths
  • ~/.claude.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • .mcp.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Config paths
  • /Library/Application Support/ClaudeCode/managed-mcp.json
  • /etc/claude-code/managed-mcp.json
  • C:\ProgramData\ClaudeCode\managed-mcp.json
Resource kinds

mcp_client_configuration, mcp_server_deployment

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Nothing appears in Telara until a Claude Code session actually emits telemetry.
This is not the Anthropic Admin connector. Org-level Anthropic spend uses Anthropic Admin.