Xgr Mcp

What is XGR MCP Gateway? XGR MCP Gateway is a Model Context Protocol (MCP) gateway that gives AI agents (Claude, ChatGPT, IDE assistants, custom hosts) structured, AI-native access to the XGR.Network stack — including XGRChain, XDaLa sessions, Explorer data, XRC standards and owner-reviewed on-chain action preparation. It is designed for agent-assisted workflow creation while keeping signing and key custody strictly local to users.

How to use XGR MCP Gateway?

• For quick use, point an MCP-capable client to the public endpoints:
  • Mainnet: https://mcp.xgr.network/mcp
  • Testnet: https://mcp.testnet.xgr.network/mcp
• Client configuration example: add the endpoints under mcpServers (supports streamable-http or http transports).
• Typical flows: agents read chain/session state, draft XRC artifacts or handoffs, and present owner-signed handoffs for local signing. Optional starter-gas grants can be requested where enabled.
• Self-hosting: deploy against your XGRChain RPC and Explorer (requires Explorer with a read-only Postgres mirror). Build/run via npm (install, typecheck, build, start) and supply documented runtime config.

Key features

• Streamable MCP endpoints for mainnet and testnet
• Read live XGRChain state, blocks, account and transaction evidence
• Inspect and explain XDaLa sessions, process steps and receipts
• Search Explorer history, transaction and session analytics
• Work with XRC standards (XRC-137, XRC-729): author, validate and bundle artifacts
• Prepare owner-reviewed, local-sign handoffs (no gateway signing)
• Optional starter-gas service: fixed 1 XGR grant with eligibility and caps
• Official network metadata endpoint (get_xgr_network_info) for canonical config
• Self-hostable with documented setup and configuration

Use cases

1. AI-assisted Web3 workflow design and process drafting
2. Authoring and validating XRC-compliant artifacts and deployment bundles
3. Inspecting and auditing XDaLa process state and execution evidence
4. Agent-driven onboarding: preparing transactions and handoffs for user signing
5. Development and testing on testnet before mainnet deployments
6. Deterministic, compliance-oriented process automation interfacing with EVM-compatible flows

FAQ

• Does the gateway hold or sign user private keys?

No. The gateway never requests, receives, stores or controls user or third-party private keys. Transactions are prepared as handoffs and must be signed locally by the user or their custody solution.

• What is the starter-gas service and is it safe?

Starter-gas is an optional service that can send a fixed 1 XGR grant from a dedicated service wallet to eligible low-balance addresses. It is tightly rate-limited (one confirmed grant per address, hourly/daily caps), stored atomically in SQLite, and cannot sign on behalf of users.

• Which endpoint should I use for testing vs production?

Use the testnet endpoint to draft, validate and experiment safely. Use mainnet to inspect and operate on real XGRChain/XDaLa activity.

• Can I self-host the gateway?

Yes. Self-hosting is supported but requires an Explorer deployment with a read-only Postgres mirror for search/analytics. Setup and runtime configuration are documented in the project’s Setup & Configuration docs.

• Where to find documentation and code?

Source code: https://github.com/xgr-network/xgr-mcp. Docs: https://xgr.network/docs/ (Gateway Overview, Tool Reference, Handoff, Knowledge, Setup).