Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Pulse MCP Server track 500 tokens of usage for customer 'user_123'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Pulse usage-based billing platform.
Track metering events, manage customers, generate invoices, and more — directly from any MCP-compatible AI assistant (Claude, Cursor, Windsurf, etc.).
npx @beinfi/pulse-mcpSet your API key as an environment variable:
export PULSE_API_KEY=sk_live_...Add to your claude_desktop_config.json:
{
"mcpServers": {
"pulse": {
"command": "npx",
"args": ["-y", "@beinfi/pulse-mcp"],
"env": {
"PULSE_API_KEY": "sk_live_..."
}
}
}
}claude mcp add pulse -- npx -y @beinfi/pulse-mcpThen set your API key:
export PULSE_API_KEY=sk_live_...Related MCP server: Revenium MCP Server
track_event — Track a single usage event for a customer
track_events_batch — Track multiple usage events in a single request
get_usage — Query aggregated usage data with optional filters
list_products — List all products
get_product — Get product details including its meters
create_product — Create a new product
create_meter — Create a meter (usage dimension) for a product
list_customers — List all customers for a product
create_customer — Create a new customer
update_customer — Update customer details
list_invoices — List invoices for a product
generate_invoice — Generate an invoice for a customer's usage period
get_invoice — Get invoice details
send_invoice — Send an invoice via email
list_payment_links — List all payment links
create_payment_link — Create a new payment link
get_payment_link — Get payment link details
list_payment_intents — List payment intents for a link
list_received_payments — List all received payments
list_my_agents — List your published AI agents
get_agent_usage — Get usage stats for an agent
invoke_agent — Invoke an AI agent with text input
list_webhooks — List all webhook subscriptions
create_webhook — Create a webhook subscription
delete_webhook — Delete a webhook subscription
Environment Variable | Required | Default | Description |
| Yes | — | Your Pulse API key ( |
| No |
| API base URL |
MIT
Create a new customer for a product
Inputs: productId (required), externalId (required), name, email.
Create a meter (usage dimension) for a product
Inputs: productId (required), name (required), displayName (required), unit (required), +1 more.
Create a new payment link that customers can use to pay
Inputs: title (required), amount (required), description, currency.
Create a new product for usage metering
Inputs: name (required), type, description.
Create a webhook subscription to receive event notifications
Inputs: url (required), events (required).
Delete a webhook subscription
Inputs: webhookId (required).
Generate an invoice for a customer's usage in a given period
Inputs: productId (required), customerId (required), periodStart (required), periodEnd (required).
Get usage statistics for a specific agent by its slug
Inputs: slug (required).
Get detailed information about a specific invoice
Inputs: productId (required), invoiceId (required).
Get details about a specific payment link
Inputs: linkId (required).
Get details of a specific product including its meters
Inputs: productId (required).
Query aggregated usage data, optionally filtered by product, customer, or date range
Inputs: productId, customerId, startDate, endDate.
Invoke an AI agent from the Pulse marketplace with a text input
Inputs: slug (required), input (required).
List all customers for a product
Inputs: productId (required).
List invoices for a product, optionally filtered by status
Inputs: productId (required), status.
List all AI agents you've published in the Pulse marketplace
Inputs: no named parameters.
List payment intents (attempted payments) for a specific payment link
Inputs: linkId (required).
List all payment links in your account
Inputs: limit, offset.
List all products in your Pulse account
Inputs: no named parameters.
List all received payments across all payment links
Inputs: limit, offset.
List all webhook subscriptions
Inputs: no named parameters.
Send (or re-send) an invoice via email to the customer
Inputs: productId (required), invoiceId (required).
Track a single usage event for a customer
Inputs: meterId (required), customerId (required), value (required), timestamp, +1 more.
Track multiple usage events in a single request
Inputs: events (required).
Update an existing customer's details
Inputs: productId (required), customerId (required), name, email.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 25 tools
Most tools have clearly distinct purposes targeting specific resources and actions, such as create_customer vs. update_customer or track_event vs. track_events_batch. However, some potential ambiguity exists between list_payment_intents and list_received_payments, as both relate to payment tracking but with slightly different scopes that could confuse an agent about which to use for specific queries.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_customer, list_products, get_usage, and update_customer. All tools use snake_case with clear action verbs, making the set predictable and easy to navigate without any deviations in naming conventions.
With 25 tools, the count is borderline high for a coherent set, as it may feel heavy and potentially overwhelming for an agent. While the tools cover a broad domain of billing, metering, and marketplace operations, the number approaches the upper limit where usability might degrade, placing it in the 16-25 range that feels borderline for typical agent interactions.
The tool set provides comprehensive coverage for billing, metering, and marketplace domains, including CRUD operations for customers, products, and webhooks, plus usage tracking and payment management. Minor gaps exist, such as no update or delete tools for products or meters, but agents can likely work around these with the available create and get operations without significant failures.
Invoicing you drive by talking to your AI: log time, raise invoices and track what's owed via MCP.
Pay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.
Accounts receivable automation for Xero and QuickBooks Online, inside your AI assistant. Ask Claude, ChatGPT or any MCP client for a receivables summary, find customers and invoices, read the email and SMS replies your customers sent, and see what Paidnice sent or skipped. Ask why a reminder, late fee or statement did or did not go out, and update a customer's contact people straight into your ledger. Secure OAuth sign-in. One connection covers every organisation you tick, with Read or Read and Write access.
Pay-per-action access to APIs and MCP tools over Lightning L402 and Base USDC x402.
