Supported agents

Per-agent MCP sign-in for Claude Code, Codex, and Cursor, plus every other agent and CI environments.

The steps on this page connect an agent to the hosted Ancher MCP server — what npx -y @ancher-ai/agent-skills install configures. If you used the recommended install, you already signed in once with ancher login and there is nothing further to do per agent.

Sign-in here is browser-based OAuth. You do not need an API token. First sign in to your Claude Code, Codex, or Cursor account as usual, then connect that agent to your Ancher account once.

Claude Code

Start Claude Code in any project:
bash
```
claude
```
In the Claude Code session, run /mcp.
Select ancher, choose its authentication option, and finish the browser sign-in.
Return to Claude Code and ask it to search or save an Ancher note.

If the browser does not open, copy the displayed URL into a browser. Confirm the server is configured with:

bash

claude mcp list

Claude Code’s MCP authentication guide explains the /mcp OAuth flow.

Codex

Run the following after the installer finishes:

bash

codex mcp login ancher

Complete the browser sign-in, restart Codex, and start a new session. Check that the server is available with:

bash

codex mcp list

Cursor

Open Cursor and start an Agent chat. The first Ancher tool use prompts you to connect and complete the browser sign-in. Approve the request, return to Cursor, and retry your request.

If you use the Cursor Agent CLI instead, authenticate the configured MCP server directly:

bash

cursor-agent mcp login ancher
cursor-agent mcp list

Cursor’s MCP documentation covers OAuth connections and MCP configuration.

Every other agent

The hosted MCP server is only configured for the three agents above. Every other agent — OpenCode, Zed, Windsurf, Gemini CLI, GitHub Copilot, and 70 more — uses the recommended install, which reaches Ancher through the CLI:

bash

npx -y skills add streamify-one/ancher-agent-skills
npm install -g @ancher-ai/cli
ancher login

There is no per-agent sign-in step on this path: ancher login covers every agent on the machine at once. The CLI requires Node 24+.

CI and non-interactive environments

Create an API token in Ancher → Settings → API and set it as ANCHER_API_TOKEN. Never place a token directly in a command.

On the recommended install the ancher CLI reads that variable directly, so ancher login is unnecessary and every agent is covered — there is no per-agent configuration step:

bash

export ANCHER_API_TOKEN=...
npm install -g @ancher-ai/cli

Add skills’ own --agent and --yes flags to npx -y skills add … when it needs to run without prompts.

On the MCP install, pass --token instead. The installer then references the environment-variable name in each agent’s configuration. This path covers Claude Code, Codex, and Cursor only:

bash

export ANCHER_API_TOKEN=...
npx -y @ancher-ai/agent-skills install --agent codex --token