4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Metronome MCP Server

Bring Usage Based Billing
to CrewAI

Learn how to connect Metronome to CrewAI and start using 31 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add Custom Field KeyAdd RateArchive CustomerCreate AlertCreate Billable MetricCreate CommitCreate ContractCreate CustomerCreate NotificationCreate ProductCreate Rate CardEdit ContractGet Audit LogsGet CustomerGet InvoiceGet Net BalanceGet ServicesGet UsageGet Usage GroupsIngest EventsList BalancesList Billable MetricsList ContractsList Credit TypesList CustomersList InvoicesList ProductsRegenerate InvoiceSearch EventsSet Custom Field ValuesVoid Invoice

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Metronome

What is the Metronome MCP Server?

Connect your Metronome account to any AI agent to streamline your usage-based billing and revenue operations through natural conversation.

What you can do

  • Usage Ingestion & Querying — Send usage events and retrieve aggregated usage data across customers and metrics using ingest_events and get_usage.
  • Customer Management — Create, list, and archive customers, or manage their billing configurations via list_customers and create_customer.
  • Billing & Invoicing — Fetch, void, or regenerate invoices and track net balances with list_invoices and get_net_balance.
  • Contract Lifecycle — Create and edit contracts, manage rate cards, and track commits using create_contract and list_contracts.
  • Alerts & Monitoring — Set up notifications, alerts, and access audit logs for billing transparency.

How it works

  1. Subscribe to this server
  2. Enter your Metronome API Token
  3. Start managing your billing operations from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Finance Teams — reconcile usage data and manage invoices without manual exports.
  • Product Managers — analyze feature usage and billing impact in real-time.
  • Engineering Teams — verify event ingestion and monitor billing services directly from the terminal.

Built-in capabilities (31)

add_custom_field_key

Create a custom field key

add_rate

Add a rate to a rate card

archive_customer

Voids invoices and archives contracts. Archive a customer

create_alert

Create a threshold notification alert

create_billable_metric

Create a billable metric

create_commit

Create a commit

create_contract

Create a contract

create_customer

Create a new customer

create_notification

Create an offset lifecycle event notification

create_product

Products can be USAGE, FIXED, COMPOSITE, or SUBSCRIPTION. Create a product

create_rate_card

Defines base prices for products. Create a rate card

edit_contract

). Edit a contract

get_audit_logs

Get audit logs

get_customer

Get a specific customer

get_invoice

Get an invoice

get_net_balance

Get net balance

get_services

Get services

get_usage

Get batched usage data

get_usage_groups

Get usage data with paginated groupings

ingest_events

Supports up to 100,000 events per second. Ingest usage events into Metronome

list_balances

List balances

list_billable_metrics

List all billable metrics

list_contracts

List customer contracts

list_credit_types

List pricing units

list_customers

Supports filtering. List all customers

list_invoices

List invoices

list_products

List products

regenerate_invoice

Regenerate an invoice

search_events

Designed for sampling-based testing. Search events by transaction ID

set_custom_field_values

Set custom field values

void_invoice

Void an invoice

Why CrewAI?

When paired with CrewAI, Metronome becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Metronome tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Metronome in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Metronome and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Metronome to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Metronome in CrewAI

The Metronome MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 31 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Metronome
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Metronome for CrewAI

Every tool call from CrewAI to the Metronome MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I check the current net balance for a specific customer?

Yes! Use the get_net_balance tool with the specific customer_id to retrieve the real-time balance information.

02

How do I see usage broken down by specific dimensions?

You can use the get_usage_groups tool. It allows you to retrieve granular usage data for a specific customer and metric, broken down by your custom grouping dimensions.

03

Is it possible to list all invoices for a client to check their payment history?

Absolutely. Use the list_invoices tool and provide the customer_id to see a paginated list of all invoices associated with that account.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →