Skip to content

Connectors · Accounting & finance

Metronome MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Metronome and the rest of your systems. It gives your agent 117 Metronome actions (54 reads, 47 writes and 16 that wait for a confirmation) and holds the Metronome credential itself, so the agent never does. It paces Metronome's limits and records every call.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "metronome.products.list",  intent: "check which Metronome account is connected"}# List products · read · 1 upstream call
  • 117actionsin one signed file
  • 54readlook, never change
  • 47writecreate and update
  • 16wait for a yesdestructive, confirmed first

Set up

Connect Metronome in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Metronome.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyMetronome API token
    account { op: "connections.requirements", service: "metronome" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "metronome.products.list" }# list products · read · 1 upstream callcheck { action: "metronome.products.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Metronome at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
100 calls a second, per connection
API covered
Metronome API v1/v2 (OpenAPI 3, Stainless SDK specification)api.metronome.com
Built from
Metronome's documentation, read 23 October 2026storage.googleapis.comGitHubdocs.metronome.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
52 of 54 reads, for up to 5 minutes; a write clears what it affects
Shared entities
4, so ask can line Metronome up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Metronome.

117 actions in 21 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 54readlook, never change
  • 47writecreate and update
  • 16destructivewait for a confirmation
  1. Contracts

    20

    10 read · 9 write · 1 destructive

    List a customer's contracts · Create a contract · Get a contract · Archive a contract

  2. Customers

    18

    8 read · 7 write · 3 destructive

    List customers · Create a customer · Get a customer · Archive a customer

  3. Rate cards

    13

    5 read · 7 write · 1 destructive

    Create a rate card · List rate cards · Get a rate card · Update a rate card

  4. Invoices

    6

    3 read · 1 write · 2 destructive

    List a customer's invoices · Get an invoice · Void an invoice · Add a one-time charge to a plan invoice

  5. Notifications

    6

    3 read · 2 write · 1 destructive

    Create a notification configuration · Get a notification configuration · Archive a notification configuration · List offset notification configurations

  6. Billable metrics

    5

    2 read · 2 write · 1 destructive

    Create a billable metric · List billable metrics · Get a billable metric · Rename a billable metric

  7. Credit grants

    5

    2 read · 2 write · 1 destructive

    Create a credit grant · List credit grants · Edit a credit grant · List credit ledger entries

  8. Custom fields

    5

    1 read · 2 write · 2 destructive

    Add a custom field key · List custom field keys · Delete custom field values from an entity · Remove a custom field key

13 more areas · 39 actions
  • Packages 5
  • Products 5
  • Commits 4
  • Credits 4
  • Usage 4
  • Balances 3
  • Customer alerts 3
  • Pricing units 3
  • Settings 3
  • Alerts 2
  • Audit logs 1
  • Dashboards 1
  • Services 1

Top actions

The Metronome API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 13 of Metronome's 13 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
metronome.products.listList productsList products.readcommerce.product.list112 connectors
metronome.customers.listList customersList customers.readcrm.company.list162 connectors
metronome.products.createCreate a productCreate a product.writecommerce.product.create92 connectors
metronome.invoices.listList a customer's invoicesList a customer's invoices.readfinance.invoice.list101 connectors
metronome.customers.createCreate a customerCreate a customer.writecrm.company.create142 connectors
metronome.contracts.listList a customer's contractsList a customer's contracts.readservice.contract.list23 connectors
metronome.invoices.getGet an invoiceGet an invoice.readfinance.invoice.get102 connectors
metronome.contracts.createCreate a contractCreate a contract.writeservice.contract.create19 connectors
metronome.invoices.voidVoid an invoiceVoid an invoice.destructivefinance.invoice.void22 connectors
metronome.usage.listGet batched usage for billable metricsGet batched usage for billable metrics.readthis connector
metronome.commits.listList a customer's commitsList a customer's commits.readthis connector
metronome.alerts.createCreate a threshold alertCreate a threshold alert.writethis connector

Try it

Prompts to paste into Claude.

Each one names the Metronome actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Metronome invoices are more than 30 days overdue? Group them by customer with the total owed.

    callsmetronome.invoices.list

  2. Writewrite

    Create a product in Metronome. Show me exactly what you will send before you save it.

    callsmetronome.products.create

  3. Across systemsread

    Which Metronome companies have invoices in ConnectWise PSA, and how many each?

    callsmetronome.customers.listconnectwise_manage.invoices.list

Across your systems

Metronome, joined to the rest of your business.

One ask fetches from Metronome and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

  • Which Metronome companies have invoices in ConnectWise PSA, and how many each?

    metronome.customers.list + connectwise_manage.invoices.list, on crm.company · ConnectWise PSA

  • Which Metronome companies have tickets in HubSpot CRM, and how many each?

    metronome.customers.list + hubspot_crm.tickets.list, on crm.company · HubSpot CRM

Also mapped by other connectorscrm.company 227commerce.product 109finance.invoice 91service.contract 20
ask
ask {  intent: "which Metronome companies have invoices in ConnectWise PSA, and how many each",  steps: [    { action: "metronome.customers.list", as: "co", input: {}, limit: 100, max_pages: 5 },    { action: "connectwise_manage.invoices.list", as: "inv", input: {}, limit: 100, max_pages: 5 },    { join: {        left: "co",        right: "inv",        on: "crm.company",        group_by: "co.name",        select: ["co.name", "count(inv.id) as invoices"]    } }  ]}
Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Metronome

Destructive actions wait for a yes.

16 Metronome actions are destructive. These are all of them:

  • Void an invoicemetronome.invoices.void
  • Archive a threshold alertmetronome.alerts.archive
  • Archive a packagemetronome.packages.archive
  • Archive a productmetronome.products.archive
  • Archive a contractmetronome.contracts.archive
  • Archive a customermetronome.customers.archive
  • Archive a rate cardmetronome.rate_cards.archive
  • Archive a notification configurationmetronome.notifications.archive
  • Archive a pricing unit (credit type)metronome.pricing_units.archive
  • Archive a billable metricmetronome.billable_metrics.archive
  • Add a one-time charge to a plan invoicemetronome.invoices.add_charge
  • Void a credit grantmetronome.credit_grants.void
  • Remove a custom field keymetronome.custom_fields.remove_key
  • Delete custom field values from an entitymetronome.custom_fields.delete_values
  • Delete a customer's billing provider configurationmetronome.customers.delete_billing_config
  • Archive customer billing provider configurationsmetronome.customers.archive_billing_provider_configurations

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dometronome.invoices.voidconfirm_policy: human

Void an invoice?

intent: the user asked me to void an invoice

run suspended · waiting for a named person · key metronome-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "metronome-agent",  allowed_actions: ["metronome.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "metronome.invoices.void", approver: "[email protected]" },    { match: "metronome.alerts.archive", approver: "[email protected]" },    { match: "metronome.packages.archive", approver: "[email protected]" }  ]}
Illustrative. Scoped to Metronome only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Metronome costs on actionlake.

Every Metronome action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Metronome refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 117 Metronome actions
  • 117actions pageeach page of a long list is one call
  • 52reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Metronome action.

117 actions by area: the id your agent calls, what it does, and its effect.

Contracts20
  • metronome.contracts.add_manual_balance_entryAdd a manual balance ledger entrywrite
  • metronome.contracts.amendAmend a contract (v1)write
  • metronome.contracts.archiveArchive a contractdestructive
  • metronome.contracts.createCreate a contractwrite
  • metronome.contracts.create_historical_invoicesCreate historical usage invoiceswrite
  • metronome.contracts.editEdit a contractwrite
  • metronome.contracts.getGet a contractread
  • metronome.contracts.get_edit_historyGet a contract's edit historyread
  • metronome.contracts.get_named_scheduleGet a contract's named scheduleread
  • metronome.contracts.get_rate_scheduleGet a contract's rate scheduleread
  • metronome.contracts.get_subscription_quantity_historyGet a subscription's quantity historyread
  • metronome.contracts.get_v1Get a contract (v1)read
  • metronome.contracts.listList a customer's contractsread
  • metronome.contracts.list_named_schedulesList a contract's named schedulesread
  • metronome.contracts.list_subscription_seats_historyList a subscription's seat historyread
  • metronome.contracts.list_v1List a customer's contracts (v1)read
  • metronome.contracts.schedule_pro_services_invoiceSchedule a professional services invoicewrite
  • metronome.contracts.set_usage_filterSet a contract's usage filterwrite
  • metronome.contracts.update_end_dateUpdate a contract's end datewrite
  • metronome.contracts.update_named_scheduleUpdate a contract's named schedulewrite
Customers18
  • metronome.customers.archiveArchive a customerdestructive
  • metronome.customers.archive_billing_provider_configurationsArchive customer billing provider configurationsdestructive
  • metronome.customers.createCreate a customerwrite
  • metronome.customers.delete_billing_configDelete a customer's billing provider configurationdestructive
  • metronome.customers.getGet a customerread
  • metronome.customers.get_billing_configGet a customer's billing provider configurationread
  • metronome.customers.get_named_scheduleGet a customer's named scheduleread
  • metronome.customers.listList customersread
  • metronome.customers.list_billable_metricsList a customer's billable metricsread
  • metronome.customers.list_billing_provider_configurationsList a customer's billing provider configurationsread
  • metronome.customers.list_costsList a customer's daily costsread
  • metronome.customers.preview_eventsPreview an invoice for hypothetical usage eventsread
  • metronome.customers.set_billing_configSet a customer's billing provider configurationwrite
  • metronome.customers.set_billing_provider_configurationsSet customer billing provider configurationswrite
  • metronome.customers.set_ingest_aliasesSet a customer's ingest aliaseswrite
  • metronome.customers.set_nameSet a customer's namewrite
  • metronome.customers.update_configUpdate a customer's configurationwrite
  • metronome.customers.update_named_scheduleUpdate a customer's named schedulewrite
Rate cards13
  • metronome.rate_cards.add_rateAdd a rate to a rate cardwrite
  • metronome.rate_cards.add_ratesAdd several rates to a rate cardwrite
  • metronome.rate_cards.archiveArchive a rate carddestructive
  • metronome.rate_cards.createCreate a rate cardwrite
  • metronome.rate_cards.getGet a rate cardread
  • metronome.rate_cards.get_named_scheduleGet a rate card's named scheduleread
  • metronome.rate_cards.get_rate_scheduleGet a rate card's rate scheduleread
  • metronome.rate_cards.listList rate cardsread
  • metronome.rate_cards.list_ratesGet a rate card's rates at a point in timeread
  • metronome.rate_cards.move_productsMove products on a rate cardwrite
  • metronome.rate_cards.set_product_orderSet the order of products on a rate cardwrite
  • metronome.rate_cards.updateUpdate a rate cardwrite
  • metronome.rate_cards.update_named_scheduleUpdate a rate card's named schedulewrite
Invoices6
  • metronome.invoices.add_chargeAdd a one-time charge to a plan invoicedestructive
  • metronome.invoices.getGet an invoiceread
  • metronome.invoices.listList a customer's invoicesread
  • metronome.invoices.list_breakdownsList a customer's invoice breakdownsread
  • metronome.invoices.regenerateRegenerate a voided invoicewrite
  • metronome.invoices.voidVoid an invoicedestructive
Notifications6
  • metronome.notifications.archiveArchive a notification configurationdestructive
  • metronome.notifications.createCreate a notification configurationwrite
  • metronome.notifications.editEdit a notification configurationwrite
  • metronome.notifications.getGet a notification configurationread
  • metronome.notifications.list_offsetList offset notification configurationsread
  • metronome.notifications.list_systemList system notification configurationsread
Billable metrics5
  • metronome.billable_metrics.archiveArchive a billable metricdestructive
  • metronome.billable_metrics.createCreate a billable metricwrite
  • metronome.billable_metrics.getGet a billable metricread
  • metronome.billable_metrics.listList billable metricsread
  • metronome.billable_metrics.updateRename a billable metricwrite
Credit grants5
  • metronome.credit_grants.createCreate a credit grantwrite
  • metronome.credit_grants.listList credit grantsread
  • metronome.credit_grants.list_ledger_entriesList credit ledger entriesread
  • metronome.credit_grants.updateEdit a credit grantwrite
  • metronome.credit_grants.voidVoid a credit grantdestructive
Custom fields5
  • metronome.custom_fields.add_keyAdd a custom field keywrite
  • metronome.custom_fields.delete_valuesDelete custom field values from an entitydestructive
  • metronome.custom_fields.list_keysList custom field keysread
  • metronome.custom_fields.remove_keyRemove a custom field keydestructive
  • metronome.custom_fields.set_valuesSet custom field values on an entitywrite
Packages5
  • metronome.packages.archiveArchive a packagedestructive
  • metronome.packages.createCreate a packagewrite
  • metronome.packages.getGet a packageread
  • metronome.packages.listList packagesread
  • metronome.packages.list_contractsList the contracts on a packageread
Products5
  • metronome.products.archiveArchive a productdestructive
  • metronome.products.createCreate a productwrite
  • metronome.products.getGet a productread
  • metronome.products.listList productsread
  • metronome.products.updateUpdate a productwrite
Commits4
  • metronome.commits.createCreate a customer-level commitwrite
  • metronome.commits.editEdit a customer-level or contract commitwrite
  • metronome.commits.listList a customer's commitsread
  • metronome.commits.update_end_dateUpdate a commit's end datewrite
Credits4
  • metronome.credits.createCreate a customer-level creditwrite
  • metronome.credits.editEdit a customer-level or contract creditwrite
  • metronome.credits.listList a customer's creditsread
  • metronome.credits.update_end_dateUpdate a credit's end datewrite
Usage4
  • metronome.usage.ingestIngest usage eventswrite
  • metronome.usage.listGet batched usage for billable metricsread
  • metronome.usage.list_with_groupsGet usage for one billable metric broken down by groupread
  • metronome.usage.search_eventsLook up ingested events by transaction IDread
Balances3
  • metronome.balances.get_net_balanceGet a customer's net balanceread
  • metronome.balances.listList a customer's commit and credit balancesread
  • metronome.balances.list_seat_balancesList a contract's seat balancesread
Customer alerts3
  • metronome.customer_alerts.getGet a customer's alert statusread
  • metronome.customer_alerts.listList a customer's alertsread
  • metronome.customer_alerts.resetReset a customer alert's evaluationwrite
Pricing units3
  • metronome.pricing_units.archiveArchive a pricing unit (credit type)destructive
  • metronome.pricing_units.createCreate a pricing unit (credit type)write
  • metronome.pricing_units.listList pricing units (credit types)read
Settings3
  • metronome.settings.list_billing_providersList configured billing providersread
  • metronome.settings.set_up_billing_providerSet up a billing providerwrite
  • metronome.settings.upsert_avalara_credentialsSet Avalara credentialswrite
Alerts2
  • metronome.alerts.archiveArchive a threshold alertdestructive
  • metronome.alerts.createCreate a threshold alertwrite
Audit logs1
  • metronome.audit_logs.listList audit log entriesread
Dashboards1
  • metronome.dashboards.get_embeddable_urlGet an embeddable customer dashboard URLread
Services1
  • metronome.services.listList Metronome's IP addresses and servicesread

Questions

The Metronome MCP server, answered.

Is there a Metronome MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 117 Metronome actions across contracts, customers, rate cards and invoices, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Metronome.

What do I need to connect Metronome?

Metronome API token. The free call account { op: "connections.requirements", service: "metronome" } lists exactly what to paste.

Can an AI agent delete or change things in Metronome?

Only if its key allows it, and only with an explicit confirmation. 16 Metronome actions are destructive, including void an invoice, archive a threshold alert and archive a package. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Metronome API limit?

actionlake paces every call to the limits in the Metronome service file: 100 calls a second per connection. Repeated reads are answered from cache (52 Metronome actions can be), which never reaches Metronome.

What does a Metronome action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (117 Metronome actions page). Cache hits, searches, dry runs and calls Metronome refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Metronome API does it cover?

The Metronome API v1/v2 (OpenAPI 3, Stainless SDK specification) at api.metronome.com. It is built from Metronome's documentation as read on 23 October 2026. 117 actions in 21 areas, each one in the signed service file (version 1.0.0).

Can I combine Metronome with my other systems?

Yes. ask joins Metronome to ConnectWise PSA or HubSpot CRM on the same customer and returns the answer rather than every row. Metronome maps crm.company, which 227 other connectors also map.

Does actionlake keep my Metronome data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Metronome credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Metronome today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.