askell-mcp
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., "@askell-mcpShow me the contract overview for contract 9876"
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.
askell-mcp
MCP server for the Askell payment and subscription API.
Connect it to Cursor, Claude Desktop, or any MCP client to discover Askell endpoints, inspect customers/contracts/billing, and call the API. Reads and writes are separate tools so clients can show their own approval UI on mutations.
Requirements
An Askell account and secret API key (from the Askell dashboard)
One of:
Related MCP server: datagate-mcp
Quick start
1. Get API keys
In the Askell dashboard, copy your private (secret) API key. Optionally also the public key (only needed for temporary payment-method / checkout status endpoints).
2. Add to your MCP client
Prefer two server entries if you have both production and sandbox keys. Tool names are the same on both; the client distinguishes them by the mcp.json key (askell-prod vs askell-sandbox). Set ASKELL_ENV — the server picks the host. Each instance's instructions include the environment it is talking to.
With Bun (bunx):
{
"mcpServers": {
"askell-prod": {
"command": "bunx",
"args": ["-y", "askell-mcp@latest"],
"env": {
"ASKELL_ENV": "production",
"ASKELL_PRIVATE_API_KEY": "your_production_secret_api_key"
}
},
"askell-sandbox": {
"command": "bunx",
"args": ["-y", "askell-mcp@latest"],
"env": {
"ASKELL_ENV": "sandbox",
"ASKELL_PRIVATE_API_KEY": "your_sandbox_secret_api_key"
}
}
}
}With a binary (download askell-mcp-<os>-<arch> from Releases, then chmod +x):
{
"mcpServers": {
"askell-prod": {
"command": "/absolute/path/to/askell-mcp-linux-x64",
"env": {
"ASKELL_ENV": "production",
"ASKELL_PRIVATE_API_KEY": "your_production_secret_api_key"
}
}
}
}Example file: mcp.json.example.
Restart the client after saving.
Configuration
Variable | Required | Default | Description |
| yes* | — | Secret API key (or |
| no | — | Public key for a few checkout/payment endpoints |
| no |
|
|
| no | — | Custom/local API base only. Do not set together with |
| no |
| Max response size returned to the model |
| no |
|
|
| no | — | Deprecated alias: |
ASKELL_ENV picks a stable host (same v1/v2 surface):
production —
https://askell.is/apisandbox —
https://sandbox.askell.is/api(isolated tenant; keys from that dashboard)
Point a second MCP server entry at sandbox (ASKELL_ENV=sandbox) rather than switching env on one process. Keys do not work across hosts. Áskell Test Gateway is a payment acquirer (fake cards) on either host — not the same as the sandbox API. Official prose at docs.askell.is still documents Test Gateway and may omit the sandbox host.
ASKELL_MUTATION_GATE:
auto(default) — confirmation form only if this request's_metaenvelope declared form elicitation (MCP 2026-07-28). 2025-era clients (Cursor, most hosts) do not send that envelope, so the mutation runs and their own “allow this tool” UI is the gate.elicit— always return an elicitation form. The SDK refuses the call if the client cannot fulfil it (2026 envelope / 2025 initialize via the legacy shim).off— never ask (eval / trusted automation).
If both ASKELL_MUTATION_GATE and ASKELL_REQUIRE_MUTATION_APPROVAL are set, ASKELL_MUTATION_GATE wins.
What you can do
Typical agent workflow:
Discover —
askell_list_operations/askell_describe_operation(from bundled OpenAPI v1 + v2)Support tasks — customer/contract/billing helpers below
Anything else —
askell_callfor GET/HEAD,askell_mutatefor POST/PUT/PATCH/DELETE
Tools
Tool | Description |
| Search bundled OpenAPI operations |
| Params and body schema for one operation |
| GET/HEAD any v1/v2 endpoint |
| POST/PUT/PATCH/DELETE any v1/v2 endpoint |
| Follow paginated list endpoints |
| v1 customer + subscriptions |
| v2 subscription contract + billing runs |
| v2 billing run (+ optional contract) |
| List configured webhooks ( |
Resources
URI | Content |
| OpenAPI v1 |
| OpenAPI v2 |
| Webhook event reference |
API notes (short)
v1 — legacy paths like
/customers/,/subscriptions/(no/v2prefix)v2 — current model: catalogs, quotes, checkouts, contracts, billing runs under
/v2/v2 discounts — coupons:
GET/POST /v2/subscription-contracts/{id}/discount|apply-code|remove-discount(one active). Quotes takepromotion_codeand, for an existing buyer,customer(id) so combo discounts + promo restrictions apply. Totals already include both. Recurringfinalizeneeds a verified payment method even when due-now is 0. Not the v1discount0–100 field.Paths use trailing slashes
Prefer v2 for new integrations; v1 remains for existing ones
Docs: docs.askell.is · OpenAPI: v1 · v2
License
Contributing
See CONTRIBUTING.md for local development, tests, and releases.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
MCP server for Recurly — accounts, subscriptions, invoices, plans; cancel & pause subs.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server for Sherweb Partner API - distributor billing, service provider management, customer subscriptions, and payable charges12Apache 2.0
- AlicenseBqualityCmaintenanceMCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.13MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Stripe API with 10 tools covering payments, customers, invoices, and subscriptions. Generated with MCPForge. Destructive and financial operations require human approval.37MIT
- FlicenseAqualityCmaintenanceA demo MCP server exposing billing operations (invoices, customers) with no built-in safety, designed as a test target for NitroWatch governance. It allows reading, sending, archiving, and permanently deleting accounts/invoices without confirmation.5-