AiNecto MCP server

ainecto — AiNecto CLI and MCP connector

Published as ainecto, @ainecto/mcp and @ainecto/cli — the same code. Command: ainecto.

Once per machine: npx -y ainecto@latest setup — signs you in through the browser (once), checks the connection, and connects Claude Code, Cursor, and Codex to the AiNecto server address (https://ainecto.com/mcp). Each agent then signs in to AiNecto by itself the first time it connects.

Every AI session sees the same AiNecto tools. What a tool may change is decided by your AiNecto permissions on the workspace, project, or document it touches — the server refuses the rest. There are no session roles (Design / Development / Test / Validation were removed in 0.8.0).

For AI agents

Run npx -y ainecto@latest setup (use a long command timeout — at least 6 minutes: sign-in waits up to 5 minutes for the user). Then run npx -y ainecto@latest doctor and do what it says.

run /mcp in a session and sign in to ainecto; Cursor — sign in when ainecto asks in its MCP settings; Codex — signs in while setup connects it (a browser tab opens and the sign-in link is printed to stderr; if it did not finish, run codex mcp login ainecto).

• setup registers the server address, so each agent signs in on its own the first time: Claude Code —

does not ask for a role or a project.

• To add AiNecto's working rules to a repository, run npx -y ainecto@latest init from its root. It

npx -y ainecto@latest tools list and npx -y ainecto@latest tools call ''. A new session loads the MCP tools.

• A server added during a session is not available in that session. Keep working through the CLI:

added — start a new session or call it through the CLI as above.

• If a result names a tool that is not in your tool list, the session started before that tool was

to allow the command.

• Claude Code's auto mode may block running an external package with npx. If it does, ask the user

Set up this machine

npx -y ainecto@latest setup              # sign in, check, connect Claude Code · Cursor · Codex
npx -y ainecto@latest setup --dry-run    # show what it would do — no sign-in, no changes
npx -y ainecto@latest setup --local      # connect through the local relay instead (see below)
npx -y ainecto@latest setup --undo       # remove the connections setup made (sign-in stays)
npx -y ainecto@latest status             # who is signed in, your AiNecto role, what is connected
npx -y ainecto@latest doctor             # what is missing, and the one command that fixes each item

setup connects each client separately and reports connected, updated, kept (someone else's ainecto entry, left untouched), not installed, or failed; if any client fails it says «partial» and exits 1:

Sign in with /mcp in a session.

• Claude Code — claude mcp add --transport http -s user ainecto https://ainecto.com/mcp (user scope).

your other servers. Cursor asks you to sign in from its MCP settings.

• Cursor — merges "ainecto": { "url": "https://ainecto.com/mcp" } into ~/.cursor/mcp.json, keeping

(a browser tab opens; setup passes Codex's output, with the sign-in link, through to stderr). If that did not finish within 90 seconds, Codex shows as failed but stays connected — run codex mcp login ainecto (re-running setup says the same).

• Codex — codex mcp add ainecto --url https://ainecto.com/mcp. Codex starts its sign-in right away

With --env dev (or --endpoint) the address is that environment's. The server address has no version to pin: a server update reaches every agent at once. Entries an older setup wrote (npx -y @ainecto/mcp@, with or without --role) are rewritten to the server address when you re-run setup; setup --undo removes either kind.

Shortened. The full README is on GitHub.