About Askell
Askell is an MCP server for accessing the Askell payment and subscription API from clients such as Cursor and Claude Desktop. It separates read and mutation tools, supports production and sandbox environments, and provides customer, contract, and billing overviews.
Key features
- 01Discover and inspect API operations
- 02Call read and mutation endpoints separately
- 03Paginate list endpoints
- 04View customer and subscription overviews
- 05Inspect contracts and billing runs
- 06List webhooks with secrets redacted
Use cases
- 01Inspect a customer’s subscriptions
- 02Triage a billing run
- 03Review API schemas before a call
- 04Separate production and sandbox access
MCP support
The server exposes Askell API operations and payment, subscription, and webhook data to MCP clients through tools and OpenAPI resources. Clients can distinguish read calls from mutations and apply their own approval UI.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y askell-mcpASKELL_PRIVATE_API_KEYSecretSecret API key from the Askell dashboardASKELL_ENVproduction (default) or sandboxLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEaskell-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). The public key is optional — only temporary payment-method and checkout status endpoints use it
- One of:
Quick start
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 server key (askell-prod vs askell-sandbox). Each instance's instructions include the environment it is talking to.
Put keys in gitignored dotenv files, not in JSON. Copy .env.example:
.env— production (ASKELL_ENV=productionand that dashboard's keys).env.sandbox— sandbox (ASKELL_ENV=sandboxand that dashboard's keys)
Bun does not auto-load .env.sandbox. --no-env-file stops the sandbox process from also reading a production .env that happens to sit in the cwd.
Cursor
Project file: .cursor/mcp.json. mcp.json.example is this shape. ${workspaceFolder} is the directory that contains that mcp.json (the repo root when the file is .cursor/mcp.json). In ~/.cursor/mcp.json, use an absolute envFile path.
With Bun:
{
"mcpServers": {
"askell-prod": {
"command": "bunx",
"args": ["--no-env-file", "x", "askell-mcp"],
"envFile": "${workspaceFolder}/.env"
},
"askell-sandbox": {
"command": "bunx",
"args": ["--no-env-file", "x", "askell-mcp"],
"envFile": "${workspaceFolder}/.env.sandbox"
}
}
}
With a binary (download askell-mcp-<os>-<arch> from Releases, then chmod +x). Same envFile; the binary reads the environment Cursor injects:
{
"mcpServers": {
"askell-prod": {
"command": "/absolute/path/to/askell-mcp-linux-x64",
"envFile": "${workspaceFolder}/.env"
}
}
}
Reload the window after saving.
Claude Desktop
Config file:
- Linux:
~/.config/Claude/claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
No envFile field. The desktop process cwd is not your repo, so a relative .env path does not resolve. With Bun, pass an absolute --env-file:
{
"mcpServers": {
"askell-prod": {
"command": "bunx",
"args": [
"--no-env-file",
"--env-file=/absolute/path/.env",
"x",
"askell-mcp"
]
},
"askell-sandbox": {
"command": "bunx",
"args": [
"--no-env-file",
"--env-file=/absolute/path/.env.sandbox",
"x",
"askell-mcp"
]
}
}
}
A binary has no --env-file. Put the keys in env (plaintext in that JSON file):
{
"mcpServers": {
"askell-prod": {
"command": "/absolute/path/to/askell-mcp-linux-x64",
"env": {
"ASKELL_ENV": "production",
"ASKELL_PRIVATE_API_KEY": "your_production_secret_api_key",
"ASKELL_PUBLIC_API_KEY": "your_production_public_api_key_optional"
}
}
}
}
Quit Claude Desktop completely and reopen it. Saving the file is not enough.
Claude Code
Project .mcp.json expands ${VAR} from the environment of the process that launched claude. It does not load a dotenv file. The Bun --env-file args from the Desktop section work here as well; a relative path is fine when you start claude from the repo. ${ASKELL_PRIVATE_API_KEY} inside env only works when that variable is already exported in that environment. A .env file alone is not read.
Configuration
| Variable | Required | Default | Description |
|---|---|---|---|
ASKELL_PRIVATE_API_KEY | yes* | — | Secret API key (or ASKELL_SECRET_API_KEY) |
ASKELL_PUBLIC_API_KEY | no | — | Public key for a few checkout/payment endpoints |
ASKELL_ENV | no | production | production | sandbox — selects the official API host |
ASKELL_API_BASE_URL | no | — | Custom/local API base only. Do not set together with ASKELL_ENV unless it matches |
ASKELL_RESPONSE_MAX_BYTES | no | 64000 | Max response size returned to the model |
ASKELL_MUTATION_GATE | no | auto | auto / elicit / off — see below |
ASKELL_REQUIRE_MUTATION_APPROVAL | no | — | Deprecated alias: true→elicit, false→off |
ASKELL_ENV picks a stable host (same v1/v2 surface):
- production —
https://askell.is/api - sandbox —
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
Tools
| Tool | Description |
|---|---|
askell_list_operations | Search bundled OpenAPI operations |
askell_describe_operation | Params and body schema for one operation |
askell_call | GET/HEAD any v1/v2 endpoint |
askell_mutate | POST/PUT/PATCH/DELETE any v1/v2 endpoint |
askell_paginate_all | Follow paginated list endpoints |
askell_customer_overview | v1 customer + subscriptions |
askell_contract_overview | v2 subscription contract + billing runs |
askell_billing_run_triage | v2 billing run (+ optional contract) |
askell_list_webhooks | List configured webhooks (hmac_secret redacted) |
Resources
| URI | Content |
|---|---|
askell://spec/v1 | OpenAPI v1 |
askell://spec/v2 | OpenAPI v2 |
askell://docs/webhook-events | Webhook event reference |
Docs: docs.askell.is · OpenAPI: v1 · v2
License
Contributing
See CONTRIBUTING.md for local development, tests, and releases.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.