RevKeen MCP
Connect RevKeen tools to AI hosts over the Model Context Protocol
RevKeen MCP is the AI integration surface for merchants and internal tools. It exposes scoped RevKeen tools over remote MCP so hosts like Claude, Cursor, and VS Code can inspect billing, customer, subscription, payment, and usage state without you hand-authoring custom connectors.
Production endpoint: https://mcp.revkeen.com/mcp
Use the API Reference for human REST documentation. Use MCP when an AI host needs structured tools, OAuth-scoped access, and a stable tool contract.
Connect to RevKeen's MCP server
{
"mcpServers": {
"revkeen": {
"url": "https://mcp.revkeen.com/mcp"
}
}
}{
"servers": {
"revkeen": {
"type": "http",
"url": "https://mcp.revkeen.com/mcp"
}
}
}claude mcp add --transport http revkeen https://mcp.revkeen.com/mcp{
"mcpServers": {
"revkeen": {
"command": "npx",
"args": ["-y", "@anthropic-ai/mcp-remote", "https://mcp.revkeen.com/mcp"]
}
}
}Server URL: https://mcp.revkeen.com/mcp
Transport: Streamable HTTP
Authentication: OAuth 2.1After your host connects, RevKeen opens a browser-based OAuth flow. The granted scopes become the tool permissions for that MCP session.
What the production server exposes by default
The default customer launch profile is read-first and exposes 20 approved v1 tools.
| Area | Default tools |
|---|---|
| Customers | customers_list, customers_get |
| Invoices | invoices_list, invoices_get |
| Payments | payments_list, payments_get |
| Orders | orders_list, orders_get |
| Subscriptions | subscriptions_list, subscriptions_get, subscriptions_list_in_dunning |
| Meters and pricing | meters_list, meters_get, meters_list_prices |
| Usage billing | usage_events_list, usage_events_aggregate, usage_events_dry_run, usage_balance_get |
| Integrations | integrations_list_packages, integrations_list_mappings |
RevKeen keeps broader write and destructive tools behind a separate rollout policy rather than exposing full API parity by default.
Scope model
| Scope | What it unlocks |
|---|---|
customers:read | Customer lists and customer detail lookups |
integrations:read | Integration package and mapping inspection |
invoices:read | Invoice list and invoice detail access |
orders:read | Order list and order detail access |
payments:read | Payment list and payment detail access |
prices:read | Meter price and pricing inspection |
subscriptions:read | Subscription and dunning-state inspection |
usage:read | Usage events, aggregates, meters, and balances |
How access works
- Your MCP host connects to
https://mcp.revkeen.com/mcp. - RevKeen authenticates the user through OAuth 2.1.
- The server issues scoped access for the MCP session.
- Tool calls are enforced server-side with merchant isolation, audit logging, and rate limiting.
This is the main difference between MCP and simply handing an AI tool an API key. The MCP server enforces access policy, session lifecycle, and tool boundaries for you.
Operational endpoints
| Endpoint | Purpose |
|---|---|
https://mcp.revkeen.com/ | Root metadata and public server information |
https://mcp.revkeen.com/healthz | Health check endpoint |
https://mcp.revkeen.com/mcp | Remote MCP endpoint |
Local development
For internal or advanced local development, run the MCP server from this repo:
pnpm --filter @revkeen/mcp-server devThe local server in apps/mcp-server uses the official MCP SDK, Streamable HTTP transport, OAuth bearer-token verification, scoped tool access, and the same launch-policy model as production.
When to use MCP vs SDKs vs REST
| Surface | Best for |
|---|---|
| MCP | AI hosts and agent workflows |
| SDKs | Application code you own and deploy |
| API Reference | Raw HTTP integrations and protocol details |
| CLI | Terminal workflows and operator tasks |
Troubleshooting
- If the host cannot connect, confirm it is using
https://mcp.revkeen.com/mcprather than an older SSE or local stdio configuration. - If OAuth succeeds but tools are missing, reconnect with the scopes you actually need.
- If the host connects but data access fails, verify that the authenticated user can access the target merchant and resources.
- If you need operational status, check the root metadata endpoint and
https://mcp.revkeen.com/healthz.