XGR MCP Gateway

Table of contents

1. Abstract
2. Purpose
3. Position in the XGR architecture
4. Public MCP endpoints
5. Example MCP client configuration
6. Tool domains
7. Agent-assisted workflow creation
8. Security boundary
9. Typical queries
10. References

Abstract

The XGR MCP Gateway is the AI-native access layer to the XGR stack. It exposes XGRChain data, XDaLa sessions, Explorer evidence, XRC standards, schemas and authoring knowledge as semantic Model Context Protocol tools.

The gateway allows MCP-compatible agents to inspect deployed workflows, reason over XDaLa sessions, draft and validate process bundles, and prepare human-in-the-loop handoffs for local wallet signing.

1. Purpose

The XGR MCP Gateway provides an agent-facing interface for reading, reasoning, authoring, validation and handoff preparation. It does not alter the XGRChain protocol, transaction format, consensus model or token economics.

Its purpose is to make XGRChain and XDaLa accessible to AI agents without weakening the user-controlled signing and custody model.

2. Position in the XGR architecture

The gateway is a fourth surface alongside the Chain, XDaLa and the Workbench.

3. Public MCP endpoints

https://mcp.xgr.network/mcp

https://mcp.testnet.xgr.network/mcp

4. Example MCP client configuration

{
  "mcpServers": {
    "xgr-mainnet": {
      "type": "http",
      "url": "https://mcp.xgr.network/mcp"
    },
    "xgr-testnet": {
      "type": "http",
      "url": "https://mcp.testnet.xgr.network/mcp"
    }
  }
}

5. Tool domains

The gateway groups tools by semantic domain instead of exposing only raw RPC mirrors. This improves tool selection for agents and keeps interactions deterministic.

• Chain: live RPC status, latest blocks and account state.
• XGR protocol: core addresses, circulating supply and rule gas estimation.
• Session evidence: XDaLa session status, timelines, receipts, payloads and evidence.
• Transactions: indexed transaction search, value transfers, account history and transaction evidence.
• XRC: XRC-137/XRC-729 inspection, process graph resolution, usage and failure analytics.
• Knowledge: standards, schemas, examples and validators for XDaLa authoring.
• Diagram: Mermaid rendering for process graphs.
• Operations / Handoff: preparation and tracking of bundle-deploy and session-start handoffs.

6. Agent-assisted workflow creation

A typical workflow starts with natural language intent and ends with a user-controlled signing step.

1. The user describes the desired XDaLa process.
2. The agent reads the relevant XDaLa authoring rules, XRC references and schemas through MCP.
3. The agent drafts XRC-137 rules and an XRC-729 orchestration or a complete XGR MultiBundle.
4. The gateway validation tools check the generated artifact before it is treated as final.
5. The gateway prepares a handoff for Workbench review.
6. The user reviews the prepared action and signs locally with their own wallet.

7. Security boundary

The MCP Gateway is deliberately non-custodial. It does not receive signing material and does not sign transactions.

• No custody of assets is introduced.
• Write operations are prepared as handoffs.
• Final authorization remains with the user and their wallet.

This keeps the trust boundary explicit: the agent can help create and validate intent; the user remains responsible for approval and signing.

8. Typical queries

9. Relationship to whitepapers and references

This technical note complements the XGR Chain Technical Whitepaper. It does not modify the chain-level protocol baseline and does not belong to the MiCAR token disclosure. MCP is an agent-facing access layer for interaction, evidence inspection, authoring, validation and handoff preparation.

• XGR MCP Gateway Overview
• XGR MCP Tool Reference
• XGR MCP Operation Handoff
• XGR MCP Authoring & Knowledge
• XGR specifications repository