askell-mcp
MCP server for Askell's payment and subscription API, allowing users to discover API operations, make raw API calls with approval for mutations, and analyze customers, contracts, billing runs, and webhooks.
README
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 — with confirmation before mutating requests.
Requirements
- An Askell account and secret API key (from the Askell dashboard)
- One of:
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
With Bun (bunx):
{
"mcpServers": {
"askell": {
"command": "bunx",
"args": ["-y", "askell-mcp"],
"env": {
"ASKELL_PRIVATE_API_KEY": "your_secret_api_key"
}
}
}
}
With a binary (download askell-mcp-<os>-<arch> from Releases, then chmod +x):
{
"mcpServers": {
"askell": {
"command": "/absolute/path/to/askell-mcp-linux-x64",
"env": {
"ASKELL_PRIVATE_API_KEY": "your_secret_api_key"
}
}
}
}
Example file: mcp.json.example.
Restart the client after saving.
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_API_URL |
no | https://askell.is/api |
API base URL (or ASKELL_API_BASE_URL) |
ASKELL_RESPONSE_MAX_BYTES |
no | 64000 |
Max response size returned to the model |
ASKELL_REQUIRE_MUTATION_APPROVAL |
no | true |
Confirm before POST/PUT/PATCH/DELETE |
Askell has no separate sandbox host — production and test traffic use the same URL. Use the Áskell Test Gateway acquirer in your dashboard for safe payment testing. See Askell getting started.
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 a raw endpoint (mutations ask for approval when enabled)
Tools
| Tool | Description |
|---|---|
askell_list_operations |
Search bundled OpenAPI operations |
askell_describe_operation |
Params and body schema for one operation |
askell_call |
Call 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 |
Resources
| URI | Content |
|---|---|
askell://spec/v1 |
OpenAPI v1 |
askell://spec/v2 |
OpenAPI v2 |
askell://docs/webhook-events |
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/ - 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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。