Public APIs & MCP server | Chinaready

Chinaready

3 min read Original article ↗

Developer docs

Wire Chinaready’s China go-to-market knowledge into your AI tools, or POST straight to our public form and search endpoints. No API keys, no sign-in.

Chinaready MCP server

The research library behind this site — insights and handbooks on China market entry — exposed as a read-only MCP server. Connect it to any MCP-capable client and every answer cites a full chinaready.co URL. Runs on our own open-source Cloudflare Worker.

Endpoint

https://mcp.chinaready.co/mcp

  • No sign-in — no keys, no OAuth
  • Read-only: 3 tools
  • Rate limited, ~120 requests/minute
  • MIT, open source

Listed on Glama — Chinaready MCP connector rated A, ownership verified Chinaready MCP — featured on Product Hunt

Connect your client

One-click where the client supports it; everywhere else it is a URL paste.

  • The button opens Cursor with the server pre-configured — nothing to type.

    Prefer manual? Add the same server to ~/.cursor/mcp.json — see the generic config under “Any other MCP client”.

  • Opens the VS Code MCP install prompt (stable and Insiders). The server then appears in Copilot Chat’s tool list.

  • Claude

    1. Settings → Customize → Connectors → + Add
    2. Choose Add custom connector
    3. Paste https://mcp.chinaready.co/mcp
    4. Authentication: choose No sign in, then Add

    Works on web and desktop. Free plans hold one custom connector — use it wisely.

  • Claude Code

    One command, per project or global:

    claude mcp add --transport http chinaready https://mcp.chinaready.co/mcp

  • ChatGPT

    1. Open chatgpt.com/plugins → +
    2. Choose Add custom MCP server
    3. Paste https://mcp.chinaready.co/mcp → Create as a plugin

  • Any other MCP client

    Windsurf, Zed, LibreChat, opencode… Remote server — no command, no keys. Windsurf calls the same field serverUrl. 

    {"mcpServers":{"chinaready":{"url":"https://mcp.chinaready.co/mcp"}}}

REST APIs

Form submissions and search over plain HTTP. The OpenAPI description (/openapi.json) is the machine-readable source of truth for all of them.

  • POST /api/contact

    Send a contact-form submission. Returns 201 with a received confirmation; Chinaready responds within 24 hours. Prefer the human form? /contact/.

    • name
    • email
    • message
    • company
    • timezone
    {"name":"Ada Lovelace","email":"[email protected]","message":"We are evaluating ICP filing options."}

    JSON body OpenAPI spec Human form

  • POST /api/intake

    Submit a market-readiness intake. Returns 201 with auto-scored fields. Human form: /intake/.

    • email
    • top-level or basics.email

    JSON body OpenAPI spec Human form

  • POST https://search.chinaready.co/search Cloudflare AI Search

    AI retrieval over the same corpus the Ask AI panel uses — no authentication. Retrieval only: bring your own model. Each returned excerpt begins with a url / title / type source header whose url is the absolute chinaready.co page link — cite that URL in answers. 

    {"messages":[{"role":"user","content":"How long does ICP filing take?"}]}

    ~120 requests/minute POST only OpenAPI spec

  • POST /api/search

    Site-search proxy over the same corpus: returns article-level results (title, snippet, relevance score), ranked by best match — no generation. Powers /search/ and the insights catalog’s AI matches. 

    {"query":"icp filing timeline"}

    ~30 searches / 10 minutes, per IP OpenAPI spec Try it in the UI