The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the XGR MCP Gateway listing page.
XGR MCP Gateway provides AI-native access to the XGR.Network stack through the Model Context Protocol. It connects MCP-compatible agents such as Claude, ChatGPT, IDE assistants and custom hosts to XGRChain, XDaLa sessions, Explorer data, XRC standards and owner-reviewed on-chain action preparation.
The gateway is designed for agent-assisted workflow creation: agents can inspect live chain evidence, reason over XDaLa process state, draft XRC artifacts and prepare handoffs that a user reviews and signs locally.
The gateway never requests, receives, stores or controls user or third-party private keys and cannot sign on behalf of users. User write intents are prepared as handoffs and signed locally. An optional starter-gas service may use a dedicated server-controlled funding key solely to send fixed XGR gas grants from the service wallet.
Mainnet:
Testnet:
Use mainnet to inspect real XGRChain and XDaLa activity. Use testnet to safely draft, validate and experiment with agent-driven workflows before production use.
For clients that still expect http instead of streamable-http, use the same endpoint URL and select the HTTP/remote MCP transport offered by your client.
get_xgr_network_info for canonical XGR.Network, XGRChain, XDaLa, RPC, Explorer, MCP, documentation and ecosystem metadata.get_xgr_network_info returns versioned, machine-readable metadata for XGR.Network and its ecosystem. Agents should use it when users request official project information, network configuration, RPC or Explorer endpoints, MCP connection details, documentation, XRC standard context or source repositories.
get_chain_status remains the live JSON-RPC status tool and additionally returns compact official entry points for the connected XGRChain mainnet.
XGR.Network MCP is built around deterministic process infrastructure rather than generic chat automation. It gives agents structured access to the XGR stack while keeping user signing, user custody and final approval outside the gateway.
This makes it suitable for:
Full reference lives in the central XGR documentation:
The gateway can be operated against your own XGRChain RPC and Explorer instance. Self-hosting requires an Explorer deployment with a read-only Postgres mirror for transaction search and session analytics tools.
Typical setup flow:
Required runtime configuration is documented in Setup & Configuration.
reserved, broadcast, confirmed and failed states.io.github.xgr-network/xdala-workflow-builderLicensed under the Apache License 2.0.
The optional purchase tools are mainnet-only, disabled by default, and are never registered by testnet. Enable them only with XGR_PURCHASE_TOOLS_ENABLED=true, XGR_PURCHASE_NETWORK=mainnet, a valid HTTPS API URL (or local HTTP), and a maximum at or below 249.99 EUR.
quote_xgr_purchase is optional planning only. create_xgr_purchase_order creates the real order in one call to POST /api/orders; the website confirmation modal is not a separate API phase. The backend is authoritative for the final price, crypto amount, custody wallet, payment reference, and reservation. The MCP holds no user or third-party private keys and does not pay; an external wallet agent can execute the returned exact payment instruction.
The 249.99 EUR maximum is an MCP policy for autonomous orders. Separately, the XGR_Web backend requires a complete billing address from a newly calculated net_eur >= 250; it is not a backend order maximum. A backend repricing/address error is returned without retrying the order.
Purchase tools distinguish fixed-XGR orders from conservative USDC/USDT budget orders. The live backend POST determines the binding market price and exact amount_crypto; EUR is only a policy/reference value. A budget order whose exact returned amount exceeds its cap is not paid and its existing reservation expires normally.
Where enabled, get_xgr_starter_gas_options exposes the current fixed grant and eligibility policy. request_xgr_starter_gas sends one fixed 1 XGR grant from a dedicated service wallet to an eligible low-balance EVM address. Agents should use it before deployments, session starts, contract calls or other on-chain actions when the target address lacks native XGR for gas.
The service does not request an address-ownership proof and does not use proof-of-work. Abuse is bounded through one confirmed grant per address, an hourly cap, a daily cap, recipient-balance eligibility, a low-balance service wallet and a limited number of retries after pre-broadcast failures.