Mezmo

Mezmo MCP integration

Checks ingestion status, builds filtered views and preset alerts, writes exclusion rules to hold down index cost, and rotates API keys and member roles.

36actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Ingest logs to mezmo

    Lyro sends log lines directly into Mezmo Log Analysis for centralized monitoring. Support teams can route customer support logs to Mezmo without manual setup, keeping critical events visible in one place.

  • Create preset alert

    Lyro creates a new preset alert in Mezmo with specified notification channels. Teams can automatically notify the right people when issues are detected, reducing response time.

  • Get ingestion status

    Lyro retrieves the current log ingestion status for a Mezmo account. Support agents can verify that logs are flowing correctly and diagnose ingestion problems immediately.

See all 36 actions

How businesses use Mezmo + Lyro

Each card is one request a support team gets, and the Mezmo actions Lyro runs to close it.

  • Answer what the logging setup is doing

    Lyro checks whether ingestion is active or paused, lists the saved views the team works from, and opens one to read its query and filters, so a question during an incident does not need a console.

    Get Ingestion StatusList ViewsGet View Details
  • Stand up a view and the alert on it

    Lyro creates a view filtered by query, host, app, level, or tag, attaches email, PagerDuty, or webhook channels to it, and registers the preset alert that fires against those conditions.

    Create ViewCreate Preset AlertUpdate Preset Alert
  • Keep noisy logs out of the index

    Lyro writes an exclusion rule that stops debug or test-environment logs being ingested, adjusts the query on an existing rule, and removes one that has outlived its purpose.

    Create Ingestion Exclusion RuleUpdate Ingestion Exclusion RuleDelete Ingestion Exclusion
  • Rotate keys and adjust who has access

    Lyro provisions an ingestion or service key, revokes one that leaked, and changes a member's role and group assignments by their email address without touching the rest of their settings.

    Create API KeyDelete API KeyUpdate Member Role and Groups

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Mezmo actions it has and picks the ones a request needs.

  1. 01

    Connect Mezmo

    Authorize the Mezmo account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Mezmo actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Mezmo · Lyro

Everything else about Mezmo

Setup, permissions, and the limits of what Lyro can do inside Mezmo.

  • It can only report on it. Get Stream Configuration returns the current streaming settings and returns error details when streaming is unavailable on the account or plan, so Lyro names the plan as the blocker instead of failing quietly.

Every action available in Mezmo

All 36 actions your agent can call on Mezmo, straight from the live MCP connection.

  • Create category

    Create a new category for views, boards, or screens in Mezmo.

  • Create ingestion exclusion rule

    Create an exclusion rule for log ingestion to control costs.

  • Create API key

    Create a new API key (ingestion or service key) in Mezmo.

  • Create member invitation

    Invite a new member to the Mezmo organization with a specified role.

  • Create preset alert

    Create a new preset alert in Mezmo with specified name and notification channels.

  • Create view

    Create a new Mezmo view with filtering and alert configuration.

  • Delete category

    Delete a category by its type and ID.

  • Delete ingestion exclusion

    Remove an ingestion exclusion rule by its ID.

  • Delete API key

    Delete an API key by its unique identifier.

  • Delete organization member

    Remove a member from the organization by their email address.

  • Delete pipeline alert

    Delete an alert for a specific component within a pipeline.

  • Delete preset alert

    Delete a preset alert by its ID.

  • Delete view

    Delete a view by its ID.

  • Get preset alert

    Retrieve details of a specific preset alert by its ID.

  • Get category

    Retrieve a category configuration by its type and ID.

  • Get index rate alert configuration

    Retrieve current index rate alert settings for the Mezmo account.

  • Get ingestion exclusion rule

    Retrieve an ingestion exclusion rule by its ID.

  • Get ingestion status

    Get the current ingestion status for the Mezmo account.

  • Get API key

    Retrieve an API key configuration by its ID.

  • Get member

    Retrieve member information by their ID.

  • Get stream configuration

    Retrieve the current event streaming configuration for the Mezmo account.

  • Get view details

    Retrieve details of a specific view by its ID.

  • Ingest logs to mezmo

    Ingest log lines into Mezmo Log Analysis.

  • List preset alerts

    List all preset alerts configured for the Mezmo account.

  • List API keys

    List all API keys and ingestion keys configured for the account.

  • List members

    List all team members in the Mezmo account configuration.

  • List telemetry pipelines

    List all telemetry pipelines configured for the account.

  • List views

    List all views configured for the account.

  • Resume log ingestion

    Resume log ingestion for the account after it has been stopped.

  • Update category

    Update a category name by its type and ID.

Ready to connect Mezmo?

Authorize the account and your agent has all 36 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot