Nullshot Plugin

Plan, inspect, and operate Nullshot from your coding agent. The plugin connects to Nullshot's OAuth-protected MCP gateway at https://mcp.nullshot.ai/mcp, loads planning skills derived from Spek Kit, and keeps specifications and task DAGs live in a Nullshot Jam.

Paste the command for your client as one line. Clients with terminal OAuth support open the Nullshot login during the command; the others request OAuth when Nullshot is first used.

Codex's bootstrap registers the MCP server and signs in; its plugin bundle, which carries the skills, is installed from the /plugins browser inside Codex. Codex has no documented terminal command for adding a marketplace, so there is nothing to paste for that half — the two codex plugin commands this table used to list are not commands Codex has.

Cursor and Gemini discover OAuth automatically when the MCP server first returns 401 Unauthorized — true for Cursor only now that its manifest declares a server for one to come from.

Cursor installs from a dashboard rather than a command — it documents no slash or CLI equivalent — but what it installs is now the whole plugin. The Cursor manifest declares the skills, the commands, and an mcpServers entry for the gateway, which is the shape Cursor's own first-party remote-MCP plugins use and which validates against Cursor's published plugin schema. It previously declared skills alone, so a Cursor user who completed the flow got skills that named tools their editor had no server to call — the least obvious way to be broken, because everything looks installed.

That server's URL is fixed at production (see below). On any other environment, use the one-click Cursor button in Nullshot's own Connect panel, which writes that environment's gateway for you. Kimi applies the plugin in a new session; if it reports that authorization is required, run /mcp-config login plugin-nullshot:nullshot. Pi exposes the equivalent interactive action as /mcp-auth nullshot.

The plugin talks to production, https://mcp.nullshot.ai/mcp, unless NULLSHOT_MCP_URL says otherwise:

export NULLSHOT_MCP_URL="https://mcp-gateway-test.devaccounts-1password.workers.dev/mcp"

Set it before the bootstrap command, and keep it set for the sessions that should use that gateway. Nullshot runs separate production, test, preview and local gateways, and each has its own accounts, jams and grants — so an agent pointed at the wrong one reads and writes the wrong environment's data while appearing to work normally. Production stays the default, so an existing install is unaffected by this.

Claude Code reads it through its plugin manifest, where ${VAR:-default} expansion is supported for an HTTP server's url. The OpenCode and Pi adapters resolve it in code.

Codex reads the variable too, but through the shell rather than through Codex: its bootstrap passes the URL as a command-line argument, so ${NULLSHOT_MCP_URL:-...} is expanded before Codex ever sees it. Codex itself does not expand ${VAR} in MCP configuration (openai/codex#2680 and #7521 are open requests for it), which is why plugins/nullshot/.mcp.json stays a plain URL — an unexpanded ${...} written into a config file would register a broken server, which is worse than one that cannot change environment.

Cursor, Kimi and Gemini are production-only. Their manifests are static. Cursor does support manifest variables, but they are values the user is prompted for with no default — an unset one would register a literally unexpanded ${...} as the server URL, which is a broken server rather than a movable one. Nullshot's Connect panel offers Cursor a one-click install carrying the right URL for whichever environment you opened it in, so nothing is lost.

1. Authenticate and select a Jam with set_active_jam_context.
2. Use using-nullshot to load Jam context and relevant remote skills.
3. Shape the product intent with shaping-nullshot-context and creating-nullshot-specs.
4. Write the reviewed task DAG with writing-nullshot-plans; the goal and tasks are replaced atomically using revision checks.
5. Use operating-nullshot for explicit build work. The connected coding agent edits and commits the Jam app directly by default; send_jam_prompt is an optional hosted-delegation path.

Creating a Jam never starts a hosted prompt. A clear request to build, implement, fix, or create an app or feature carries execution authorization through spec and plan, so the coding agent does not ask for a redundant second start message. Planning-only requests still stop before implementation. Direct execution avoids additional Nullshot-hosted agent usage but may use the coding client's own model subscription or API budget.

For example, “create a todo app” creates a prompt-free Jam in planning, synchronizes the specification and task DAG, then has the connected coding agent edit and commit the Jam app. The agent marks each plan task in progress and complete through the MCP so the Spek visualization stays current. It calls send_jam_prompt only if hosted execution is deliberately selected.

The plugin does not ship coding-method skills or a local Spek visualization server. Nullshot Jam is the source of truth for the live specification and plan.

• plugins/nullshot/ is the canonical Codex and Claude plugin bundle.
• Root manifests adapt that bundle for Cursor, Kimi, Gemini, OpenCode, and Pi.
• scripts/validate.mjs verifies manifests, paths, skills, and the canonical MCP URL.

pnpm install
pnpm test
pnpm validate

See NOTICE for Spek Kit, Spec Kit, Superpowers, and Pi MCP adapter attribution.