Connect jpcite to Cursor MCP in 30 seconds

Five-minute setup

1. Confirm Cursor 0.42 or later: Cursor → Settings → About. Versions 0.41 and below do not support MCP, so update first.
2. Prepare uvx: install with curl -LsSf https://astral.sh/uv/install.sh | sh (skip if you already have it).
3. Place .cursor/mcp.json in the project root: mkdir -p .cursor && curl -o .cursor/mcp.json https://jpcite.com/.cursor/mcp.example.json
4. Restart Cursor: open Settings → MCP and check that jpcite shows a green dot.
5. (Optional) Embed an API key: replace env.JPCITE_API_KEY with your jc_... key (new keys use the jc_ prefix; previously issued sk_ / am_ keys remain compatible). Omit it to stay on the anonymous free tier.

Copy-paste snippet

Create .cursor/mcp.json in the project root.

{
  "mcpServers": {
    "jpcite": {
      "command": "uvx",
      "args": ["autonomath-mcp"],
      "env": {
        "JPCITE_API_KEY": "jc_xxxxx"
      }
    }
  }
}

To configure it globally, place the same content in ~/.cursor/mcp.json.

Verification

Type the following in Cursor chat. Success means jpcite is called and the result comes back with a source_url.

@jpcite search_programs q="ものづくり補助金" prefecture="東京都"

You are connected when Settings → MCP → jpcite shows a tools count of 261 on the right. Generation of 36-Agreement labor documents is not offered publicly.

When smoke-testing the REST endpoint directly, always use -G --data-urlencode. Embedding a Japanese query straight into the URL breaks the HTTP request line, and the API returns {"error":{"code":"bad_request",...,"hint":"Use --data-urlencode for non-ASCII query params..."}}.

curl -G "https://api.jpcite.com/v1/programs/search" \
  --data-urlencode "q=ものづくり補助金" \
  --data-urlencode "prefecture=東京都" \
  -H "X-API-Key: ${JPCITE_API_KEY:-}"

FAQ