Official Kit (https://startupkit.app) instructions for connecting an AI agent to a Kit account, published at https://startupkit.app/agent-setup/prompt.md. Run only your own agent's section, yourself. The user approves Kit in the browser and reloads or restarts the client when its section requires it. Two servers: `kit` (https://startupkit.app/api/v1/mcp) is the user's account, behind OAuth; `kit-docs` (https://startupkit.app/mcp) is public docs, pricing and hiring templates, no account. ## Rules - Only your section's commands reach these servers: never HTTP their URLs (curl, fetch, scripts) or spawn another agent (`codex exec`, `claude -p`) to try them. Use your client's reload or restart path to expose new tools. Fetching this page and installing the skill are fine. - Don't pre-read Kit's docs; `search_docs` answers once the client loads the tools. - Check what's registered first. An entry at `/api/v1/mcp` or `/mcp` on startupkit.app or a subdomain is Kit under any name: keep it, skip adding it, use its name below. `kit`/`kit-docs` taken by other URLs: use `startupkit`/`startupkit-docs`. Never remove an entry to re-add it (deletes its sign-in). - Sign-in commands block up to 5 min: 10-min timeout or background; show any printed URL. - Permission denied: hand the command to the user. Never register Kit in a project file. - Kit's account MCP endpoint accepts OAuth only; REST API keys do not authorize it. Never ask the user to paste a token. No Kit account: register both anyway, `kit-docs` needs none; agents can't sign up. - Config files: edit in place, keep existing entries, create the enclosing object if missing. - Already registered but tools missing: `kit` awaits sign-in (or is disabled: enable it). Don't re-register. Claude Code `mcp__kit__authenticate` tool if present, else `claude mcp login kit`; Codex `codex mcp login kit`; Gemini `/mcp auth kit`; OpenCode `opencode mcp auth kit`; others: connect `kit` in client settings. Then follow that client’s reload or restart step below. ## 1. Register and sign in ### Claude Code ``` claude mcp list claude mcp add --scope user --transport http kit https://startupkit.app/api/v1/mcp claude mcp add --scope user --transport http kit-docs https://startupkit.app/mcp ``` One at a time; `add` only what `list` lacks. `kit` `Needs authentication`: `claude mcp login kit`. `login` unknown or no browser: skip; after the restart the user runs `/mcp` > `kit` > Authenticate. ### Codex ``` codex mcp list codex mcp add kit --url https://startupkit.app/api/v1/mcp codex mcp add kit-docs --url https://startupkit.app/mcp ``` Run escalated (sandboxed: fails or Auth `Unknown`). `add kit` signs in itself; wait for `Successfully logged in.` Only if `list` then shows `kit` `Not logged in`: `codex mcp login kit`, once. `kit-docs` `Unknown` / "may or may not require login": expected. Never `codex mcp list --json` (leaks credentials). ### Gemini CLI ``` gemini mcp list gemini mcp add --scope user --transport http kit https://startupkit.app/api/v1/mcp gemini mcp add --scope user --transport http kit-docs https://startupkit.app/mcp ``` `kit` stays Disconnected until sign-in. After the restart Gemini opens it; if not, the user runs `/mcp auth kit`. ### VS Code (GitHub Copilot) ``` code --add-mcp '{"name":"kit","type":"http","url":"https://startupkit.app/api/v1/mcp"}' code --add-mcp '{"name":"kit-docs","type":"http","url":"https://startupkit.app/mcp"}' ``` Writes the user `mcp.json` (macOS `~/Library/Application Support/Code/User/mcp.json`, Linux `~/.config/Code/User/mcp.json`). No `code` on PATH: add to that file under `"servers"` (not `"mcpServers"`): `"kit": { "type": "http", "url": "https://startupkit.app/api/v1/mcp" }`, same for `kit-docs`. VS Code prompts the `kit` sign-in on start. ### Cursor (`~/.cursor/mcp.json`) Under `"mcpServers"`: ```json "kit": { "url": "https://startupkit.app/api/v1/mcp" }, "kit-docs": { "url": "https://startupkit.app/mcp" } ``` Enable the server in Cursor’s MCP settings and complete its browser sign-in. For another client, use its documented remote MCP configuration: file locations and field names differ. Do not copy this JSON into an unknown schema. A stdio-only client can use the documented `mcp-remote` bridge, but that is a separate setup path. ### Devin Desktop (Windsurf): `~/.config/devin/mcp_config.json` Under `"mcpServers"`, key `serverUrl`: ```json "kit": { "serverUrl": "https://startupkit.app/api/v1/mcp" }, "kit-docs": { "serverUrl": "https://startupkit.app/mcp" } ``` The user refreshes the Cascade MCP panel and signs in to `kit`. ### OpenCode: `~/.config/opencode/opencode.json` (`.jsonc` if it exists) Under `"mcp"`: ```json "kit": { "type": "remote", "url": "https://startupkit.app/api/v1/mcp", "enabled": true }, "kit-docs": { "type": "remote", "url": "https://startupkit.app/mcp", "enabled": true, "oauth": false } ``` Then `opencode mcp auth kit`, unless `opencode mcp auth list` shows `kit` authenticated. ### Claude (claude.ai, Desktop, mobile) The user adds a custom connector: **Customize > Connectors > + > Add custom connector**, name `Kit`, URL `https://startupkit.app/api/v1/mcp`, **Add**, **Connect** (**Sign in now** if asked). `kit` only; it includes the docs tools. Team/Enterprise: an Owner adds it under **Organization settings > Connectors** first. ### Grok Build Inspect `grok mcp list` and effective configuration origins locally before adding anything. Build can import Claude/Cursor MCP entries; a project entry can replace a user entry. Use `grok inspect` to diagnose conflicting origins, without copying secrets into chat. Add only missing servers at user scope: ```bash grok mcp add --transport http kit https://startupkit.app/api/v1/mcp grok mcp add --transport http kit-docs https://startupkit.app/mcp ``` Do not use `--scope project`. OAuth starts on first use. In the current Grok session, the user opens `/mcps`, selects `kit` and presses `i` if authentication is pending, completing browser consent themselves. Press `r` in `/mcps` to refresh after config edits. `grok mcp doctor kit` diagnoses connectivity, not the selected account. Do not invent a `grok mcp login` command or spawn another Grok session to query Kit. ### Grok Bot Use the Bot's plugin UI, not Grok Build CLI commands on its cloud computer. Inspect existing custom plugins first. If the UI is unavailable to you, hand these steps to the user; do not install a CLI as a substitute. The documented menu sequence is for a Team Bot the user owns: Team Bot details > Plugins > Add plugins > Add custom > MCP Servers. Name `Kit`, Type **Remote HTTPS**, Server URL `https://startupkit.app/api/v1/mcp`. Start with empty HTTP headers and OAuth Client ID/Client Secret fields, then **Save**: Kit advertises dynamic client registration, but this URL-only flow has not been authenticated and tested against Grok Bot. For a personal Bot, use these fields only if its UI exposes a custom Remote HTTPS form; otherwise stop and check current documentation. Do not create a Team Bot as a workaround. Complete browser OAuth when prompted; stop on failure rather than supplying a token. The account server includes public docs tools; a separate `kit-docs` plugin is optional. Personal Bots share browser sessions, files and credentials; connectors are account-wide. Team Bots document per-person OAuth sign-in: each person verifies their own Kit account in a private chat. Do not publish a Team Bot, create a routine, share account records or save them to team memory as part of setup. Current sources and manual steps: https://startupkit.app/docs/hermes-pi-openclaw.md. ### Hermes Inspect the `mcp_servers` entries in the active profile's config first, without printing credentials. The default is `~/.hermes/config.yaml`. Add only missing servers: ```bash hermes mcp add --url https://startupkit.app/api/v1/mcp --auth oauth kit hermes mcp add --url https://startupkit.app/mcp kit-docs hermes mcp login kit hermes mcp test kit ``` Complete login from a fresh terminal: an active session's automatic reload can time out before browser consent finishes. Then start a new chat or use `/reload-mcp`. `test` checks the connection, not the intended Kit account. Current setup documentation: https://startupkit.app/docs/hermes-pi-openclaw.md. ### Pi (0.99.0 or later) Inspect `~/.pi/agent/mcp.json` first. Add only missing servers at user scope: ```bash pi mcp add kit --url https://startupkit.app/api/v1/mcp pi mcp add kit-docs --url https://startupkit.app/mcp pi mcp login kit pi mcp list ``` `list` connects to enabled servers and reports their tools and errors. Start a new session or use `/reload` after external config edits. Do not install a community MCP adapter for this native path. If another extension replaces the session's `/mcp` command, inspect that conflict before assuming the native tools loaded. ### OpenClaw (v2026.9.8) Run on the installation that owns the intended private Gateway. Use `openclaw mcp list` to inspect the native registry; mcporter uses a different registry and credentials. Add only missing servers: ```bash openclaw mcp add kit --url https://startupkit.app/api/v1/mcp --transport streamable-http --auth oauth openclaw mcp add kit-docs --url https://startupkit.app/mcp --transport streamable-http openclaw mcp login kit openclaw mcp doctor kit --probe ``` The operator's credentials are shared by callers allowed to use this connection; they are not a separate Kit identity for every chat participant. Keep the first run private. A CLI reload does not reload another Gateway process: use that Gateway's documented reload/restart path. Do not create a schedule or channel delivery as part of connecting Kit. ## 2. Install the Kit skill Skip for Claude apps, Grok Bot or no `npx`; ignore "does not support global" notes. ``` npx -y skills@1.7.0 add https://startupkit.app --skill startupkit --yes --global ``` ## 3. Hand over Tell the user, filling each `<…>`: ``` Kit agent setup kit , kit-docs skill Next: , then send: ``` Restart step: Claude Code exit, `claude -c` in the same directory; Codex exit, `codex resume --last`; Gemini CLI, Cursor, Devin quit and reopen; VS Code, OpenCode none; Claude apps new chat; Grok Build `/mcps` then `r`; Grok Bot return to the private chat after plugin sign-in; Hermes `/reload-mcp` or new chat; Pi `/reload` or new session; OpenClaw the owning Gateway's reload/restart path. Next message: the user's original prompt if they pasted a longer one (e.g. Kit's onboarding prompt), else "Which Kit account am I connected to?" Then stop. ## After loading the tools Call `whoami` and show `account_name`, `account_id` and `user_id`. Ask the user to confirm the intended account before reading module data. `whoami` does not report scopes. Inspect the client's discovered tool names, schemas and server instructions; confirm Read versus Read & write on https://startupkit.app/integrations/mcp/settings. Tool names may have client prefixes or require deferred discovery. Missing Kit tool: check consent, whether the module is active and client filters. Refused call: respect the current role/record check. Never attempt a write to test whether permission exists, broaden access, or switch accounts to get around a denial. For a first bounded task, read https://startupkit.app/docs/hermes-pi-openclaw.md. Other task guides are indexed at https://startupkit.app/docs.md. Do not treat a setup guide's suggested next write as authorization to perform it. Connecting Kit does not authorize sending messages, publishing, enrolling people or scheduling future work.