xdala-workflow-builder
XGR.Network MCP is a connector for XGRChain and the XDaLa on-chain process engine, enabling AI agents to access chain data, inspect process activity, and…
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- Get Chain Status: Use this for live XGRChain status. Returns chain id, latest block number and gas price from JSON-RPC.
- Get Latest Block: Use this when the user asks for the latest EVM block details from XGRChain.
- Get Account Live State: Use this for live EVM account state. Returns balance, nonce and contract code for an address.
What data it sees
Do you need an account
No: the server works without sign-in
XGR.Network MCP is a connector for XGRChain and the XDaLa on-chain process engine, enabling AI agents to access chain data, inspect process activity, and prepare secure workflow actions for user-controlled wallet signing.
How to connect
How to connect xdala-workflow-builder to Claude
The server address to paste into Claude settings:
https://xdala-workflow-builder--xgrnetwork.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect xdala-workflow-builder to ChatGPT
The server address to paste into ChatGPT settings:
https://xdala-workflow-builder--xgrnetwork.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect xdala-workflow-builder to Cursor
The server address to paste into Cursor settings:
https://xdala-workflow-builder--xgrnetwork.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (60)
Raw names from tools/list. Only developers need these.
| get_chain_status | Use this for live XGRChain status. Returns chain id, latest block number and gas price from JSON-RPC. |
| get_latest_block | Use this when the user asks for the latest EVM block details from XGRChain. |
| get_account_live_state | Use this for live EVM account state. Returns balance, nonce and contract code for an address. |
| get_transaction_evidence | Use this when the user asks what happened in a specific transaction. Combines indexed Explorer transaction data, receipt data and live RPC fallback if available. |
| get_transaction_receipt | Use this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data. |
| search_transactions | Read-only chain-wide Explorer DB transaction search. Use for general transaction, native XGR value, from/to address, hash, input, session id, validity/execution, and block/time-range questions; do not sample XDaLa sessions for chain-wide transaction questions. |
| get_recent_value_transfers | Read-only shortcut for recent native XGR value transfers from the Explorer transaction index. Native value transfer means transactions.value > minValueWei and does not include gas fees. |
| get_account_transactions | Read-only chain-wide Explorer DB transaction lookup for one account as sender, recipient, or both. Use this instead of XDaLa session tools for account-wide transaction history. |
| get_block_transactions | Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset. |
| get_transaction_stats | Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters. |
| get_session_transactions | Use this to list the blockchain transactions belonging to an XDaLa session. This returns the timeline of transaction hashes, blocks, fees and iteration steps. It does not return full engine payloads, API saves or contract read results. |
| get_session_status_live | Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id. |
| list_wakeup_targets_by_address | Use this to list WAITING XDaLa runtime steps that the given wallet or Safe address is allowed to wake via RPC. This is read-only and calls xgr_listWakeupTargetsByAddress. |
| resolve_wakeup_payload_schema | Use this to resolve payload fields for one currently WAITING wake-up target from the session snapshot returned by xgr_listWakeupTargetsByAddress. This never calls rule loaders or decrypts XRC-137 rules. |
| get_sessions_overview | Use this for high-level indexed XDaLa session analytics from the Explorer API. |
| find_latest_xdala_session | Use this when the user asks for the latest XDaLa session but does not provide owner and sessionId. This read-only tool resolves the newest indexed XDaLa session from the Explorer database and can optionally include final receipt payload data. |
| get_latest_session_payload | Use this when the user asks for the payload of the latest XDaLa session. This read-only tool resolves the latest indexed session without requiring owner plus sessionId, then returns payload, apiSaves, contractSaves and extras from the final receipt. |
| get_recent_xdala_sessions | Use this to list recent indexed XDaLa sessions from the read-only Explorer database, especially when the user does not know owner and sessionId. Supports optional owner filtering, time windows, result limits and payload enrichment. |
| list_xdala_session_owners | Use this when the user asks which owners had XDaLa sessions, asks for the owner list, or when aggregate results show uniqueOwners but the concrete owner addresses are needed. For “last 3 weeks”, pass windowHours=504. |
| list_xdala_sessions | Use this when the user asks to list XDaLa sessions, enumerate recent sessions, or discover owner/sessionId pairs. This returns concrete owner + sessionId pairs and supports keyset pagination. For “last 3 weeks”, pass windowHours=504. |
| list_xdala_session_ids | Use this when the user asks for session IDs. Always returns session IDs grouped by owner because session IDs are only unique together with owner. |
| get_xdala_session_detail | Use this when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId. |
| get_xdala_session_stats | Use this when the user asks for aggregate XDaLa session statistics, for example “statistics for the last 2 weeks”, “success/failure counts”, “average session duration”, “average steps per session”, “top errors”, or “how many sessions ran recently”. For “last 2 weeks”, pass windowHours=336. |
| get_xdala_session_timeseries | Use this when the user asks for XDaLa sessions over time, for example “sessions per day”, “daily sessions last 2 weeks”, “monthly session trend”, or “success/fail per day”. For “last 2 weeks by day”, pass windowHours=336 and bucket="day". |
| get_xdala_step_stats | Use this when the user asks for step-level XDaLa statistics, for example “how many steps were valid”, “invalid steps”, “failed steps”, “step gas totals”, or “step stats for a session”. |
| get_xdala_payload_key_stats | Use this when the user asks which payload fields/keys occurred, how often payload fields appeared, or which payload fields were empty/non-empty. For “last 14 days”, pass windowHours=336. |
| get_xdala_payload_term_stats | Use this when the user asks for payload terms, payload words, payload Begriff statistics, or a statistic over all payload terms in a time range. For “last 14 days”, pass windowHours=336. Do not sample sessions for this task. |
| get_xdala_payload_field_value_stats | Use this when the user asks which values occurred for a specific payload field, for example “which DocumentType values occurred?” or “top values for ReasonCategory”. |
| get_xdala_active_sessions_timeseries | Use this when the user asks for active/concurrent XDaLa sessions over time. |
| get_session_receipt_logs | Use this to inspect what an XDaLa session actually did. Returns decoded engine receipt data such as input payload, API saves, contract saves, execution contract, rule contract, valid flag, inner gas usage and optional raw receipt logs. Do not use this for a simple transaction timeline; use get_session_transactions instead. |
| get_xgr_core_addresses | Use this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method. |
| get_xgr_circulating_supply | Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply. |
| estimate_xdala_rule_gas | Use this to estimate XDaLa/XRC-137 rule gas. Returns validation gas, branch gas, grant fees and worst-case totals from xgr_estimateRuleGas. |
| get_xrc729_authority | Read-only authority lookup for one XRC-729 orchestration contract. Reads owner()/getOwner() and getExecutorList(), detects zero-address executor wildcard, and never signs, submits, executes, or creates a handoff. |
| find_startable_xdala_workflows | Read-only discovery of deployed XRC-729 workflows that a given address can start as owner, executor, or wildcard executor. Use this whenever the user provides an address and asks which sessions/workflows they can start. This tool does not create session-start handoffs. |
| list_xrc_contracts | Read-only list of indexed XRC-137/XRC-729 contracts globally or filtered by owner/type. |
| get_xrc_contract | Read-only lookup of one indexed XRC contract by address. |
| list_xrc_events | Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range. |
| get_xrc_contract_events | Read-only list of all indexed XRC events for one contract. |
| get_xrc729_ostc_state | Read-only list of indexed OSTC state entries for an XRC-729 contract. |
| get_xrc_owner_summary | Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner. |
| read_xrc729_ostc_json | Read-only eth_call to XRC729.getOSTC(ostcId), returning the runtime OSTC JSON string. |
| read_xrc137_rule_json | Read-only eth_call to XRC137.getRule(), returning the runtime rule JSON string. |
| resolve_xrc729_process_graph | Resolve deployed XRC-729 OSTC runtime JSON and linked indexed XRC-137 rule contracts without mutating chain state. |
| get_xrc_usage | Read-only usage statistics from Explorer PGRO tx_receipts for XRC-137 rules or XRC-729 OSTC/process filters. |
| list_xrc_process_sessions | Read-only list of sessions associated with an XRC-729 OSTC id/hash. |
| find_reusable_xrc137_rules | Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed. |
| get_unused_xrc137_rules | Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage. |
| get_xrc_failure_stats | Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters. |
| create_operation_handoff | Create an offchain human-in-the-loop operation and return a browser URL. The MCP never signs or submits transactions; the user executes locally with a browser wallet on the operation page. Do not use this tool to start, run, launch, execute, or queue XDaLa sessions. Do not use this tool for xgr_validateDataTransfer, SessionPermit, Manage Sessions imports, xgr-session-start@1, XDaLa session start handoffs, or starting a deployed XRC-729 workflow. For these intents, use create_xdala_session_start_handoff. If create_xdala_session_start_handoff is unavailable, report that the session-start tool is unavailable instead of falling back to create_operation_handoff. |
| get_operation_status | Return the current status of an operation handoff. Use this after the user opens the operation page and signs or cancels local wallet transactions. |
| cancel_operation_handoff | Cancel a pending offchain operation handoff. This never cancels already signed or submitted chain transactions. |
| create_xdala_bundle_deploy_handoff | Store a validated xgr-multi-bundle@1 bundle offchain under an unguessable bearer handle and return an XDaLa Workbench import URL. The MCP does not sign, submit, or execute transactions. |
| get_xdala_bundle_deploy_handoff | Return stored metadata, bundle JSON, and any recorded deployed result/artifact for an XDaLa bundle deploy handoff handle. |
| get_xdala_bundle_deploy_result | Return the stored XDaLa bundle deploy result, canonical deployed artifact, and audit events for a handoff handle. This is read-only and never signs, submits, or executes transactions. |
| cancel_xdala_bundle_deploy_handoff | Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions. |
| create_xdala_session_start_handoff | Prepare and store a read-only xgr-session-start@1 handoff for xDaLa Workbench. Use this tool whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session. Use this tool for starting an existing deployed XRC-729/XRC-137 workflow, starting from a runtime XRC-729 orchestration, starting from a bundle deploy result, or importing a canonical xgr-session-start@1 request into xDaLa Manage Sessions. When explaining required input to users, use canonical xgr-session-start@1 terminology: sessions[].orchestration, sessions[].ostcId, sessions[].stepId, sessions[].payload, sessions[].maxTotalGas. Do not ask users for entryStepId; entryStepId is not the Workbench Session Start field. For deployed XRC-729 workflows, first inspect the runtime, identify ostcId and the likely entry step, resolve that step's XRC-137 rule, derive required payload fields from the XRC-137 payload schema, treat fields with defaults as optional, and present required and optional/default fields before creating a handoff. Do not call this tool with guessed payload values. If required start payload fields are missing, first present the required fields to the user and ask for values or explicit permission to use demo values. Only use demo/dummy/example/default values when the user explicitly asks or accepts them. This tool returns a Workbench xdalaUrl such as https://xdala.devnet.xgr.network/session-start/ss_... . The agent must show the returned xdalaUrl to the user. Do not replace the xdalaUrl with a generic /operations/op_... link. The MCP does not sign, submit, or execute. xDaLa Workbench performs local signing and calls xgr_validateDataTransfer. Do not describe the XRC-729 contract owner as the owner of a not-yet-started session; owner()/getOwner() and getExecutorList() identify start-authority roles only. Use sessions[].starterAddress only as an intended starter when explicitly set, and use terminal result data such as result.results[].owner/sessionId/pid for the actual session owner/starter after Workbench start. |
| get_xdala_session_start_handoff | Read stored xDaLa session start handoff metadata, canonical request, authority, derived sessionOwnership role summary, validation, lean result summary, and terminal result. Read-only; does not sign, submit, or execute. Use sessionOwnership to avoid confusing the XRC-729 contract owner with the actual session owner/starter before Workbench completion. |
| cancel_xdala_session_start_handoff | Cancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work. |
| get_xdala_session_start_result | Return terminal xDaLa session start result, lean result summary, and audit events. Read-only preparation/result lookup only; the MCP does not sign, submit, or execute, and users sign locally in Workbench/wallet/local signer. For completed handoffs, prefer result.results[].owner/sessionId/pid over XRC-729 contract owner facts when identifying the actual session owner/starter. |