Connect your coding agent to Niro
niro mcp install connects your coding agents to Niro. niro start runs it for you at the end of setup. Run it yourself to connect another agent later.
Before you start
npx @niroai/niro@latest start
niro start signs you in through your browser. niro mcp install needs that sign-in.
Install
niro mcp install # pick from a list
niro mcp install --client cursor # one agent
niro mcp install --client codex,cursor # several
niro mcp install --list # see the agents it knows
When it finishes, it prints one line per agent and then "Restart your AI assistant to start using Niro." Restart the agent: it reads its settings only when it starts.
The 14 agents
| Agent | --client |
Page |
|---|---|---|
| Claude Code | claude-code |
Connect Claude Code to Niro |
| Codex | codex |
Connect Codex to Niro |
| Claude Desktop | claude-desktop |
Connect Claude Desktop to Niro |
| Cursor | cursor |
Connect Cursor to Niro |
| Windsurf | windsurf |
Connect Windsurf to Niro |
| VS Code (GitHub Copilot) | vscode |
Connect VS Code (GitHub Copilot) to Niro |
| Gemini CLI | gemini-cli |
Connect Gemini CLI to Niro |
| GitHub Copilot CLI | copilot-cli |
Connect GitHub Copilot CLI to Niro |
| Factory (droid) | factory |
Connect Factory (droid) to Niro |
| Goose | goose |
Connect Goose to Niro |
| OpenCode | opencode |
Connect OpenCode to Niro |
| Cline | cline |
Connect Cline to Niro |
| Kiro | kiro |
Connect Kiro to Niro |
| Antigravity | antigravity |
Connect Antigravity to Niro |
How each agent learns to use Niro
Connecting an agent gives it the tools. Whether it reaches for them first depends on what else the agent is told:
- Claude Code gets hooks: small commands Claude Code runs at fixed moments. They remind it to use Niro and show an impact check before an edit. It also gets two skills and a section in
~/.claude/CLAUDE.md. - Codex and Windsurf get the same two skills, in
~/.agents/skills, plus instruction text. - Cursor, Cline, Kiro, Gemini CLI, Copilot CLI, Factory and OpenCode get instruction text (a rule file) only.
- Claude Desktop, VS Code, Goose and Antigravity get the connection only.
All Niro tools only read
Every Niro tool reads the graph or your files, and none changes your code. One tool, mark_task_complete, records the summary your agent writes at the end of a task. That summary is sent to Niro with the tool-usage record (see What leaves your machine).
Because the tools only read, some installers let them run without asking you each time:
- Cursor:
niro:*is added to Cursor's allowlist. - Kiro:
autoApprove: ["*"]is set. - Codex:
default_tools_approval_mode = "writes"is set, so Codex asks only for tools that write.
Other MCP clients
If your agent is not in the list, choose "Other (print the config)" in the picker. It prints a block like this to paste into your agent's MCP settings:
{ "mcpServers": { "niro": { "command": "niro", "args": ["mcp", "serve"] } } }
The printed block also carries the settings your setup needs. Use the printed block, not this example.
Remove Niro from an agent
niro mcp uninstall --client cursor
niro mcp uninstall --all
This removes everything the install added: the connection, the hooks, the instruction text, the skills, and the Cursor allowlist entry. It removes the Cursor rule only in the current folder. Your sign-in stays.