mcpbeat

XDaLa Workflow Builder MCP Server

io.github.xgr-network/xdala-workflow-builder
answering

XDaLa Workflow Builder is answering right now. Last checked 2 min ago. It exposes 88 tools. Last commit 26 Jul 2026.

Remote MCP server for XDaLa workflow preparation on XGR.Network.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
88
Tools
read from the server
204 ms
Response time
average over 24h
0
Stars
last commit 26 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add xdala-workflow-builder --transport http https://mcp.xgr.network/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "xdala-workflow-builder": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.xdala-workflow-builder]
url = "https://mcp.xgr.network/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "xdala-workflow-builder": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "xdala-workflow-builder": {
      "url": "https://mcp.xgr.network/mcp"
    }
  }
}

Available tools 88

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

xdala
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.
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_active_sessions_timeseries
Use this when the user asks for active/concurrent XDaLa sessions over time.
get_xdala_authoring_rules
Use this before creating, modifying or reviewing XRC/XDaLa artifacts.
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.
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_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_process_mermaid
Render an XDaLa XRC-729 process graph from runtime, bundle, or bundle handoff data as Mermaid flowchart text. Read-only; does not sign, submit, or execute transactions.
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_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.
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.
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”.
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.
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.
xgr
create_xgr_purchase_order
Create one live mainnet order for a fixed XGR amount.
create_xgr_purchase_order_by_budget
Create one conservative USDC/USDT budget order; payment may be blocked after exact backend check.
get_xgr_circulating_supply
Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.
get_xgr_core_addresses
Use this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method.
get_xgr_doc
Retrieve canonical Markdown documentation for an XGR/XDaLa topic.
get_xgr_multibundle_reference
Retrieve canonical xgr-multi-bundle@1 Markdown documentation.
get_xgr_multibundle_schema
Retrieve canonical XGR MultiBundle schema.
get_xgr_network_info
Use this when the user asks what XGR.Network, XGRChain or XDaLa is, or requests official XGR URLs, chain metadata, RPC, Explorer, MCP, testnet faucet, documentation, XRC standards, source repositories or ecosystem entry points. Returns canonical project metadata and links; use get_chain_status for live chain state.
get_xgr_purchase_options
Read available mainnet purchase options.
get_xgr_session_start_schema
Retrieve canonical Workbench xgr-session-start@1 handoff schema.
get_xgr_standard_example
Retrieve a concrete JSON example for XRC-137 or XRC-729.
get_xgr_standard_reference
Use this before drafting XRC-137 or XRC-729 artifacts.
get_xgr_standard_schema
Retrieve machine-readable JSON schema for XGR standards.
get_xgr_starter_gas_options
Check whether free native XGR starter gas is available for a low-balance EVM address. Use this before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. Returns the fixed 1 XGR grant policy and the tool to call next.
list_xgr_docs
List canonical Markdown documentation topics served by the MCP knowledge base.
list_xgr_standard_examples
List available example artifacts for a standard.
list_xgr_standards
List agent-readable XGR and XDaLa standards available in the MCP knowledge base.
xrc
get_xrc_contract
Read-only lookup of one indexed XRC contract by address.
get_xrc_contract_events
Read-only list of all indexed XRC events for one contract.
get_xrc_failure_stats
Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters.
get_xrc_owner_summary
Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner.
get_xrc_usage
Read-only usage statistics from Explorer PGRO tx_receipts for XRC-137 rules or XRC-729 OSTC/process filters.
list_xrc_contracts
Read-only list of indexed XRC-137/XRC-729 contracts globally or filtered by owner/type.
list_xrc_events
Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range.
list_xrc_process_sessions
Read-only list of sessions associated with an XRC-729 OSTC id/hash.
validate
validate_xdala_blueprint
Validate XRC-729 OSTC plus per-step XRC-137 payload-flow consistency.
validate_xdala_bundle
Alias for validate_xgr_multibundle.
validate_xdala_rules
Validate rule expressions against available placeholder fields.
validate_xgr_multibundle
Validate canonical deployable xgr-multi-bundle@1.
validate_xgr_session_start
Validate legacy low-level session-start payload only.
validate_xgr_session_start_handoff
Validate a canonical Workbench xgr-session-start@1 request.
validate_xrc137_authoring
Validate a drafted XRC-137 authoring object.
xrc729
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.
get_xrc729_ostc_state
Read-only list of indexed OSTC state entries for an XRC-729 contract.
list_xrc729_contracts_by_executor
Read-only Explorer lookup for active XRC-729 executor relations of one address. This is index-backed, does not scan contracts, and returns Explorer pagination metadata.
read_xrc729_ostc_json
Read-only eth_call to XRC729.getOSTC(ostcId), returning the runtime OSTC JSON string.
cancel
cancel_operation_handoff
Cancel a pending offchain operation handoff. This never cancels already signed or submitted chain transactions.
cancel_xdala_bundle_deploy_handoff
Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.
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.
latest
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_block
Use this when the user asks for the latest EVM block details from XGRChain.
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.
recent
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_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_recent_operations
List recent offchain operation handoffs. Secrets and browser execution tokens are never returned by this tool.
session
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_session_status_live
Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.
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.
transaction
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.
get_transaction_stats
Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.
account
get_account_live_state
Use this for live EVM account state. Returns balance, nonce and contract code for an address.
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.
operation
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.
resolve
resolve_wakeup_payload_schema
Use this to resolve payload fields for one currently WAITING wake-up target. It reads XRC-729.getOSTC(step -> XRC-137) and XRC-137.getRule() via eth_call for plain JSON rules. Encrypted rules are not decrypted server-side.
resolve_xrc729_process_graph
Resolve deployed XRC-729 OSTC runtime JSON and linked indexed XRC-137 rule contracts without mutating chain state.
block
get_block_transactions
Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.
chain
get_chain_status
Use this for live XGRChain status. Returns chain id, latest block number and gas price from JSON-RPC, plus official XGR.Network entry points for the connected mainnet.
estimate
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.
quote
quote_xgr_purchase
Non-binding USDC/USDT budget planning only.
request
request_xgr_starter_gas
Use this tool when a user or agent needs native XGR to pay transaction fees on the configured XGR network. It sends one fixed 1 XGR grant from a dedicated server-controlled funding wallet to an eligible low-balance EVM address. Use it before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. One confirmed grant per address; client-IP request limits apply; no repayment is required. The service never requests, receives or stores user or third-party private keys and cannot sign on behalf of users.
reusable
find_reusable_xrc137_rules
Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.
sessions
get_sessions_overview
Use this for high-level indexed XDaLa session analytics from the Explorer API.
startable
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.
transactions
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.
unused
get_unused_xrc137_rules
Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.
wakeup
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, then enriches public/plain XRC rule payload metadata via eth_call when available.
xrc137
read_xrc137_rule_json
Read-only eth_call to XRC137.getRule(), returning the runtime rule JSON string.

Endpoints

URLTransportStateLatencyChecked
https://mcp.xgr.network/mcp streamable-http answering 194 ms 2 min ago

XDaLa Workflow Builder — questions

Answers built from our own checks of this server.

What can XDaLa Workflow Builder do?
It exposes 88 tools, read directly from the server on our last check. Among them: cancel_operation_handoff, cancel_xdala_bundle_deploy_handoff, cancel_xdala_session_start_handoff, create_operation_handoff, create_xdala_bundle_deploy_handoff, create_xdala_session_start_handoff and 82 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is XDaLa Workflow Builder mostly used for?
Its tools cluster around xdala, xgr and xrc. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is XDaLa Workflow Builder working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 204 ms. The bar chart above shows every period we have measured.
How do I connect XDaLa Workflow Builder?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does XDaLa Workflow Builder need an API key?
No. XDaLa Workflow Builder completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 88 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is XDaLa Workflow Builder?
It answers our handshake in 204 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is XDaLa Workflow Builder open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.