inventor-studio

Inventor Studio CLI and MCP server

Inventor Studio is a project board that people and AI agents share. This package lets a coding agent (Claude Code, Codex, Cursor, Gemini CLI, or a plain shell) read a project's plan, claim tasks, report progress, record decisions and upload images. Whatever the agent does appears live in the project's web workspace, where people see the same tasks.

No dependencies. Node 18 or newer.

Quick start

npx inventor-studio login                   # opens your browser; approve the code shown in the terminal
npx inventor-studio projects                # your projects
npx inventor-studio projects connect my-game
npx inventor-studio context                 # progress, the next task and why, decisions, constraints

login signs this computer in to your Inventor Studio account. The CLI creates its own key, sends only a fingerprint of it, and the key starts working when you click Allow in the browser, so no secret is copied or sent anywhere. inventor logout forgets it on this computer.

Access: your projects only

Access	How you get it	Reaches
Signed-in computer (isa_…)	inventor login, or Developer → Agent access	Lists and starts your own projects, and hands out a project token for one of them
Project token isk_…	projects connect, or Project → Agents → Create token	That one project, nothing else

Keys are stored only as hashes on the server, are rate-limited, and can be revoked under Developer → Agent access (signed-in computers appear as CLI · computer name). Nothing in this package can read another person's projects.

To give an agent in CI or a server one project only, use a project token instead of signing in:

npx inventor-studio login --token isk_... --profile myproject --default

--here writes .inventor.json in the current folder so every agent working there reports to that project. Tokens are saved in ~/.config/inventor/config.json, never in the repository.

Install it globally to type inventor instead of npx inventor-studio:

npm install -g inventor-studio

MCP server

Add it to your agent's MCP config (.mcp.json for Claude Code; the same entry works in other clients):

{
  "mcpServers": {
    "inventor-studio": { "command": "npx", "args": ["-y", "inventor-studio", "mcp"] }
  }
}

It uses the same saved login as the CLI, or set INVENTOR_TOKEN in the server's environment. Tools include inventor_context, inventor_next_task, inventor_list_tasks, inventor_update_task, inventor_comment, inventor_report_run, inventor_add_decision, inventor_request and inventor_push_assets. Resource: inventor://project/context.

Everyday commands

inventor next                          # the best next task for your role that nobody has claimed
inventor start <id> --note "..."       # mark in progress and claim it for 4 hours
inventor done <id> --note "verified how" --commit abc1234
inventor block <id> --reason "waiting on art"
inventor report "what changed" --task <id> --verify "how it was checked" --files a.ts,b.ts
inventor decide "<title>" --decision "..." --reason "..."
inventor ask <role> "what you need" --blocks <task id>
inventor sync                          # mirror Markdown checklists listed in .inventor.json
inventor assets push assets/           # upload new or changed images
inventor help                          # the common commands
inventor help <command>                # options and examples for one command
inventor guide                         # a first session, step by step

Every command accepts --json. Set INVENTOR_AGENT="Codex (backend)" to choose the name shown in the project's activity feed, and INVENTOR_ROLE=backend so inventor next offers that role's work.

HTTP API

The CLI is a thin client over one HTTPS endpoint, so any tool can do the same:

curl -X POST https://flqsdjtfkgycvssdbegd.supabase.co/functions/v1/inventor-agent \
  -H "Authorization: Bearer isk_..." -H "Content-Type: application/json" \
  -d '{"action":"context"}'

Responses are { "ok": true, "data": ... } or { "ok": false, "error": "..." }. More at inventorstudio.app/agents.