Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for the Chia blockchain. Read-only full-node access via Coinset hosted nodes, 36 tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"chia": {
"command": "npx",
"args": [
"-y",
"chia-mcp"
]
}
}
}Run this in your terminal
claude mcp add chia -- npx -y chia-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"chia": {
"command": "npx",
"args": [
"-y",
"chia-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"chia": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"chia-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The publisher (danieljperry) is not the repo owner (Chia-Network); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 24 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol (MCP) server that exposes 36 tools for querying the Chia blockchain (up to 38 with push_tx and local-node options). Uses Coinset hosted nodes — no local Chia node required.
Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"] } } }
claude mcp add chia -- npx -y chia-mcp
claude mcp add chia --env CHIA_NETWORK=testnet11 -- npx -y chia-mcp
Add to .cursor/mcp.json in your project or ~/.cursor/mcp.json globally:
{
"mcpServers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"] } } }
Add to your User Settings (JSON) or .vscode/mcp.json:
{
"mcp": { "servers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"] } } } }
Set CHIA_NETWORK to use testnet11:
{
"mcpServers": { "chia": { "command": "npx", "args": ["-y", "chia-mcp"], "env": { "CHIA_NETWORK": "testnet11" } } } }
| Variable | Default | Description |
|---|---|---|
CHIA_NETWORK | mainnet | Network to connect to: mainnet or testnet11 |
CHIA_FULL_NODE_URL | _(auto from network)_ | Override the full node RPC endpoint URL (e.g., https://api.coinset.org or your own node). Local Chia nodes require mTLS client certificates; use a reverse proxy that terminates mTLS since chia-mcp does not support client certificates directly. |
CHIA_MCP_ENABLE_PUSH_TX | _(unset)_ | Set to 1 or true to enable the push_tx tool (disabled by default for safety) |
[start, end).[start, end).complete flag. This is the correct way to check a balance.offer1...) into a structured summary: coin spends, amounts, coin IDs, puzzle sizes, signature status. Uses the official chia-wallet-sdk for correct parsing.max_depth hops.get_additions_and_removals (which can be 1+ MB).Quick reference showing input → output shape for the most commonly used tools.
Input: {} (no parameters)
Output: { peak_height: 9470000, sync: { synced: true }, difficulty: 2528, space: "33501849665552384", mempool_size: 3, ... }
Input: { name: "0xabc123..." }
Output: { coin: { parent_coin_info: "0x...", puzzle_hash: "0x...", amount: 1750000000000 }, confirmed_block_index: 5000000, spent_block_index: 5000042, coinbase: false, timestamp: 1700000000 }
Input: { puzzle_hash: "0xabc123...", include_spent_coins: false }
Output: [ { coin: { ... }, confirmed_block_index: ..., spent_block_index: 0 }, ... ] Note: Response truncated at 50KB. For complete balance, use get_address_summary instead.
Input: { address: "xch1abc123..." }
Output: { total_balance_mojos: "1750000000000", total_balance_xch: "1.75", coin_count: 3, complete: true, oldest_coin_height: 4500000, newest_coin_height: 9400000 } Note: Pages through ALL unspent coins. The complete flag indicates whether the full balance was reached.
Input: { coin_id: "0xabc123...", max_depth: 10 }
Output: { lineage: [ { coin_id: "0x...", parent: "0x...", amount: 1750000000000, height: 5000042 }, ... ], depth_reached: 5, reached_coinbase: true }
Input: { header_hash: "0xabc123..." }
Output: { height: 5000042, is_transaction_block: true, num_additions: 12, num_removals: 6, total_amount_created: "3500000000000", total_amount_spent: "3500000000000", top_movements: [ ... ] } Note: Much smaller than raw get_additions_and_removals (which can be 1+ MB).
Input: { offer: "offer1..." }
Output: { valid: true, summary: { offered: { xch: "1.0" }, requested: { "asset_id_abc...": 100 } }, coin_spends: 3, has_signature: true }
Input: { puzzle_hash: "0xabc123...", prefix: "xch" }
Output: { address: "xch1abc123..." } Note: Local computation — no RPC call.
Input: { address: "xch1abc123..." }
Output: { puzzle_hash: "0xabc123..." } Note: Local computation — no RPC call.
Input: { parent_coin_info: "0x...", puzzle_hash: "0x...", amount: 1750000000000 }
Output: { coin_id: "0xabc123..." } Note: SHA256(parent + puzzle_hash + amount). Accepts string amounts for values > Number.MAX_SAFE_INTEGER.
This server wraps the Chia full node RPC API using Coinset's hosted endpoints:
https://api.coinset.org/ https://testnet11.api.coinset.org/ All RPC calls are simple HTTP POST requests with JSON bodies. No authentication required.
Most tools work against any Chia full node (Coinset-hosted or your own). Three tools are Coinset extensions — they do not exist in chia-blockchain's full node RPC API and will return HTTP 404 against a local node or the simulator:
| Tool | Coinset | Local node / Simulator |
|---|---|---|
get_puzzle_and_solution_with_conditions | ✅ | ❌ — use get_puzzle_and_solution + local CLVM eval |
get_memos_by_coin_name | ✅ | ❌ |
get_coin_records_by_hints | ✅ | ❌ — only singular get_coin_records_by_hint exists |
Simulator portability: Code written against Coinset's extended endpoints will not work against the simulator or a local node. The simulator (
chia dev sim) and standardchia-blockchainnodes support the same standard RPC surface. Develop against the simulator using standard RPCs for maximum portability; use Coinset extensions for production querying convenience.
Shared RPCs: get_network_info and get_aggsig_additional_data are shared RPC endpoints available on all Chia services (not full-node-specific). They work on both Coinset and local nodes.
Deliberately omitted RPCs: Three upstream full node RPCs are not exposed as tools: get_constants (static data better served by constants.json), get_recent_signage_point_or_eos (internal consensus detail not useful for agents), and create_block_generator (timelord/farmer internal). All other full node RPCs are exposed.
The server provides 9 prompts that encode tool sequencing and failure modes for common Chia tasks:
| Prompt | Description |
|---|---|
network_status | Check the current state of a Chia network: peak height, sync status, difficulty, mempool. |
address_balance | Check the XCH balance of a Chia address using get_address_summary for accuracy. |
coin_lookup | Look up a specific coin by its coin ID and inspect its details. |
trace_lineage | Trace a coin's parent chain to understand where funds came from. |
block_summary | Summarize a block's contents: transaction count, value moved, top addresses. |
transaction_status | Check whether a transaction is confirmed, in mempool, or dropped. |
offer_safety | Evaluate whether a Chia offer is safe to accept (hidden spends, asset verification, expiry). |
token_verification | Verify whether tokens (CATs) are legitimate by checking the asset ID against trusted registries. |
fee_selection | Determine the appropriate fee for a Chia transaction based on current network conditions. |
Only the beginning is shown; read the rest in the repo