# Connect Inari Inari keeps the memory and plan of the user's projects: over MCP you keep each project's brief, decisions, plan, board and documents, and the user sees the work at https://inari.build and answers your questions and needs. MCP address: https://inari.build/mcp — Streamable HTTP, OAuth sign-in in the browser. No token or key needed. ## Agent with a terminal — Inari CLI (the main path) Claude Code (in the terminal and in the Code tab of the Claude app), Codex, Cursor, VS Code: no connector and no `mcp add` needed, Inari installs with one command and works in this same session (https://inari.build/skill.md?lang=en). macOS and Linux (WSL included); on Windows without WSL and in a sandbox without network, use your client's section below. 1. `curl -fsSL https://inari.build/install.sh | sh` — one file `~/.inari/bin/inari`, its SHA-256 is checked against `https://inari.build/cli/SHA256SUMS`; what else the CLI installs and how to check the sum by hand — in https://inari.build/skill.md?lang=en. 2. `~/.inari/bin/inari setup` — a link and a sign-in code in the output, the browser opens by itself: the user signs in and presses “Allow”. The command waits up to 100 seconds; if it prints “Вход ещё не подтверждён” (sign-in not confirmed yet), run it again right away, the sign-in continues. 3. In this session Inari tools go through `~/.inari/bin/inari call ''` (the list — `~/.inari/bin/inari tools`); in the next sessions — the MCP server `inari`. ## Without the CLI: general - The client starts the sign-in, not you. Don't open Inari pages or sign-in links yourself — neither in a browser nor in a built-in preview: the client opens the system browser itself, where the user signs in and presses “Allow”. - You may run the add command yourself if you have the user's terminal. The user does the sign-in — tell them what to press. - A server added during a session shows up only in a new session. After the sign-in, ask the user to restart the client. - Find your client's section and give the user only its steps. If Inari is already in the client, don't add it again. ## Claude Code without the CLI If you already have Inari tools (whoami) — from a connector or the inari server — add nothing. 1. Run: `claude mcp add --scope user --transport http inari https://inari.build/mcp`. `--scope user` makes Inari available in every project, not only in this folder. 2. Ask the user to quit Claude Code and run `claude mcp login inari` in the terminal (a browser opens: sign in and “Allow”), then come back with `claude --continue` and type “Start with Inari”. Another way to sign in — in a new session `/mcp` → inari → Authenticate. 3. If the browser didn't bring the user back to Claude Code, have them paste the address from the address bar into Claude Code. No browser (SSH) — `claude mcp login inari --no-browser`. ## Claude without a terminal: claude.ai, the Claude app chat, mobile Only the user adds a connector. Give them the link: https://claude.ai/customize/connectors/yours?modal=add-custom-connector&connectorName=Inari&connectorUrl=https%3A%2F%2Finari.build%2Fmcp&open_in_browser=1 There: “Continue” (if asked about signing in — “Sign in now” and “Register automatically”), “Add”, then “Connect” at Inari. Without the link: Customize → Connectors → “+” → “Add custom connector”, address https://inari.build/mcp. One connector works in claude.ai, the Claude app and on mobile. The free plan allows one custom connector; in Team and Enterprise the organization owner adds the connector: https://claude.ai/admin-settings/connectors?modal=add-custom-connector&connectorName=Inari&connectorUrl=https%3A%2F%2Finari.build%2Fmcp&open_in_browser=1 In a chat Inari is turned on through “+” → Connectors. In the Claude app the link is opened with Cmd- or Ctrl-click, in a regular browser: the built-in panel has no user sign-ins. ## Codex: CLI, the ChatGPT app, IDE extension Ask the user to run in their terminal: `codex mcp add inari --url https://inari.build/mcp`. The command adds Inari at once for the CLI, the app and the extension (shared `~/.codex/config.toml`) and opens the browser to sign in. Don't run it yourself: it waits for the user to sign in. After that a new codex session is needed, and Restart in the app and the extension. Sign in again: `codex mcp login inari` (or `/mcp login inari` in a session). No browser (SSH) — `codex mcp login inari --no-browser`. Codex in WSL reads the config from the WSL home folder, not the Windows one. Without a terminal, in the Codex section of the ChatGPT app: Settings → MCP servers (in newer versions — Settings → Plugins → MCPs) → Add server: Streamable HTTP, name inari, address https://inari.build/mcp → Save → Restart → “Authenticate” at inari. In the IDE extension — the gear → MCP servers or `config.toml`: `[mcp_servers.inari]` and `url = "https://inari.build/mcp"`, then Restart extension and “Authenticate”. ## Cursor Give the link: https://cursor.com/en/install-mcp?name=inari&config=eyJ1cmwiOiJodHRwczovL2luYXJpLmJ1aWxkL21jcCJ9. If you have a terminal, you can instead add the server `"inari": {"url": "https://inari.build/mcp"}` to `mcpServers` in `~/.cursor/mcp.json`, leaving the other servers as they are. Sign in: Cursor settings → MCP → inari → “Connect”; in Cursor CLI — `agent mcp login inari`. ## VS Code Run: `code --add-mcp '{"name":"inari","type":"http","url":"https://inari.build/mcp"}'`. Sign in: on the server's first start VS Code asks to “Authenticate”. Without a terminal: Command Palette → “MCP: Add Server” → HTTP → address https://inari.build/mcp → name inari → Global. ## Gemini CLI Run: `gemini mcp add --scope user --transport http inari https://inari.build/mcp`. Sign in: the user restarts gemini and types `/mcp auth inari`. ## ChatGPT Only the user does it, on the web: Plugins → “+” → “Add custom MCP server”, address https://inari.build/mcp, Authentication — OAuth → “Create as a plugin”, then sign in. Writing to Inari works on Business, Enterprise and Edu; on other plans it is read-only or custom servers are unavailable; a workspace admin may block them. ## Another client Have the user add a remote MCP server (Streamable HTTP) with the address https://inari.build/mcp. The client opens the sign-in itself. If it asks for a token or a key, it can't do OAuth for MCP and won't work with Inari. JetBrains AI Assistant can't do OAuth for MCP yet — suggest Codex or Claude Code in the IDE terminal. - Zed: Settings → AI → MCP Servers → Add Remote Server or in settings.json `"context_servers": { "inari": { "url": "https://inari.build/mcp" } }`. - Cline: MCP Servers → Remote Servers, name inari, type Streamable HTTP → Add Server. - goose: Extensions → Add → Remote Extension (Streamable HTTP). - Devin Desktop (formerly Windsurf), Warp, Raycast: a remote MCP server in their MCP settings; exact menu items not verified. ## After sign-in In a new session call `whoami` of the inari server. If `nextStep` is not null, follow it: 1. Find out which project this is about: if you're working in a folder with code, look at it yourself; if not, ask. 2. Offer to create a project: a name is required, a summary only if you know it for sure. One option — offer it and ask to confirm; several — let the user choose; declining is fine too. Ask with your own client (its question tool with options, if it has one). 3. Once the user agrees — product_create; if you're in a folder with git, pass repository so the folder gets linked. 4. Tell the user in one message: “Inari is connected: you're signed in as . Project “” added — ”. Write to the user in the user's language: convey the messages from these steps by meaning, not word for word; name buttons and commands as they are.