← Back to home Docs

Supported agents

spawnpoint connects to your coding agent over MCP. Every agent below starts with the same installer; the only thing that differs is the one-time sign-in step. Protocol detail (endpoint, transport, auth, tools) lives on the MCP server page.

Start here, whichever agent you use. One command detects every coding agent on your machine and writes the right config for each. Do not hand-edit an MCP config file: the installer knows the right path, the right format, and the right endpoint, and it is the only path we test.
curl -fsSL https://getspawnpoint.com/install | bash

Limit it to one agent with SPAWNPOINT_AGENT=claude|codex|cursor|opencode|copilot|vscode|jcode. Then sign in once, in the browser, for the agent you use. Find yours below.

Claude Code (terminal)

  1. Run the installer. It also adds the spawnpoint plugin, so "deploy this" works as a skill.
  2. Restart Claude Code.
  3. Run /mcp, choose spawnpoint, choose Authenticate, and approve in the browser.

Claude desktop app

The Claude desktop app ships its own Claude Code runtime that reads the same config as the CLI, so the installer wires it too — even on a machine that has only the app and no claude command. Run the installer, then open the app's Code tab, run /mcp, choose spawnpoint, and Authenticate.

No terminal? Add it as a custom connector

If you never open a terminal, skip the installer and add spawnpoint by hand — it takes three clicks and works on every plan (Free allows one custom connector):

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it spawnpoint and paste the URL https://app.getspawnpoint.com/mcp.
  3. Click Add, then Connect and approve the sign-in in your browser.

This route adds spawnpoint to Claude chat and Cowork; the Code tab reads the same connection. You do not get the deploy skill this way (that rides the plugin the installer adds), but every spawnpoint tool works, and "deploy this" still gets you a link.

Codex CLI

  1. Run the installer. It runs codex mcp add for you.
  2. Run codex mcp login spawnpoint and approve in the browser.

Cursor

  1. Run the installer. It writes the spawnpoint entry into ~/.cursor/mcp.json for you.
  2. Run cursor-agent mcp login spawnpoint, or open Cursor's MCP settings and approve spawnpoint.

opencode

  1. Run the installer.
  2. Run opencode mcp auth spawnpoint.

GitHub Copilot CLI

  1. Run the installer.
  2. Run copilot, use any spawnpoint tool, and approve the browser sign-in when it prompts.

VS Code Copilot

  1. Run the installer.
  2. Open Copilot Chat in agent mode, start the spawnpoint server, and sign in from the browser prompt.

jcode

  1. Run the installer. It writes the spawnpoint entry into ~/.jcode/mcp.json.
  2. Use any spawnpoint tool; mcp-remote opens the browser sign-in on first use.

jcode speaks stdio-only MCP today, so the installer bridges it to the hosted endpoint through the mcp-remote npm package, which needs Node (npx) on your PATH. On a headless machine, create an API token and add "--header" and "Authorization: Bearer spk_live_your_token" to the entry's args instead.

Any other MCP client

The installer does not know your client, so this is the one case where you configure it yourself. Point it at https://app.getspawnpoint.com/mcp over Streamable HTTP and complete the OAuth flow it discovers from .well-known. The MCP server page has the exact config shape and the per-agent commands for wiring a supported agent by hand.

No browser available (CI, cloud agents)

Clients that cannot do OAuth send a token instead: create a spk_live_… API token in the console and send it as Authorization: Bearer spk_live_…. Both credential types are accepted on the same endpoint, and every call is scoped to the account that authorized it.

Then say "deploy this." Whatever the agent, the rest is the same: one tool call, one link back. The getting started page walks the whole path.