How to connect Mezmo to Claude

Connect Claude Web, Desktop and Cowork to Mezmo MCP. Send application error logs to mezmo, delete outdated pipeline alert for a component, and more using natural language, with authentication handled for you.

Mezmo logoMezmo
Api Key

Mezmo is a unified platform for log management and telemetry data processing. It helps you collect, analyze, and manage log data for better operational visibility.

36 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Mezmo account to Claude via Composio Connect, enabling it to send application error logs to Mezmo, delete outdated pipeline alert for a component, ingest security event logs from last hour, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Mezmo with

Connecting Mezmo to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Mezmo account

Back in Claude, ask it to connect to Mezmo or give it any Mezmo-related task.

For example, ask Claude to:

  • "Send application error logs to Mezmo"
  • "Delete outdated pipeline alert for a component"
  • "Ingest security event logs from last hour"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Mezmo account is ready to use.

What is the Mezmo Claude Connector, and what's possible with it?

The Mezmo MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, and more directly to your Mezmo account. It provides structured and secure access to your log management and telemetry pipelines, so your agent can ingest logs, manage pipeline alerts, streamline monitoring, and automate log-driven workflows on your behalf.

  • Automated log ingestion: Seamlessly send structured log events from any host or service to Mezmo for real-time analysis and monitoring.
  • Pipeline alert deletion: Direct your agent to remove specific alerts tied to components in your pipelines, helping manage noise and maintain alert hygiene.
  • Streamlined alert management: Enable your agent to clean up outdated or redundant alerts, keeping your pipeline monitoring focused and actionable.
  • Real-time telemetry processing: Let your agent push telemetry data instantly for advanced analytics, troubleshooting, and observability workflows.

Troubleshooting

1. Why does Claude not use the Composio connector for Mezmo?

The connector can show as connected, but Claude must use it in each Mezmo conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Mezmo again.

2. Why does Claude show an MCP server error before Mezmo connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Mezmo.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Mezmo.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Mezmo authorization link not work?

The Composio connector is one server. Your Mezmo account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Mezmo connection.
  • Composio creates a fresh Mezmo authorization link.
  • Open that link in your browser and finish the Mezmo sign-in.

4. Why do Mezmo actions fail after they worked before?

The Mezmo connection can expire or lose permission.

  • Ask Claude to inspect the Mezmo connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Mezmo account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Mezmo.
  • If the action still fails with a permission error, check that the connected account has that permission in Mezmo itself.

5. How do I switch to a different Mezmo account?

Claude can manage the Mezmo connection for you.

  • Ask Claude to disconnect or delete the current Mezmo account.
  • Ask Claude to connect Mezmo again.
  • Open the new Composio authorization link for Mezmo.
  • Sign in with the other Mezmo account in the browser.
  • After the account connects, ask Claude to retry the Mezmo task.

6. Why is my Mezmo connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Mezmo connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If Mezmo tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Mezmo.
TOOLS

Supported Tools

Every Mezmo action and event your agent gets out of the box.

Create Category

Tool to create a new category for views, boards, or screens in Mezmo.

Create Ingestion Exclusion Rule

Tool to create an exclusion rule for log ingestion to control costs.

Create API Key

Tool to create a new API key (ingestion or service key) in Mezmo.

Create Member Invitation

Tool to invite a new member to the Mezmo organization with a specified role.

Create Preset Alert

Tool to create a new preset alert in Mezmo with specified name and notification channels.

Create View

Tool to create a new Mezmo view with filtering and alert configuration.

Delete Category

Tool to delete a category by its type and ID.

Delete Ingestion Exclusion

Tool to remove an ingestion exclusion rule by its ID.

Delete API Key

Tool to delete an API key by its unique identifier.

Delete Organization Member

Tool to remove a member from the organization by their email address.

Delete Pipeline Alert

Tool to delete an alert for a specific component within a pipeline.

Delete Preset Alert

Tool to delete a preset alert by its ID.

Delete View

Tool to delete a view by its ID.

Get Preset Alert

Tool to retrieve details of a specific preset alert by its ID.

Get Category

Tool to retrieve a category configuration by its type and ID.

Get Index Rate Alert Configuration

Tool to retrieve current index rate alert settings for the Mezmo account.

Get Ingestion Exclusion Rule

Tool to retrieve an ingestion exclusion rule by its ID.

Get Ingestion Status

Tool to get the current ingestion status for the Mezmo account.

Get API Key

Tool to retrieve an API key configuration by its ID.

Get Member

Tool to retrieve member information by their ID.

Get Stream Configuration

Tool to retrieve the current event streaming configuration for the Mezmo account.

Get View Details

Tool to retrieve details of a specific view by its ID.

Ingest Logs to Mezmo

Ingest log lines into Mezmo Log Analysis.

List Preset Alerts

Tool to list all preset alerts configured for the Mezmo account.

List API Keys

Tool to list all API keys and ingestion keys configured for the account.

List Members

Tool to list all team members in the Mezmo account configuration.

List Telemetry Pipelines

Tool to list all telemetry pipelines configured for the account.

List Views

Tool to list all views configured for the account.

Resume Log Ingestion

Tool to resume log ingestion for the account after it has been stopped.

Update Category

Tool to update a category name by its type and ID.

Update Index Rate Alert Configuration

Tool to configure index rate alerting settings including thresholds and notification channels.

Update Ingestion Exclusion Rule

Tool to update an existing exclusion rule by its ID.

Update API Key

Tool to update an API key name by its ID.

Update Member Role and Groups

Tool to update a member's role and group assignments by their email address.

Update Preset Alert

Tool to update an existing preset alert by ID.

Update Mezmo View

Tool to update an existing Mezmo view by its ID.

FAQ

Frequently asked questions

With a standalone Mezmo MCP server, the agents and LLMs can only access a fixed set of Mezmo tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Mezmo and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Mezmo tools.

Yes, absolutely. You can configure which Mezmo scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Mezmo data and credentials are handled as safely as possible.

Start with Mezmo.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Mezmo tool your agent needs.Free to start.

Start building