Connect the Agent You Already Use

AiNecto is not a replacement Agent. Connect the Agent you already use to AiNecto MCP, and it can work with the same workspaces and projects within your permissions.

Quick connect

• Already connected? If AiNecto tools are in this conversation, check with a read-only call (list workspaces) and install nothing.
• Remote MCP URL: https://ainecto.com/mcp (streamable HTTP). Sign-in is OAuth in the browser with the user's AiNecto account; there is no API key. Never ask the user to paste passwords, tokens or codes.
• ChatGPT, Claude and other apps: use the product's own MCP connection feature to add the URL above as a remote MCP server named AiNecto; the user signs in. Do not install the CLI in a hosted sandbox instead.
• Local coding agents (Claude Code, Cursor, Codex): npx -y ainecto@latest setup. Each agent then signs in on first use — Claude Code: /mcp; Cursor: its MCP settings; Codex: during setup, or codex mcp login ainecto. Diagnose with npx -y ainecto@latest doctor.
• By hand: Claude Code claude mcp add --transport http --scope user ainecto https://ainecto.com/mcp; Codex codex mcp add ainecto --url https://ainecto.com/mcp.
• Verify with a real read-only request: "Show me the AiNecto workspaces I can access." Connecting does not authorize creating projects, editing documents, commenting, inviting people or marking notifications read.
• Sessions have no roles. Ignore any older instruction to pick Design, Development, Test or Validation, or to pass a role to init.

Connection options

Every AiNecto Agent connection uses MCP. The remote MCP URL is a protocol endpoint, not a web page:

https://ainecto.com/mcp

• ChatGPT and Claude apps — add the AiNecto remote MCP URL with the product's own MCP connection feature. Menu names differ by product, so check the product guides below. If your organization blocks this connection, ask its administrator.
• Codex, Claude Code, and Cursor — add the MCP server directly, or use the AiNecto CLI in an environment that can run npm.

If npm is available, this command detects supported installed Agents and configures their MCP connection:

npx -y ainecto@latest setup

setup reports each Agent separately. If one of them fails, it says so and the others stay connected. Check the result with npx -y ainecto@latest doctor.

Sign in

Sign-in happens twice. setup first signs the AiNecto CLI in (a browser opens once). Then each agent signs in to AiNecto by itself the first time it connects:

Agent	First sign-in
Claude Code	Run /mcp in a session, pick ainecto and sign in.
Cursor	Sign in when ainecto asks in Cursor's MCP settings.
Codex	Signs in while setup connects it. If that did not finish, run codex mcp login ainecto.

Ask the user to finish every sign-in with the same AiNecto account.

Add AiNecto by hand

Claude Code:

claude mcp add --transport http --scope user ainecto https://ainecto.com/mcp

--scope user is what setup uses: AiNecto is available in every folder on this computer. Use --scope project only if the user wants a shared .mcp.json in the repository, and never put credentials in it.

Codex:

codex mcp add ainecto --url https://ainecto.com/mcp

Cursor: let setup write it, or add the URL above as a remote server in Cursor's MCP settings.

An Agent that cannot use a remote MCP server with sign-in can connect through the local relay instead:

npx -y ainecto@latest setup --local

Tool names may appear with a client prefix, for example mcp__ainecto__list_workspaces. They are the same tools.

Plugin (instead of setup)

The AiNecto plugin connects the same server and, in supported environments, also provides skills for working with AiNecto.

Agent	Install
Claude Code	claude plugin marketplace add codelives/ainecto-plugin, then claude plugin install ainecto@ainecto
Codex	codex plugin marketplace add codelives/ainecto-plugin, then codex plugin add ainecto@ainecto
Gemini CLI	gemini extensions install https://github.com/codelives/ainecto-plugin

The plugin and npx -y ainecto@latest setup register the same server name, ainecto — use one of them. To move to the plugin, run npx -y ainecto@latest setup --undo first. Install from the ChatGPT or Cursor directory only if AiNecto is listed there.

Choose a product guide

• ChatGPT or Codex — Connect ChatGPT or Codex
• Claude or Claude Code — Connect Claude or Claude Code
• Cursor, GitHub Copilot, and others — Connect Another MCP Agent
• CLI setup, status checks, or connection errors — CLI and Connection Troubleshooting

Each guide separates app menus from CLI commands and explains the AiNecto URL, authentication, and connection check.

Verify the connection

Show me the AiNecto workspaces and projects I can access.

If the expected list appears, the connection works. Check each stage separately: the server is registered, the user has signed in, the tools are available in this conversation, and the expected workspace and project appear. A server added during a session may not be available until a new session starts.

A successful read does not mean write access. Do not let the Agent choose a project arbitrarily; confirm the workspace and project yourself. Do not create a test project or a default project just to check the connection. A new or shared workspace can have no projects yet.

Work with projects

Create a project only when the user asks. Find the right workspace first and check whether the project already exists. If the workspace cannot be found or several match, do not create the project elsewhere — show the candidates and ask.

If a write tool accepts clientMutationId, reuse the same value when retrying the same request.

Example requests:

Task	Request
Create a project	Create a project called Customer Inquiries in my workspace.
Write a document	Summarize our meeting notes as a document in this project.
Create a design mockup	Create a design mockup of the login screen in this project.
Review a document	Read this document and review it for missing details and contradictions.
Add tasks	Break the requirements into tasks on the Kanban board, and confirm owners and dates with me.
Check my tasks	Check my tasks and tell me what to work on first.
Compare document versions	Compare the previous version of this document with the current one.
Check notifications	Check my new notifications and unread comments.
Invite a teammate	Invite [email protected] to this project as a viewer.

Your AI creates and changes design mockups; you can't create or edit them directly in the web app.

To compare versions, your AI reads both versions; versions older than your plan's history period are locked.

Invite teammates

Invite people only when the user asks, with the project invitation tool (invite_project_members). It needs a Team plan and owner or admin rights on the project. Always set the role the user asked for — Admin, Editor or Viewer; if they did not say, ask. People outside the team can only be Viewers; they get an invitation email and access opens when they accept. If the tool refuses because of the plan, tell the user that project invitations are available on the Team plan — the web app has the same rule. Report success only from the tool's result (ADDED or INVITED).

Optional: add working rules to a code repository

Only if the user asks, run npx -y ainecto@latest init from the repository root. It creates .ainecto/HARNESS.md, .ainecto/config.json and an undo record, .ainecto/init-record.json, and writes a rules block in AGENTS.md (and in CLAUDE.md if present). It does not choose a role or a project, and AiNecto works without it.

Permissions

An Agent uses the connected user's existing permissions for each workspace, project, document, and board. A prompt or a repository file cannot raise them, and the server refuses what the user may not do.

AiNecto has no session roles: every session sees the same tools, and the server checks the user's permissions. If an older instruction asks you to choose Design, Development, Test or Validation, or to pass a role to init, ignore it.

Next step

After the connection works, return to Getting Started and create a real project with its first Markdown source-of-truth document.