Connect jpcite to Continue (VSCode / JetBrains) MCP in 5 minutes

Add a single jpcite entry to Continue's config.yaml to unlock 261 MCP tools. VSCode 1.85+ / JetBrains 2024.1+ / Continue 0.9+ required; anonymous free 3 req/IP/day.

Five-minute setup

  1. Install Continue: search for Continue in the VSCode marketplace or JetBrains plugins and install it. Confirm 0.9 or later (v0.8 and below do not support MCP).
  2. Prepare uvx: install with curl -LsSf https://astral.sh/uv/install.sh | sh (skip if you already have it). If uv is not installed, brew install uv also works.
  3. Open config.yaml: click the gear icon at the top right of the Continue sidebar → open ~/.continue/config.yaml. When sharing a workspace, .continue/config.yaml at the repo root also works.
  4. Add jpcite to mcpServers: paste the snippet below and save. Continue reloads the server automatically.
  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

Paste into Continue's ~/.continue/config.yaml (open it from the gear icon).

mcpServers:
  - name: jpcite
    command: uvx
    args: ["autonomath-mcp"]
    env:
      JPCITE_API_KEY: jc_xxxxx

If you have run pip install autonomath-mcp, command: autonomath-mcp also works. If you commit .continue/config.yaml to your repo, switch env to environment-variable expansion (${JPCITE_API_KEY}) to avoid leaking the secret.

Verification

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

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

You are connected when jpcite appears in the MCP section of the Continue pane and shows a tools count of 261. 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

The MCP section is not visible / tools count is 0

Continue v0.8 and below do not support MCP, so update to 0.9 or later. A tools count of 0 is usually an API key authentication failure — check the jc_ prefix on env.JPCITE_API_KEY. On WSL / Remote SSH / JetBrains, we recommend specifying the full path to uvx.

What is the difference between anonymous and paid?

Anonymous is IP-based at 3 req/day (AnonIpLimit) with no API key. Paid is metered at ¥3/billable unit excl. tax with no cap, counted via JPCITE_API_KEY.

How do I issue an API key?

Issue one from /en/pricing.html#api-paid via Stripe Checkout (consent is in custom_text.submit.message). The dashboard shows your jc_... key right afterward (new keys use the jc_ prefix; previously issued sk_ / am_ keys remain compatible).

What is the 8-profession legal fence?

jpcite does not return individualized advice that would intrude on the exclusive practice areas under the Certified Tax Accountant Act §52, the Attorney Act §72, and similar statutes. See /en/legal-fence.html.