Subscription Platform
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.
In Elaichi
Connect Metronome once
-
Open Connections, choose Add connection, and pick Metronome.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect Metronome to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Metronome to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Metronome to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
Audit log
Every Metronome call, logged and attributable.
Track who did what in Metronome, when, and against which resource.
- When
- Who
- What happened
- Type
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch approval requests
Metronome
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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 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.
Put Metronome in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.