@bxetech/bpe-mcp
v0.1.1
Published
MCP server for the BPE (Bitcoin Pricing Engine) market-data API. Lets Claude Desktop, Cursor, and other MCP-enabled agents query consolidated BTC pricing, ML signals, funding-rate skew, and natural-language market briefings.
Downloads
49
Maintainers
Readme
BPE MCP Server
Model Context Protocol server for the BPE market-data API. Lets Claude Desktop, Cursor, Goose, and other MCP-enabled agents query consolidated Bitcoin pricing, ML signals, funding-rate skew, and natural-language market briefings — without writing any HTTP boilerplate.
Status: v0.1 prototype. Four tools, local stdio transport, no LLM calls inside the briefing endpoint (template-rendered). API key required.
Why use it
If you're building an agent that touches Bitcoin markets, you have two options today:
- Talk to 36 different exchange APIs directly. Each has a different schema, different auth, different rate limits, different reliability. Your agent burns tokens reasoning over inconsistent payloads.
- Use one consolidated source. BPE aggregates all 36 venues into a single normalised feed with derived signals (ML predictions, sentiment, funding skew, basis). One auth, one schema, one tool call.
This MCP server is option 2 dressed up as native tools your agent can discover and call.
Tools (v0.1)
| Tool | What it does |
|---|---|
| get_consolidated_price | Current BTC price aggregated across the BPE network |
| get_market_briefing | 5–8 line natural-language market summary (price, funding, ML, sentiment, anomalies) |
| get_funding_skew | Per-venue annualised funding rates + max-spread pair |
| get_ml_signal | Current ML prediction across configurable time horizons |
Install
npm install -g @bxetech/bpe-mcpOr use npx with no install (recommended for Claude Desktop):
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"bpe": {
"command": "npx",
"args": ["-y", "@bxetech/bpe-mcp"],
"env": {
"BPE_API_KEY": "bpe_..."
}
}
}
}Restart Claude Desktop. The four tools appear under the MCP server picker.
Configuration
| Env var | Default | Notes |
|---|---|---|
| BPE_API_KEY | (required) | Get one at https://bxetech.com/contact |
| BPE_BASE_URL | https://mcp.bxetech.com | Override for self-hosted / local dev |
| BPE_TIMEOUT_MS | 5000 | Per-request timeout |
Local development
git clone https://github.com/bxetech/bpe-mcp
cd bpe-mcp
npm install
npm run build
BPE_API_KEY=... npm run devTo dogfood in Claude Desktop while iterating, point at the local build:
{
"mcpServers": {
"bpe-dev": {
"command": "node",
"args": ["/abs/path/to/mcp-server/dist/index.js"],
"env": {
"BPE_API_KEY": "...",
"BPE_BASE_URL": "http://localhost:8082"
}
}
}
}Roadmap
- v0.2 —
get_basis,get_sentiment_snapshot,subscribe_alert(webhook subscription) - v0.3 — Hosted HTTP transport for non-developer install (Cursor extension, ChatGPT Desktop)
- v0.4 — Optional LLM-rendered briefing via Haiku (richer prose, with per-call cost)
See docs/research/AGENT_INTEGRATION_AND_MONETISATION_2026-04-27.md for the broader product / monetisation plan.
License
MIT — see LICENSE.
