Xiangqi

Xiangqi — connector documentation

• MCP endpoint: https://xiangqi.connectorbay.com/mcp
• REST API: POST https://xiangqi.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://xiangqi.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://xiangqi.connectorbay.com/health · Tool schemas: https://xiangqi.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/xiangqi · agent@connectorbay.com

What Xiangqi is for

A hand-curated Xiangqi (Chinese chess) reference — piece moves, the river & palace, the cannon's jump-capture, strategy and notation.

What it does

Xiangqi is a fully local, hand-curated Chinese chess reference. piece_info gives one piece's full detail: how it moves, its Chinese name and pinyin, notation abbreviation, where it's restricted to (the palace, or never crossing the river), any special rule, and its relative value. piece_comparison lines up two named pieces' movement, restrictions and value side by side. rule_lookup explains a rule topic in depth: board setup, the river (河界) that the elephant can never cross and that changes a soldier's movement, the palace (九宫) that confines the general and advisors, the flying-general rule against two exposed generals, the cannon's signature jump-capture over a single screening piece, the horse/elephant blocking restrictions (hobbling the horse's leg, blocking the elephant's eye), check/checkmate/stalemate (a loss, not a draw, in xiangqi), and perpetual-check/perpetual-chase repetition rules. term_glossary defines common terms like jiangjun, kunbi, zhong pao and pingfeng ma. opening_concept explains a named opening (Central Cannon, Screen Horses, Three-Step Tiger, ...) or the Advisor-Elephant Fortress defensive formation. strategy_concept explains general strategic ideas like keeping the fortress intact or counting local attackers versus defenders. notation_reference explains how moves are written in both WXF coordinate notation and traditional Chinese notation with a worked example. beginner_tips gives a ranked shortlist of the most essential things to learn first. Keyless; fully local; zero upstream calls; nothing stored.

What it is not

Not an official product of, or affiliated with, any brand, league, publisher, or organization it may factually mention. Xiangqi is a hand-curated reference and design tool, not a substitute for an official rulebook, certified instruction, or professional advice. Fully local, zero upstream calls, nothing stored.

Tools

Pieces

piece_info — Full detail for one Xiangqi piece: how it moves, its Chinese name/pinyin, notation abbreviation, category, where it's restricted to (palace-only, or never crossing the river), any special rule (flying general, cannon jump-capture, hobbled horse's leg, blocked elephant's eye), and its relative value. Use for "how does the horse move in xiangqi", "can the elephant cross the river", "how does the cannon capture". Args: name.

piece_comparison — Side-by-side comparison of two named pieces' movement, restrictions, special rules and relative value. Use for "chariot vs cannon, which is stronger", "horse vs elephant", "advisor vs soldier". Args: piece_a, piece_b.

Rules

rule_lookup — In-depth explanation of one Xiangqi rule topic — board/setup, the river (河界), the palace (九宫), the flying-general rule, the cannon's signature jump-capture, the horse/elephant blocking restrictions, check and checkmate (and stalemate, which is a loss rather than a draw), or perpetual-check/perpetual-chase repetition rules. Omit topic to list every available topic. Use for "what's the flying general rule", "how does the cannon actually capture", "is stalemate a draw in xiangqi". Args: topic.

Reference

term_glossary — Definitions of common Xiangqi terms — jiangjun (check), jiangsi (checkmate), kunbi (stalemate-loss), zhong pao (central cannon), pingfeng ma (screen horses), changjiang/changzhuo (perpetual check/chase), and more, each with its Chinese spelling. Use for "what does jiangjun mean", "what's kunbi", "what's the difference between changjiang and changzhuo". Args: term.

notation_reference — How Xiangqi moves are written down: board coordinates, WXF-style coordinate notation, traditional Chinese notation, a worked example move, and a symbol summary table (advance, retreat, level move). Use for "how do you write down a xiangqi move", "what does C2=5 mean", "what does 平 mean in notation".

Strategy

opening_concept — Explains a named Xiangqi opening (Central Cannon, Screen Horses, Same-Direction Cannons, Three-Step Tiger, ...) or the Advisor-Elephant Fortress defensive formation — what it is and its key idea. Omit name to list all. Use for "what's a Central Cannon opening", "what's the advisor-elephant fortress", "what defense goes with central cannon". Args: name.

strategy_concept — Explains a general Xiangqi strategic concept — keeping the fortress intact, valuing a cannon by its available mounts, getting chariots onto open files, watching for hobbled horses, counting local attackers vs defenders, avoiding perpetual-check patterns, and more — each with a short example. Omit name to list all. Use for "how do I get better at xiangqi", "why does my cannon need a mount", "what does counting attackers and defenders mean". Args: name.

beginner_tips — A curated, ranked shortlist of the most essential things a new Xiangqi player should know first, from most to least essential. Use for "what should a beginner learn first", "give me xiangqi tips", "how do I get started". Args: count.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/xiangqi/support

Xiangqi — Privacy Policy

Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Xiangqi is. Xiangqi is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated Xiangqi (Chinese chess) reference — piece moves, the river & palace, the cannon's jump-capture, strategy and notation. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Xiangqi is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Xiangqi — Terms of Service

Effective 25 September 2026. These terms govern use of the Xiangqi connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Xiangqi is a fully local, hand-curated Chinese chess reference.
2. A reference, not professional advice. Xiangqi is an independent reference and hobby/game-design tool, not affiliated with or endorsed by any brand, organization, league, or publisher it may factually mention. It does not provide legal, financial, medical, or safety-certification advice, and is not a substitute for supervised instruction where real physical risk is involved.
3. Content varies. Rules, terminology and conventions described here reflect commonly-cited general practice; local house rules, regional variants, and official governing-body rulebooks may differ.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/xiangqi

Xiangqi support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://xiangqi.connectorbay.com/mcp
• REST API: https://xiangqi.connectorbay.com/openapi.json
• Live status: https://xiangqi.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Xiangqi never asks for them.