--- title: "Metronome MCP server for AI agents - actionlake" description: "Give Claude 117 Metronome actions through one MCP server: contracts, customers, rate cards. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/metronome updated: 2026-10-23 --- 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. [Connect Metronome free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 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 ``` - 117 actions in one signed file - 54 read look, never change - 47 write create and update - 16 wait for a yes destructive, 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_key` Metronome 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 call check { 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 2026[storage.googleapis.com](https://storage.googleapis.com/stainless-sdk-openapi-specs/metronome/metronome-2e8e5f64af2afa983b38547a3480f0009972428077054f3d4c81961775040756.yml) [GitHub](https://github.com/Metronome-Industries/metronome-python/blob/main/api.md) [docs.metronome.com](https://docs.metronome.com/api) **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. - **54** read look, never change - **47** write create and update - **16** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `metronome.products.list` List products | List products. | read | `commerce.product.list` 112 connectors | | `metronome.customers.list` List customers | List customers. | read | `crm.company.list` 162 connectors | | `metronome.products.create` Create a product | Create a product. | write | `commerce.product.create` 92 connectors | | `metronome.invoices.list` List a customer's invoices | List a customer's invoices. | read | `finance.invoice.list` 101 connectors | | `metronome.customers.create` Create a customer | Create a customer. | write | `crm.company.create` 142 connectors | | `metronome.contracts.list` List a customer's contracts | List a customer's contracts. | read | `service.contract.list` 23 connectors | | `metronome.invoices.get` Get an invoice | Get an invoice. | read | `finance.invoice.get` 102 connectors | | `metronome.contracts.create` Create a contract | Create a contract. | write | `service.contract.create` 19 connectors | | `metronome.invoices.void` Void an invoice | Void an invoice. | destructive | `finance.invoice.void` 22 connectors | | `metronome.usage.list` Get batched usage for billable metrics | Get batched usage for billable metrics. | read | this connector | | `metronome.commits.list` List a customer's commits | List a customer's commits. | read | this connector | | `metronome.alerts.create` Create a threshold alert | Create a threshold alert. | write | this 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. Read read Which Metronome invoices are more than 30 days overdue? Group them by customer with the total owed. calls `metronome.invoices.list` 2. Write write Create a product in Metronome. Show me exactly what you will send before you save it. calls `metronome.products.create` 3. Across systems read Which Metronome companies have invoices in ConnectWise PSA, and how many each? calls `metronome.customers.list` `connectwise_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](https://actionlake.com/connectors/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](https://actionlake.com/connectors/hubspot-crm) Also mapped by other connectors `crm.company` **227** `commerce.product` **109** `finance.invoice` **91** `service.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 invoice `metronome.invoices.void` - Archive a threshold alert `metronome.alerts.archive` - Archive a package `metronome.packages.archive` - Archive a product `metronome.products.archive` - Archive a contract `metronome.contracts.archive` - Archive a customer `metronome.customers.archive` - Archive a rate card `metronome.rate_cards.archive` - Archive a notification configuration `metronome.notifications.archive` - Archive a pricing unit (credit type) `metronome.pricing_units.archive` - Archive a billable metric `metronome.billable_metrics.archive` - Add a one-time charge to a plan invoice `metronome.invoices.add_charge` - Void a credit grant `metronome.credit_grants.void` - Remove a custom field key `metronome.custom_fields.remove_key` - Delete custom field values from an entity `metronome.custom_fields.delete_values` - Delete a customer's billing provider configuration `metronome.customers.delete_billing_config` - Archive customer billing provider configurations `metronome.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. do metronome.invoices.void confirm_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: "lead@example.com" }, { match: "metronome.alerts.archive", approver: "lead@example.com" }, { match: "metronome.packages.archive", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 117 Metronome actions - 117 actions page each page of a long list is one call - 52 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Metronome action. 117 actions by area: the id your agent calls, what it does, and its effect. **Contracts 20** - `metronome.contracts.add_manual_balance_entry` Add a manual balance ledger entry write - `metronome.contracts.amend` Amend a contract (v1) write - `metronome.contracts.archive` Archive a contract destructive - `metronome.contracts.create` Create a contract write - `metronome.contracts.create_historical_invoices` Create historical usage invoices write - `metronome.contracts.edit` Edit a contract write - `metronome.contracts.get` Get a contract read - `metronome.contracts.get_edit_history` Get a contract's edit history read - `metronome.contracts.get_named_schedule` Get a contract's named schedule read - `metronome.contracts.get_rate_schedule` Get a contract's rate schedule read - `metronome.contracts.get_subscription_quantity_history` Get a subscription's quantity history read - `metronome.contracts.get_v1` Get a contract (v1) read - `metronome.contracts.list` List a customer's contracts read - `metronome.contracts.list_named_schedules` List a contract's named schedules read - `metronome.contracts.list_subscription_seats_history` List a subscription's seat history read - `metronome.contracts.list_v1` List a customer's contracts (v1) read - `metronome.contracts.schedule_pro_services_invoice` Schedule a professional services invoice write - `metronome.contracts.set_usage_filter` Set a contract's usage filter write - `metronome.contracts.update_end_date` Update a contract's end date write - `metronome.contracts.update_named_schedule` Update a contract's named schedule write **Customers 18** - `metronome.customers.archive` Archive a customer destructive - `metronome.customers.archive_billing_provider_configurations` Archive customer billing provider configurations destructive - `metronome.customers.create` Create a customer write - `metronome.customers.delete_billing_config` Delete a customer's billing provider configuration destructive - `metronome.customers.get` Get a customer read - `metronome.customers.get_billing_config` Get a customer's billing provider configuration read - `metronome.customers.get_named_schedule` Get a customer's named schedule read - `metronome.customers.list` List customers read - `metronome.customers.list_billable_metrics` List a customer's billable metrics read - `metronome.customers.list_billing_provider_configurations` List a customer's billing provider configurations read - `metronome.customers.list_costs` List a customer's daily costs read - `metronome.customers.preview_events` Preview an invoice for hypothetical usage events read - `metronome.customers.set_billing_config` Set a customer's billing provider configuration write - `metronome.customers.set_billing_provider_configurations` Set customer billing provider configurations write - `metronome.customers.set_ingest_aliases` Set a customer's ingest aliases write - `metronome.customers.set_name` Set a customer's name write - `metronome.customers.update_config` Update a customer's configuration write - `metronome.customers.update_named_schedule` Update a customer's named schedule write **Rate cards 13** - `metronome.rate_cards.add_rate` Add a rate to a rate card write - `metronome.rate_cards.add_rates` Add several rates to a rate card write - `metronome.rate_cards.archive` Archive a rate card destructive - `metronome.rate_cards.create` Create a rate card write - `metronome.rate_cards.get` Get a rate card read - `metronome.rate_cards.get_named_schedule` Get a rate card's named schedule read - `metronome.rate_cards.get_rate_schedule` Get a rate card's rate schedule read - `metronome.rate_cards.list` List rate cards read - `metronome.rate_cards.list_rates` Get a rate card's rates at a point in time read - `metronome.rate_cards.move_products` Move products on a rate card write - `metronome.rate_cards.set_product_order` Set the order of products on a rate card write - `metronome.rate_cards.update` Update a rate card write - `metronome.rate_cards.update_named_schedule` Update a rate card's named schedule write **Invoices 6** - `metronome.invoices.add_charge` Add a one-time charge to a plan invoice destructive - `metronome.invoices.get` Get an invoice read - `metronome.invoices.list` List a customer's invoices read - `metronome.invoices.list_breakdowns` List a customer's invoice breakdowns read - `metronome.invoices.regenerate` Regenerate a voided invoice write - `metronome.invoices.void` Void an invoice destructive **Notifications 6** - `metronome.notifications.archive` Archive a notification configuration destructive - `metronome.notifications.create` Create a notification configuration write - `metronome.notifications.edit` Edit a notification configuration write - `metronome.notifications.get` Get a notification configuration read - `metronome.notifications.list_offset` List offset notification configurations read - `metronome.notifications.list_system` List system notification configurations read **Billable metrics 5** - `metronome.billable_metrics.archive` Archive a billable metric destructive - `metronome.billable_metrics.create` Create a billable metric write - `metronome.billable_metrics.get` Get a billable metric read - `metronome.billable_metrics.list` List billable metrics read - `metronome.billable_metrics.update` Rename a billable metric write **Credit grants 5** - `metronome.credit_grants.create` Create a credit grant write - `metronome.credit_grants.list` List credit grants read - `metronome.credit_grants.list_ledger_entries` List credit ledger entries read - `metronome.credit_grants.update` Edit a credit grant write - `metronome.credit_grants.void` Void a credit grant destructive **Custom fields 5** - `metronome.custom_fields.add_key` Add a custom field key write - `metronome.custom_fields.delete_values` Delete custom field values from an entity destructive - `metronome.custom_fields.list_keys` List custom field keys read - `metronome.custom_fields.remove_key` Remove a custom field key destructive - `metronome.custom_fields.set_values` Set custom field values on an entity write **Packages 5** - `metronome.packages.archive` Archive a package destructive - `metronome.packages.create` Create a package write - `metronome.packages.get` Get a package read - `metronome.packages.list` List packages read - `metronome.packages.list_contracts` List the contracts on a package read **Products 5** - `metronome.products.archive` Archive a product destructive - `metronome.products.create` Create a product write - `metronome.products.get` Get a product read - `metronome.products.list` List products read - `metronome.products.update` Update a product write **Commits 4** - `metronome.commits.create` Create a customer-level commit write - `metronome.commits.edit` Edit a customer-level or contract commit write - `metronome.commits.list` List a customer's commits read - `metronome.commits.update_end_date` Update a commit's end date write **Credits 4** - `metronome.credits.create` Create a customer-level credit write - `metronome.credits.edit` Edit a customer-level or contract credit write - `metronome.credits.list` List a customer's credits read - `metronome.credits.update_end_date` Update a credit's end date write **Usage 4** - `metronome.usage.ingest` Ingest usage events write - `metronome.usage.list` Get batched usage for billable metrics read - `metronome.usage.list_with_groups` Get usage for one billable metric broken down by group read - `metronome.usage.search_events` Look up ingested events by transaction ID read **Balances 3** - `metronome.balances.get_net_balance` Get a customer's net balance read - `metronome.balances.list` List a customer's commit and credit balances read - `metronome.balances.list_seat_balances` List a contract's seat balances read **Customer alerts 3** - `metronome.customer_alerts.get` Get a customer's alert status read - `metronome.customer_alerts.list` List a customer's alerts read - `metronome.customer_alerts.reset` Reset a customer alert's evaluation write **Pricing units 3** - `metronome.pricing_units.archive` Archive a pricing unit (credit type) destructive - `metronome.pricing_units.create` Create a pricing unit (credit type) write - `metronome.pricing_units.list` List pricing units (credit types) read **Settings 3** - `metronome.settings.list_billing_providers` List configured billing providers read - `metronome.settings.set_up_billing_provider` Set up a billing provider write - `metronome.settings.upsert_avalara_credentials` Set Avalara credentials write **Alerts 2** - `metronome.alerts.archive` Archive a threshold alert destructive - `metronome.alerts.create` Create a threshold alert write **Audit logs 1** - `metronome.audit_logs.list` List audit log entries read **Dashboards 1** - `metronome.dashboards.get_embeddable_url` Get an embeddable customer dashboard URL read **Services 1** - `metronome.services.list` List Metronome's IP addresses and services read 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. ## More connectors like Metronome Shares the most action names with - [sevdesk 9](https://actionlake.com/connectors/sevdesk) - [SAP S/4HANA Cloud Public Edition 8](https://actionlake.com/connectors/sap-s-4hana-cloud-public-edition) - [Recurly 7](https://actionlake.com/connectors/recurly) - [Maxio Advanced Billing 6](https://actionlake.com/connectors/maxio-advanced-billing) - [Lexware Office 5](https://actionlake.com/connectors/lexware-office) - [Anrok 3](https://actionlake.com/connectors/anrok) Joins with, on shared entities - [ConnectWise PSA 4](https://actionlake.com/connectors/connectwise-psa) - [HaloPSA 4](https://actionlake.com/connectors/halopsa) - [Microsoft Dynamics 365 4](https://actionlake.com/connectors/microsoft-dynamics-365) - [Kaseya BMS 4](https://actionlake.com/connectors/kaseya-bms) - [Syncro 4](https://actionlake.com/connectors/syncro) - [RepairShopr 4](https://actionlake.com/connectors/repairshopr) Browse - [All Accounting & finance connectors](https://actionlake.com/connectors/category/accounting-and-finance) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Metronome; the name is the vendor's own. Counts are from the Metronome service file, version 1.0.0. ## Give your agent Metronome today. [Connect Metronome free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/metronome More: https://actionlake.com/llms.txt