Overview
What is qng-mcp?
qng-mcp is an MCP (Model Context Protocol) server for the qng blockchain network. It exposes blockchain data through standard MCP tools, allowing AI assistants (via MCP clients like mcphost) to query block counts, block details, and state root information.
How to use qng-mcp?
Configure the server in either stdio or SSE mode. For stdio, run the server executable (docker or native) with -rpc pointing to a qng RPC endpoint (e.g., http://127.0.0.1:8545). For SSE, start the server with -t sse and set the client URL to http://localhost:8080/sse. Use an MCP client (e.g., mcphost) with the appropriate config file.
Key features of qng-mcp
- Supports stdio and SSE transport modes
- Provides tools for blockchain queries
- Extensible via
config.json - Works with any MCP‑compatible client
- Lightweight: runs as a Docker container or standalone executable
Use cases of qng-mcp
- Query the latest block count on the qng network
- Retrieve transaction details of a specific block by order
- Fetch state root and EVM state information for a given block
- Integrate qng blockchain data into AI‑powered assistants
- Extend server capabilities by editing
config.json
FAQ from qng-mcp
What is qng-mcp and what does it do?
It is an MCP server for the qng blockchain. It lets MCP clients (like mcphost) call tools to fetch block counts, blocks by order, and block state roots from a qng RPC endpoint.
How do I run qng-mcp?
You can run it via Docker (docker run -i --rm qng_mcp_server -rpc http://127.0.0.1:8545) or as a native executable (./qng_server.exe -rpc http://127.0.0.1:8545/). For SSE mode, start with -t sse.
What tools does qng-mcp expose?
Based on the example usage, the server provides at least three tools: get_block_count, get_block_by_order, and get_block_stateroot.
Can I add new capabilities to qng-mcp?
Yes. The README states: “If you want more capabilities please extend config.json”.
What are the transport and runtime requirements?
The server requires a running qng RPC endpoint (default http://127.0.0.1:8545). It supports stdio (via Docker or the native binary) and SSE (HTTP) transport. No additional authentication or dependencies are mentioned in the README.
