Skip to content

Metronome MCP connector

The Metronome connector lets Claude, ChatGPT, Cursor, or any MCP client look up usage, manage billable metrics, credit types, customer alerts, and approval requests in Metronome, with each person signed in as themselves and every action logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Metronome to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Metronome once

  1. Open Connections, choose Add connection, and pick Metronome.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Metronome API key. One person generates a token in Metronome and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

metronome
Metronome
Billsby
Fanvue
Ordway
Paddle
Recharge
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Metronome MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Metronome MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Metronome MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Metronome to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Metronome through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Finance

    Check a customer's usage before month end

    Ask what a customer has consumed this period by seat or by group and get the figure straight from Metronome, without opening a dashboard or waiting on an export.

  • Revenue operations

    Review and approve pending approval requests

    Pull up every open approval request in Metronome, read the details, and approve or deny it in the same conversation so pricing changes stop waiting on someone to log in.

  • Billing operations

    Set up a new billable metric

    Describe the event you want to charge on and have the metric created in Metronome, or archive an old one once it is no longer used in any plan.

  • Customer success

    Reset a customer's spend alert after a call

    When a customer has been warned about a threshold and agreed a path forward, reset their alert in Metronome and confirm which alerts are still active on the account.

  • Product

    Define credit types for a new offering

    List the credit types already in Metronome, add one for a new product line, and archive types that belong to retired packaging.

  • Engineering

    Send test usage events and confirm they landed

    Ingest a handful of usage events into Metronome from a plain request, then look up the resulting usage to check the metric counts them the way you expect.

Try asking

  • “Summarize this month's approval requests pending in Metronome.”
  • “Which customers triggered billing alerts this week?”
  • “List billable metrics archived in the last 30 days.”

See all 139 Metronome tools below

Compare

Elaichi vs Zapier MCP vs Composio for Metronome

All three can connect Metronome to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Metronome, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Metronome tools Allow or restrict single Metronome tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Metronome call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Metronome tools for your AI agents

139 tools are ready to call through Elaichi's MCP endpoint the moment you connect Metronome, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Metronome gets you

6 screens from the product, each doing one job for your Metronome account.

The agent

Ask billing questions, get live answers.

Query Metronome usage, invoices and approvals in plain language and get answers from live records.

  • approval requests
  • alerts
  • billable metrics
  • customers

Ask Elaichi to work across your apps.

Summarize this month's approval requests pending in Metronome.

Which customers triggered billing alerts this week?

List billable metrics archived in the last 30 days.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint, every client, no shared keys.

Connect Claude, ChatGPT or Cursor to Metronome through one governed org endpoint.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

139 Metronome tools, zero custom code.

Every Metronome method, alert and billable metric is cataloged and ready to call.

  • List all Metronome approval requests
  • Create a Metronome approval request
  • Get single Metronome approval request by ID
  • Metronome approval requests approve
ElaichiTools
Tool Action Description
List all Metronome approval requests List List approval requests in Metronome submitted by agentic tokens, with optional status and creation-date filters. Returns: id, status, token_name, created_at, expires_at, approval_url, reviewed_by, reviewed_at, completed_at, approval_request_payload, response, name, description, method, path, body.
Create a Metronome approval request Create Submit a write operation for human approval in Metronome when an agentic token blocks the mutation. Returns the created approval request including id, status, approval_url, name, description, method, path, and body. Required: name, description, method, path, body.
Get single Metronome approval request by ID Get Get a single approval request in Metronome by id. Returns: id, status, token_name, created_at, expires_at, approval_url, reviewed_by, reviewed_at, completed_at, approval_request_payload, response, name, description, method, path, body. Required: id.
Metronome approval requests approve Approve Approve a pending approval request in Metronome, allowing the queued write operation to execute automatically. Returns: id, status, token_name, created_at, expires_at, approval_url, reviewed_by, reviewed_at, completed_at, approval_request_payload, response, name, description, method, path, body. Required: approval_request_id.
Create a Metronome approval request deny Create Deny a pending approval request in Metronome, preventing the queued write operation from executing and closing the request. Returns the updated approval request including id, status, token_name, approval_url, and approval_request_payload. Required: approval_request_id.

Toolboxes

Every team gets its own Metronome toolbox.

Scope billing, alerts and approval tools to the teams that actually need them.

  • Billing Ops
  • Revenue
  • Customer Success
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Billing Ops toolbox

Metronome · invoices and billing config

Metronome starter 18 Mar 4, 2026

Revenue toolbox

Metronome · billable metrics and pricing

— 9 Mar 2, 2026

Customer Success toolbox

Metronome · customer alerts and accounts

— 24 Feb 27, 2026

Finance toolbox

Metronome · approvals and reconciliation

Metronome starter 6 Feb 19, 2026

Engineering toolbox

Metronome · webhooks and API keys

— 31 Jan 30, 2026

Support toolbox

Metronome · alert resets and lookups

— 12 Jan 22, 2026

Shared connections

Delegated Metronome access, no shared credentials.

See who connected each Metronome account and how many teams and members use it.

  • Billing Prod
  • Finance NA
  • Support EMEA
  • Revenue Ops
ElaichiConnections
Connection Scope Status Access
ME

Metronome (Billing Prod)

Connected by Emily Carter

Personal • Active 1 team · 6 members
ME

Metronome (Finance NA)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
ME

Metronome (Support EMEA)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
ME

Metronome (Revenue Ops)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
ME

Metronome (Customer Success)

Connected by Ryan Hayes

Personal • Active Not shared
ME

Metronome (Engineering)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Metronome call, logged and attributable.

Track who did what in Metronome, when, and against which resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Metronome Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Metronome Approval requests Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Metronome Approval requests List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

Schedules trigger real Metronome work end to end.

A trigger fetches records, drafts a digest, a person approves, then it posts back to Metronome.

Metronome digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch approval requests

    Metronome

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Metronome

    Queued

Collections and dashboards

Metronome health, computed on a schedule.

Four metrics and a 14 day chart track Metronome records with no model involved.

Metronome health

Refreshed 4 minutes ago · every 15 minutes · from the approval requests collection

Live

Approval requests

1,284 ↓ 12%

Alerts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Approval requests created

Last 14 days

By team

Share of activity

Billing Prod 34%

Finance NA 27%

Support EMEA 21%

Revenue Ops 18%

FAQ

Frequently asked questions

How do I connect Metronome to Claude?

In Elaichi, open connectors, choose Metronome, and paste a Metronome API key when asked. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Metronome is ready to use.

Does Metronome work with ChatGPT and Cursor as well as Claude?

Yes. Once Metronome is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Metronome once and every client you use picks it up.

What can an AI agent actually do with my Metronome data?

With Metronome connected, an agent can look up a customer's usage by seat or by group, list and reset customer alerts, create or archive billable metrics and credit types, review approval requests and approve or deny them, send usage events, and manage billing settings such as Stripe configuration. Because Metronome offers well over a hundred actions, short concrete asks work best, for example "show open approval requests" rather than a long paragraph.

Does connecting Metronome give the AI access to everything in my billing setup?

No. Everything an agent does in Metronome runs under the API key the person connected, so it can only reach what that key is allowed to reach. Elaichi can narrow that further by blocking specific actions for a team, and it can never grant more than the Metronome key itself allows.

Can my team share one Metronome connection?

Yes. One person connects Metronome in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who looked up usage or approved a request in Metronome, not just which connection was used.

Can I stop an agent from deleting or changing things in Metronome?

Yes. Restrictions in Elaichi apply per action, so you can allow reading usage and alerts in Metronome while blocking archiving metrics, deleting Stripe billing configuration, or approving requests. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt can reach it.

What happens to a Metronome connection when someone leaves?

When you offboard a person in Elaichi, their access to Metronome through every client ends at once. A Metronome connection shared with a team keeps working for everyone else, and if you disconnect Metronome in Elaichi it disappears from Claude, ChatGPT, Cursor, and every other client in one step.

Does the Metronome MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Metronome is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Metronome?

Yes. Both let Claude, ChatGPT or Cursor use Metronome. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Metronome call.

How is Elaichi different from Composio for Metronome?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Metronome: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Metronome in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.