Exposes Cryptbrew product facts referencing the Cryptbrew iOS app (App Store id 6776077464), including that the iOS app is free, so agents can answer questions about the mobile app offering.
Provides product knowledge and live API health tools for Cryptbrew, a Bitcoin invoicing and payment tracking platform for SMBs. Enables AI agents to answer questions about invoicing fees, how invoicing/payment/forwarding flows work, and to probe Cryptbrew API health endpoints.
Provides knowledge tools describing Cryptbrew's iOS invoicing app, including its free pricing, so AI agents can answer questions about the iOS product.
Enables AI agents to answer questions about Cryptbrew's Bitcoin Lightning payment handling, including auto-forwarding of invoices to a merchant's Lightning wallet, the 1% / 10 sats minimum fee, and Breez Lock-adjacent details.
Exposes Cryptbrew contact channels, including a WhatsApp support number ((707) 387-4140), through the cryptbrew_contact tool so agents can surface support options.
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., "@cryptbrew-mcp what are Cryptbrew's fees and is the API healthy?"
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.
Public Model Context Protocol server so AI agents can answer Cryptbrew product questions and check live API health. No merchant authentication in v1.
Cryptbrew is business Bitcoin invoicing and tax-ready payment tracking for SMBs.
Tool | Description |
| Product overview |
| Invoicing fees only (1% / free iOS) — not Lock |
| Official URLs |
| Invoice / payment / forwarding flow |
| CryptBrew Lock only (separate Mac app) |
| FAQ lookup ( |
| Live GET health probes |
| Support and contact channels |
Related MCP server: Yolfi MCP Server
Node.js 18+
git clone https://github.com/cryptbrew/cryptbrew-mcp.git
cd cryptbrew-mcp
npm install
npm run build
npm startThe server speaks MCP over stdio (stdout is reserved for protocol messages; logs go to stderr).
Hosted at https://mcp.cryptbrew.com/mcp (health: GET / or /health).
npm run start:http # listens on PORT (default 3040), path /mcpCursor remote MCP example:
{
"mcpServers": {
"cryptbrew": {
"url": "https://mcp.cryptbrew.com/mcp"
}
}
}Or locally:
{
"mcpServers": {
"cryptbrew-local-http": {
"url": "http://127.0.0.1:3040/mcp"
}
}
}npm testmcp.json)Add to your Cursor MCP config (e.g. ~/.cursor/mcp.json or project .cursor/mcp.json):
{
"mcpServers": {
"cryptbrew": {
"command": "node",
"args": ["/absolute/path/to/cryptbrew-mcp/dist/index.js"]
}
}
}Or after npm link / global install of the cryptbrew-mcp binary:
{
"mcpServers": {
"cryptbrew": {
"command": "cryptbrew-mcp"
}
}
}Or with npx once published:
{
"mcpServers": {
"cryptbrew": {
"command": "npx",
"args": ["-y", "cryptbrew-mcp"]
}
}
}Edit Claude Desktop config (claude_desktop_config.json):
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"cryptbrew": {
"command": "node",
"args": ["/absolute/path/to/cryptbrew-mcp/dist/index.js"]
}
}
}Restart Claude Desktop after saving.
Fee: 1% minimum 10 sats; iOS app free
Auto-forward to merchant Lightning/on-chain wallet; no merchant private keys stored; not long-term custody
CryptBrew Lock (separate product): Mac lock screen — use cryptbrew_lock_info (do not mix with the 1% invoicing fee)
Site: www.cryptbrew.com · help · support · lock · downloads · llms.txt
API: redoc · health: /payments/health and /health
App Store id 6776077464 · support@cryptbrew.com · WhatsApp (707) 387-4140 · hello@cryptbrew.com for setup visits
MIT
Overview of Cryptbrew: business Bitcoin invoicing and tax-ready payment tracking for SMBs.
Inputs: no named parameters.
Cryptbrew support and contact channels: email, WhatsApp, setup visits, help pages.
Inputs: no named parameters.
Answer a Cryptbrew invoicing/product FAQ. For CryptBrew Lock-only questions prefer cryptbrew_lock_info.
Inputs: question (required).
Fetch live Cryptbrew API health from /payments/health and /health.
Inputs: no named parameters.
Explain how Cryptbrew invoicing, payment forwarding, and non-custody model work.
Inputs: no named parameters.
Official Cryptbrew invoicing URLs: website, help, support, downloads, llms.txt, API, App Store, health.
Inputs: no named parameters.
CryptBrew Lock only (separate Mac app): lock screen, Touch ID, failed-auth photo+email, Homebrew, $9.99. Not the invoicing 1% fee.
Inputs: no named parameters.
Cryptbrew invoicing fees only: payment fee (1% min 10 sats) and free iOS app. Not CryptBrew Lock — use cryptbrew_lock_info for Lock.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 8 tools
Most tools target a distinct informational topic, but cryptbrew_faq, cryptbrew_about, and cryptbrew_how_it_works overlap for general 'how does it work?' queries. The pricing vs. lock_info boundary is well handled, but the broad-faq catch-all remains a misselection risk.
All tools follow a predictable cryptbrew_<topic> snake_case pattern with no mixed conventions. Names are readable and consistently structured.
The set has 8 tools, which is well-scoped for a product-information server. Each major aspect has a dedicated tool without excessive granularity.
Covers pricing, links, mechanism, Lock app, FAQ, health, contact, and overview. Minor gaps exist for terms/legal details or deeper API reference beyond the links tool, but the core informational surface is solid.
Persistent memory, hybrid search and a goal graph for AI agents, over stdio or remote HTTP.
Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs.
