feat: add bitcoin-mcp ToolServer and Bitcoin SRE Agent#1558
feat: add bitcoin-mcp ToolServer and Bitcoin SRE Agent#1558Bortlesboat wants to merge 1 commit intokagent-dev:mainfrom
Conversation
Add bitcoin-mcp as a contrib ToolServer for Bitcoin network analysis (49 tools including fee estimation, mempool analysis, block inspection, transaction decoding, and mining stats). Also includes a Bitcoin SRE Agent definition with a detailed system prompt covering incident response protocols, tool selection guides, fee interpretation rules, and safety guidelines. bitcoin-mcp is available on PyPI (pip install bitcoin-mcp) and works with zero configuration via the free Satoshi API.
There was a problem hiding this comment.
Pull request overview
Adds a new contributed MCP ToolServer for bitcoin-mcp and an accompanying “Bitcoin SRE” Agent definition so kagent users can run Bitcoin network/node diagnostics and incident-response workflows via MCP tools.
Changes:
- Introduces a
ToolServermanifest that runsbitcoin-mcpviauvx(stdio transport). - Introduces a “Bitcoin SRE Agent” manifest with an incident-response system prompt and A2A skill metadata.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| contrib/tools/bitcoin-mcp/bitcoin-sre-agent.yaml | Adds a Bitcoin SRE Agent definition and A2A skill metadata referencing the bitcoin-mcp toolserver. |
| contrib/tools/bitcoin-mcp.toolserver.yaml | Adds a ToolServer definition to run the bitcoin-mcp MCP server via uvx. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| spec: | ||
| description: >- | ||
| Bitcoin infrastructure SRE agent for incident detection, | ||
| investigation, and response. Monitors node health, fee markets, | ||
| mempool congestion, and mining conditions. | ||
| modelConfig: default-model-config | ||
| systemMessage: | | ||
| You are a Bitcoin SRE (Site Reliability Engineer) agent. Your job is |
There was a problem hiding this comment.
This Agent manifest doesn’t follow the v1alpha2 Agent schema: v1alpha2 requires spec.type and then spec.declarative (or spec.byo) to hold fields like modelConfig, systemMessage, tools, and a2aConfig. With the current top-level spec.modelConfig/spec.systemMessage/spec.tools/spec.a2aConfig, the CRD validation should reject this resource due to unknown/missing required fields. Restructure the manifest to include spec.type: Declarative and move the declarative fields under spec.declarative: (similar to contrib/tools/k8sgpt-mcp-server/k8sgpt-agent.yaml).
| tools: | ||
| - type: McpServer | ||
| mcpServer: | ||
| toolServer: bitcoin-mcp |
There was a problem hiding this comment.
The MCP tool reference format here doesn’t match the v1alpha2 Tool schema. mcpServer expects a typed reference (apiGroup, kind, name, optional namespace) to the tool provider resource, plus optional toolNames/requireApproval. toolServer: bitcoin-mcp is not a recognized field and should be replaced with a typed reference to the ToolServer resource (apiGroup/kind/name), optionally scoping to a subset of toolNames and/or using requireApproval for sensitive tools.
| toolServer: bitcoin-mcp | |
| apiGroup: kagent.dev | |
| kind: ToolServer | |
| name: bitcoin-mcp | |
| namespace: kagent |
| apiVersion: kagent.dev/v1alpha1 | ||
| kind: ToolServer | ||
| metadata: | ||
| name: bitcoin-mcp |
There was a problem hiding this comment.
This ToolServer is namespaced, but the manifest omits metadata.namespace while the agent hard-codes metadata.namespace: kagent. If users apply these manifests without -n kagent, the ToolServer will land in the default namespace and the agent in kagent, causing the agent’s tool reference to fail resolution. Consider adding metadata.namespace: kagent here (or removing the explicit namespace from the agent) so the two resources are consistently installable.
| name: bitcoin-mcp | |
| name: bitcoin-mcp | |
| namespace: kagent |
Summary
Add bitcoin-mcp as a contrib ToolServer and a Bitcoin SRE Agent definition.
ToolServer (
contrib/tools/bitcoin-mcp.toolserver.yaml):pip install bitcoin-mcp/uvx bitcoin-mcpBitcoin SRE Agent (
contrib/tools/bitcoin-mcp/bitcoin-sre-agent.yaml):Why
Bitcoin node operators need 24/7 monitoring. This agent demonstrates kagent's value for financial infrastructure operations — a domain where AI agents can save real time and prevent real incidents.
bitcoin-mcp has 116 tests, 950+ PyPI downloads/month, and is listed on the official MCP Registry.
Test plan
context7.mcp.yamlpattern exactlyuvx bitcoin-mcpinstalls and runs without configuration