Metrifox exposes an MCP (Model Context Protocol) server that lets AI assistants query your billing data directly — customers, subscriptions, invoices, plans, usage, and MRR.
This means you can ask an AI assistant questions like:
- “How many subscribers does each plan have?”
- “Show me the MRR trend for the last 6 months”
- “What invoices are overdue for customer Acme Corp?”
…and the assistant will fetch real data from your Metrifox account to answer.
Server endpoint
https://api.metrifox.com/mcp
Authentication
There are two ways to authenticate with the MCP server:
Option 1: API Key
The simplest option. Use an API key from your dashboard in the x-api-key header.
- Go to Developers > API Keys in your Metrifox dashboard
- Create or copy an existing API key
- Pass it as a header:
x-api-key: sk_live_your_key_here
API keys have read and write scopes that control what actions they can perform. Currently all MCP tools are read-only, but when write tools are added, API keys without write scope won’t be able to use them.
Option 2: OAuth (for AI chat apps)
For apps where users log in with their Metrifox credentials, the MCP server supports the full OAuth 2.0 authorization code flow with PKCE.
When using OAuth, the tools and resources available are scoped to the user’s role permissions. A user who only has access to view customers won’t be able to query invoices or subscriptions.
OAuth endpoints:
| Endpoint | Description |
|---|
GET /.well-known/oauth-authorization-server | Authorization server metadata (discovery) |
GET /.well-known/oauth-protected-resource | Protected resource metadata |
POST /mcp/oauth/register | Dynamic client registration |
GET /mcp/oauth/authorize | Authorization page |
POST /mcp/oauth/token | Token exchange (authorization code → access token) |
Most MCP clients (Claude Desktop, Cursor, etc.) handle the OAuth flow automatically when you provide the server URL. You typically just need to enter the MCP endpoint and the client takes care of the rest.
Connecting your AI assistant
Claude Desktop
Add this to your Claude Desktop config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"metrifox": {
"url": "https://api.metrifox.com/mcp",
"headers": {
"x-api-key": "sk_live_your_key_here"
}
}
}
}
Cursor
- Open Settings > MCP
- Click Add new MCP server
- Set the transport to Streamable HTTP
- Enter
https://api.metrifox.com/mcp as the URL
- For API key auth, add the header
x-api-key with your key. For OAuth, leave headers empty — Cursor will handle the login flow.
Windsurf
Add to your Windsurf MCP config:
{
"mcpServers": {
"metrifox": {
"serverUrl": "https://api.metrifox.com/mcp",
"headers": {
"x-api-key": "sk_live_your_key_here"
}
}
}
}
Other MCP clients
Any MCP-compatible client that supports Streamable HTTP transport can connect. Configure it with:
- URL:
https://api.metrifox.com/mcp
- Auth: Either
x-api-key header or OAuth (the server advertises OAuth discovery at /.well-known/oauth-authorization-server)
What you can do
Once connected, your AI assistant can:
- Look up customers — search by name, email, or key, and get full details including subscriptions, payment methods, and credit wallets
- Check invoices and billing — view invoices by status (paid, overdue, etc.) and pull billing history for any subscription
- Explore usage — see what features a customer has access to, their usage breakdown, and trends over time
- Browse products and plans — view plan summaries, detailed pricing configurations (including localized pricing), entitlements, and subscriber counts
- Track revenue — get MRR trends over time and per-plan revenue breakdowns
- Generate charts — create bar, line, pie, or doughnut charts from any data
- Search docs — look up Metrifox product documentation
The full list of tools and their parameters are automatically discovered by your MCP client when it connects — no manual configuration needed.
Permissions
How permissions work depends on the authentication method:
| Auth method | Permission model |
|---|
| API Key | Controlled by the key’s scopes (read, write). All read tools are available with a read-scoped key. Write tools (coming soon) will require write scope. |
| OAuth | Scoped to the logged-in user’s role permissions. Tools are filtered — users only see and can use tools they have permission for. |
