MCP Server

The maintained Xian MCP server is xian-mcp-server.

It exposes Xian wallet, query, transaction, indexed-read, crypto, and DEX operations to AI assistants and other tool-calling systems.

Important Safety Rule

This server can hold private keys and submit transactions.

Use it as a local tool. Do not expose it publicly and do not point it at production wallets unless you have deliberately accepted that risk.

Secret-bearing wallet tools are now disabled by default. To enable wallet creation/export, transaction submission helpers, signing, encryption, and decryption, set:

XIAN_MCP_ENABLE_UNSAFE_WALLET_TOOLS=1

Without that opt-in, the MCP server still exposes the safer read/query/indexed inspection surface, but it rejects the unsafe wallet operations.

Those unsafe tools are also omitted from tools/list and the HTTP /tools discovery surface until you opt in, so downstream tool-calling systems only see the read-safe default surface.

Network Configuration

Configure the target network explicitly. Local current-code defaults are:

Variable	Purpose	Local default
XIAN_NODE_URL	Node RPC URL	http://127.0.0.1:26657
XIAN_GRAPHQL	GraphQL endpoint	http://127.0.0.1:5000/graphql
XIAN_CHAIN_ID	Chain ID used for transaction payloads	xian-local-1
XIAN_INCLUDE_RAW	Include raw SDK payloads in responses	false

When in doubt, read result.node_info.network from the node's /status response and use that value for XIAN_CHAIN_ID.

For a current local stack node, point the MCP server at the local RPC and GraphQL endpoints (stack defaults shown):

XIAN_NODE_URL=http://127.0.0.1:26657
XIAN_GRAPHQL=http://127.0.0.1:5000/graphql
XIAN_CHAIN_ID=xian-local-1

Use the chain ID from the node's /status response when running against a custom local network.

Transport Modes

It supports two transport styles:

Mode	Use case
MCP over stdio	desktop assistants and MCP-native clients
HTTP / REST	web apps, custom tool-calling loops, and automation

In HTTP mode, the same tool registry is exposed as:

• GET /tools for discovery
• POST /tools/{name} for invocation

What It Can Do

Current capability groups include:

• read balances, token holdings, contract state, and contract source
• simulate transactions for chi estimation
• read indexed blocks, transactions, events, and state history
• inspect shielded wallet history and shielded output tags
• verify messages and inspect DEX prices

With XIAN_MCP_ENABLE_UNSAFE_WALLET_TOOLS=1, it can also:

• create or import wallets, including HD-wallet flows
• send transactions and token transfers
• sign, encrypt, and decrypt messages
• execute DEX buy/sell helper flows

The implementation sits on top of the maintained Xian SDKs rather than inventing its own chain protocol.

DEX Tools

The DEX tools use the canonical DEX contract names:

• con_pairs for pair discovery and reserves
• con_dex for router-level liquidity and swap behavior
• con_dex_helper for single-pair buy and sell helper flows

get_dex_price is read-only. buy_on_dex and sell_on_dex submit transactions and therefore require XIAN_MCP_ENABLE_UNSAFE_WALLET_TOOLS=1.

The buy/sell helpers send exact decimal amount and slippage values and convert deadline_min into the Xian VM datetime payload expected by the current DEX contracts. The target network must already have the canonical DEX contracts and liquidity for the requested pair.

Typical Uses

• local AI-assisted wallet operations
• agent workflows that need structured Xian tools
• prototyping higher-level automation before building a dedicated app backend

Related Tools

• xian-py
• xian-js
• xian-intentkit