Integrating Claude Cowork with Mavvrik

Introduction

When teams use Claude Cowork across an organization, usage can span many users, sessions, and workflows. Provider billing may show the total spend, but it does not always make it easy to understand who used Cowork, which sessions drove cost, what models were used, or how usage changed over time.

Mavvrik gives you that visibility.

Once Claude Cowork is connected, Mavvrik captures usage and cost data and shows it in Agentic cost and session views. Enterprise owners can review spend over time, inspect usage by user, analyze session-level activity, and understand which Cowork workflows are contributing to cost.

This guide gets you from registration to first visible Claude Cowork data in Mavvrik. You will add Claude Cowork in the Mavvrik dashboard, copy the generated credentials, configure them in the Claude admin console, and verify that data appears in Mavvrik.

Claude Cowork sends telemetry to Mavvrik through OpenTelemetry configuration in the Claude admin console.

Once integrated, you will mainly use two places in the dashboard: Cost for spend over time and Sessions for user and session-level inspection.

Step 1: Register Claude Cowork in the Mavvrik dashboard

Go to Admin → Accounts → Agents and click + Agent.

A right-side drawer opens with two tabs: Setup and Connect.

In the Setup tab, Mavvrik generates an Agent ID automatically. You can keep it or edit it during registration. It cannot be changed after registration.

Enter an Agent Name.

Use a clear name such as:

CODE

claude-cowork

or

CODE

company-claude-cowork

Add an optional description if needed.

Click Next to move to the Connect tab.

Step 2: Copy the Mavvrik credentials

In the Connect tab, copy the values generated by Mavvrik.

You will need these values when configuring Claude Cowork:

CODE

MVK_AGENT_ID
MVK_TENANT_ID
MVK_API_KEY

Keep these values available for the next step.

Do not change the generated Agent ID after this point. The Agent ID is used to associate Claude Cowork telemetry with the agent you registered in Mavvrik.

Step 3: Open Claude Cowork monitoring settings

Go to the Claude admin console.

Open:

CODE

Organization settings → Products → Cowork

Scroll to the Monitoring section.

Claude Cowork supports OpenTelemetry configuration from this section.

Step 4: Configure the OTLP endpoint

In the Monitoring section, enter the Mavvrik ingest endpoint.

Use this value:

CODE

https://ingest.mavvrik.ai

Enter it in the OTLP endpoint field.

Step 5: Set the OTLP protocol

Set OTLP protocol to:

CODE

http/json

This tells Cowork to send telemetry to Mavvrik using the expected OTLP HTTP JSON format.

Step 6: Add the Mavvrik OTLP headers

In the OTLP headers field, add the Mavvrik authentication header.

Use the tenant ID and API key copied from the Mavvrik Connect tab.

Format:

CODE

x-tenant-id={MVK_TENANT_ID},Authorization=Bearer {MVK_API_KEY}

Example:

CODE

x-tenant-id=your-tenant-id,Authorization=Bearer your-api-key

Do not include extra spaces before or after the comma.

Step 7: Add resource attributes

In the Resource attributes field, add the Mavvrik Agent ID.

Use this format:

CODE

mvk.agent_id={MVK_AGENT_ID},mvk_app_name=cowork

Example:

CODE

mvk.agent_id=your-agent-id,mvk_app_name=cowork

The mvk.agent_id value tells Mavvrik where to associate the Cowork telemetry.

The mvk_app_name=cowork value identifies the telemetry source as Claude Cowork.

Step 8: Save the monitoring configuration

Save the Cowork monitoring settings.

After saving, Cowork will send telemetry to Mavvrik using the configured OTLP endpoint, headers, protocol, and resource attributes.

If the Claude admin console shows a network egress allowlist message for ingest.mavvrik.ai, confirm that the domain is allowed.

Step 9: Generate Claude Cowork activity

After the monitoring settings are saved, ask one or more users to use Claude Cowork.

For first-time verification, use a known user and perform a simple Cowork workflow that includes at least one model interaction.

Mavvrik starts showing data after Cowork emits telemetry and the data is processed by Mavvrik.

Step 10: Verify the integration in Mavvrik

After running a test workflow, go to: Home → Agentic → Cost

Confirm that Claude Cowork activity appears for the agent you registered.

You should be able to see Cowork cost and usage over time.

Review fields such as: User, User email, Model, Operation, etc

Then go to: Home → Agentic → Sessions

Search or filter by the user who performed the test.

Open a session and confirm that the expected Cowork activity appears.

Review fields such as: Session ID, User, User email, Duration, Tokens, LLM calls, Tool calls, Cost etc.

Troubleshooting

No data in the Mavvrik dashboard

Confirm that the Cowork monitoring settings were saved successfully.

Check that the following values are configured:

CODE

OTLP endpoint=https://ingest.mavvrik.ai
OTLP protocol=http/json
OTLP headers=x-tenant-id={MVK_TENANT_ID},Authorization=Bearer {MVK_API_KEY}
Resource attributes=mvk.agent_id={MVK_AGENT_ID},mvk_app_name=cowork

Also confirm that the Mavvrik header value is formatted correctly:

CODE

x-tenant-id={MVK_TENANT_ID},Authorization=Bearer {MVK_API_KEY}

There should be no extra spaces before or after the comma.

Data appears under the wrong agent

Check the Resource attributes value.

It should contain the Agent ID copied from the Mavvrik agent you registered for Claude Cowork:

CODE

mvk.agent_id={MVK_AGENT_ID}

If this value is missing or incorrect, Mavvrik may not associate the telemetry with the expected agent.

User or session details are missing

Cowork telemetry must include the relevant user and session attributes for Mavvrik to show user and session-level breakdowns.

If cost appears but user or session details are incomplete, confirm that Cowork monitoring is enabled and that users generated activity after the configuration was saved.

Cost looks lower than expected

Confirm that Cowork activity was generated after the monitoring settings were saved.

Only telemetry emitted after the configuration is active will appear in Mavvrik.

Also check that the test workflow included model activity. Workflows without model usage may not produce the expected cost records.

The OTLP endpoint cannot be reached

Confirm that the endpoint is entered exactly as:

CODE

https://ingest.mavvrik.ai

If your organization controls outbound network access, confirm that ingest.mavvrik.ai is allowed for Cowork telemetry export.

Final checklist

Before calling the integration complete:

[ ] Claude Cowork is registered as an agent in Mavvrik
[ ] MVK_AGENT_ID was copied from the Mavvrik Connect tab
[ ] MVK_TENANT_ID was copied from the Mavvrik Connect tab
[ ] MVK_API_KEY was copied from the Mavvrik Connect tab
[ ] Claude Cowork Monitoring settings were opened in the Claude admin console
[ ] OTLP endpoint is set to https://ingest.mavvrik.ai
[ ] OTLP protocol is set to http/json
[ ] OTLP headers include the Mavvrik tenant ID and API key
[ ] Resource attributes include mvk.agent_id and mvk_app_name=cowork
[ ] The monitoring settings were saved successfully
[ ] A test Cowork workflow was run
[ ] Activity is visible in Home → Agentic → Cost
[ ] Session-level activity is visible in Home → Agentic → Sessions

Configuration reference

Use these values when setting up Claude Cowork monitoring for Mavvrik:

CODE

OTLP endpoint
https://ingest.mavvrik.ai

CODE

OTLP protocol
http/json

CODE

OTLP headers
x-tenant-id={MVK_TENANT_ID},Authorization=Bearer {MVK_API_KEY}

CODE

Resource attributes
mvk.agent_id={MVK_AGENT_ID},mvk_app_name=cowork