Mezmo for AI agents
Mezmo is a log management platform that collects, processes, and analyzes telemetry data for engineering and operations teams monitoring production systems. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Mezmo.
Check ingestion status
Look up whether logs are flowing correctly into a pipeline, a read-only health check.
Search recent alert configurations
List preset alerts configured for a view to confirm on-call coverage is set up correctly before a release.
Approve before deleting a view
Require approval before deleting a saved view, since dashboards and alerts may reference it.
36 Mezmo actions, graded by risk.
Every Mezmo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
14Look things up. Allowed by default.
- mezmo.get_keyGet API Key
- mezmo.get_viewGet View Details
- mezmo.get_alertGet Preset Alert
- mezmo.list_keysList API Keys
- mezmo.get_memberGet Member
- mezmo.list_viewsList Views
- mezmo.list_alertsList Preset Alerts
- mezmo.get_categoryGet Category
- mezmo.list_membersList Members
- mezmo.list_pipelinesList Telemetry Pipelines
- mezmo.get_stream_configGet Stream Configuration
- mezmo.get_index_rate_alertGet Index Rate Alert Configuration
- mezmo.get_ingestion_statusGet Ingestion Status
- mezmo.get_ingestion_exclusionGet Ingestion Exclusion Rule
write
15Create and change things. Allow, or ask the user first.
- mezmo.create_keyCreate API Key
- mezmo.update_keyUpdate API Key
- mezmo.create_viewCreate View
- mezmo.update_viewUpdate Mezmo View
- mezmo.create_memberCreate Member Invitation
- mezmo.update_memberUpdate Member Role and Groups
- mezmo.create_categoryCreate Category
- mezmo.update_categoryUpdate Category
- mezmo.create_preset_alertCreate Preset Alert
- mezmo.update_preset_alertUpdate Preset Alert
- mezmo.update_index_rate_alertUpdate Index Rate Alert Configuration
- mezmo.create_ingestion_exclusionCreate Ingestion Exclusion Rule
- mezmo.update_ingestion_exclusionUpdate Ingestion Exclusion Rule
- mezmo.ingest_logsIngest Logs to Mezmo
- mezmo.resume_ingestionResume Log Ingestion
destructive
7Delete, cancel or archive. Ask first, or deny outright.
- mezmo.delete_keyDelete API Key
- mezmo.delete_viewDelete View
- mezmo.delete_memberDelete Organization Member
- mezmo.delete_categoryDelete Category
- mezmo.delete_preset_alertDelete Preset Alert
- mezmo.delete_pipeline_alertDelete Pipeline Alert
- mezmo.delete_ingestion_exclusionDelete Ingestion Exclusion
Mezmo in three steps.
- 01Your users connect MezmoThey add their Mezmo api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create API Key” can wait for the user, and “delete API Key” can be denied outright.
- 03Any agent can actYour agent calls Mezmo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('mezmo', { read: 'allow', write: 'ask', // create_key destructive: 'deny', // delete_key }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Mezmo connects.
Users add their Mezmo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Mezmo connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Mezmo from any agent.
Mezmo and Arc0, answered.
Can I use Mezmo with Claude, ChatGPT or Cursor?
Yes. Connect Mezmo to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Mezmo actions you allow.
How do users connect Mezmo?
Users add their Mezmo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Mezmo actions can my agent take?
36 in total: 14 read, 15 write and 7 destructive, such as “create API Key”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Mezmo?
Yes. Actions like “delete API Key” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Mezmo too?
Yes. The same Mezmo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Mezmo into your agent.
Your users connect Mezmo once, under your brand. Your agent gets 36 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan