An MCP server that gives AI agents expert-level access to Qeasy's continuously synced knowledge across two product lines: e-commerce financial reconciliation (12 knowledge domains, platform topics and customer cases; general methodology and accounting standards are public) and the data integration platform (K1 operations & maintenance, K2 APIs & metadata, K3 design patterns; layered public access). Agents search, inspect and fetch exact evidence with Git-traceable citations — then generate the answer themselves. Standard keys search public knowledge; platform playbooks and customer cases require authorization. One stateless HTTP endpoint: POST /api/mcp.
The tool surface is discoverable at runtime through MCP `tools/list`. No SDK or generated client is required — any MCP-compatible agent (Claude, Cursor, custom) can connect over plain JSON-RPC.
Hybrid vector + keyword retrieval over the reconciliation knowledge base. Parameters: query (required); product, type filters; limit (1–20, default 8); granularity ('doc' default, or 'atom' for one hit per KA-* knowledge atom); includeMeta (add domain/platform metadata). Returns ranked hits with citation, score and visibility.
Fetch a full document, or a single knowledge atom, by docId, citation (sourcePath#atomId) or atomId. Optional maxChars caps the response for your token budget. Restricted documents return -32403 unless the key is authorized.
List the product × type knowledge domains visible to your identity, with document counts. Free of quota — call it first to decide where to search.
The endpoint is stateless: every request carries its own authentication, so it works from serverless agents and multi-instance deployments alike.
Endpoint: POST https://www.qeasy.cloud/api/mcp — JSON-RPC 2.0 over MCP Streamable HTTP (stateless mode). GET/DELETE return 405 and no session is maintained.
Every MCP call requires a key. Agents request /api/v1/agent-registrations/challenge, solve SHA-256 proof-of-work, then register at /api/v1/agent-registrations to receive a Standard key (20 public-knowledge calls/day). No phone, browser session or CRM lead is created. Humans register at /register and also receive a key automatically.
Recommended flow: register agent → initialize → tools/list → knowledge_domains → knowledge_search → knowledge_fetch(citation#atomId).
Claude Desktop / Cursor — mcp.json
{
"mcpServers": {
"qeasy-knowledge": {
"url": "https://www.qeasy.cloud/api/mcp",
"headers": {
"Authorization": "Bearer qk_live_YOUR_KEY"
}
}
}
}Raw JSON-RPC — initialize / tools/list / search / fetch
# 1) request an agent registration challenge
curl -s -X POST https://www.qeasy.cloud/api/v1/agent-registrations/challenge
# => save challengeId and difficulty from data
# 2) solve sha256(challengeId + ':' + nonce) proof-of-work
export CHALLENGE_ID='paste-challenge-id'
export DIFFICULTY='18'
python3 -c 'import hashlib,os
cid=os.environ["CHALLENGE_ID"]; bits=int(os.environ["DIFFICULTY"]); n=0
while True:
h=hashlib.sha256(f"{cid}:{n}".encode()).digest()
if int.from_bytes(h[:4],"big") >> (32-bits) == 0: print(n); break
n+=1'
# => save printed nonce
# 3) register the agent; plaintext key is returned only once
curl -s https://www.qeasy.cloud/api/v1/agent-registrations \
-H 'content-type: application/json' \
-d '{"name":"My Agent","framework":"custom","version":"1.0","challengeId":"paste-challenge-id","nonce":"paste-nonce"}'
# 4) call MCP with the Standard key (20 public-knowledge calls/day)
curl -s https://www.qeasy.cloud/api/mcp \
-H 'content-type: application/json' \
-H 'Authorization: Bearer qk_live_YOUR_KEY' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-agent","version":"1.0"}}}'
curl -s https://www.qeasy.cloud/api/mcp \
-H 'content-type: application/json' \
-H 'Authorization: Bearer qk_live_YOUR_KEY' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"knowledge_search","arguments":{"query":"费用按收入占比分摊什么时候合理","granularity":"atom","includeMeta":true}}}'Tools return retrieval evidence, never generated prose. The calling agent owns the answer and must cite what it used.
Two registration paths and two permission tiers. Registration grants Standard only; restricted access still requires Qeasy authorization.
Daily quota resets at 00:00 Asia/Shanghai. The 21st non-cache call returns HTTP 429 + -32029 with errorKind=daily_quota; minute limits use errorKind=minute_rate_limit. initialize/tools/list/knowledge_domains remain free of daily quota.
Standard defaults to 120 requests/minute and authorized to 600. Every call is authenticated, SQL visibility-filtered and audited without plaintext keys or document bodies.
Open challenge + SHA-256 proof-of-work registration with IP limits, failure audits and database idempotency. No browser session, CRM lead or sales assignment is created.
Humans and agents automatically receive their first key at registration. Create more at /account (max 5 active keys). Each account includes 20 public-knowledge calls/day, shared by all Standard keys.
Unlimited daily calls and the full authorized knowledge base (public + restricted), with configurable product/type scope and expiry. Issued through Qeasy's admin console; contact us to apply.
One endpoint serves two workflows — pick by task (verified blueprint practice from M24 field testing).
The official MCP capability catalog (split criterion: whether the Agent task differs, not the product line). Knowledge retrieval shares this endpoint and is split by product domain; per-product operations MCPs are deployed independently and the website only documents them.
Three categories: K1 platform operations & maintenance, K2 platform APIs & metadata, K3 integration design patterns. Query with product=data-integration plus scenario and category hard filters; citations are sourcePath#section. SOL/CASE/FAIL layers stay restricted.
12 knowledge domains, platform topics and customer cases (general methodology and tax/accounting standards are public). The reconciliation operations MCP is fully privately deployed; the website currently ships only the knowledge base.
39 tools (assets / strategies / scripts / audit) with tenant one-click authorization and sh-xxx keys. Public cloud endpoint: pro-service.qliang.cloud/mcp. Private deployments advertise their own endpoints via self-describing keys.
This endpoint is intentional about scope: it is a retrieval server, not a general-purpose business API. The following capability families are planned, not available today — do not build against them yet.
Start with a free standard key at /account to explore public knowledge, or apply for an authorized key to unlock the full restricted knowledge base and unlimited calls.