Skip to main content
Jinko exposes a remote MCP endpoint with OAuth support. Most modern MCP clients only need the endpoint URL.

​
Endpoint

https://mcp.builders.gojinko.com/mcp

​
Sandbox

Test the full flow against the sandbox environment (isolated data) before going to production: 
https://mcp.builders.sandbox.gojinko.com/mcp
Sandbox uses separate API keys / OAuth from production — generate a sandbox key from the dashboard. A production token will not authenticate against sandbox (and vice-versa).

​
Claude Code

claude mcp add --transport http jinko https://mcp.builders.gojinko.com/mcp

​
Cursor

{
  "mcpServers": {
    "jinko": {
      "url": "https://mcp.builders.gojinko.com/mcp"
    }
  }
}

​
API key mode

When your client does not support OAuth, attach an Authorization: Bearer jnk_* header instead.