CLI and Connection Troubleshooting

Every Agent connection to AiNecto uses MCP. You can add the remote MCP URL directly in an app or use AiNecto CLI on a device that can run npm to configure Codex, Claude Code, and Cursor together.

Use AiNecto CLI

Configure the connection:

npx -y ainecto@latest setup

Setup checks AiNecto sign-in and the MCP connection, then registers AiNecto in installed Codex, Claude Code, and Cursor environments. If one Agent fails, it reports that result separately from successful Agents.

Check the current state:

npx -y ainecto@latest status

Diagnose connection problems and obsolete settings:

npx -y ainecto@latest doctor

If the CLI is unavailable—or when connecting from the ChatGPT or Claude app—add the remote MCP URL directly using the product guide.

Common connection checks

Check the URL, authentication, permission, and Agent tool state in that order.

1. Verify the connection values

• Name: AiNecto
• Server URL: https://ainecto.com/mcp
• Remote transport: HTTP or Streamable HTTP
• Authentication: AiNecto browser sign-in

If you have an old URL, a duplicate server, or another server with the same name, keep only the intended current connection and retry.

2. Check the server in the Agent

• ChatGPT — confirm that AiNecto is installed and enabled in Plugins
• Codex — run codex mcp list
• Claude — enable AiNecto in the conversation's Connectors
• Claude Code — run claude mcp list or open /mcp
• Other Agent — confirm that AiNecto is enabled in its MCP tools or connection screen

3. Check authentication

When browser authentication opens, sign in with the AiNecto account used for the real work. If you closed the window or the session expired, reconnect from the Agent's MCP management screen.

Never paste tokens, passwords, or private keys into prompts, documents, or comments.

4. Check permissions

Show me the AiNecto workspaces and projects I can access.

If no list appears, the problem is likely connection or authentication. If the list appears but a project is missing, check sharing and permissions for that account in the AiNecto web app.

An Agent uses the connected user's existing permissions. A prompt cannot elevate them. If an invitation is refused, check the plan and project role — see Connect the Agent You Already Use.

5. Test reading and writing separately

Start by reading a source-of-truth document.

Find and read the Project Context Markdown document in [project name].

If reading works but creating or editing does not, check the Agent's workspace policy, security settings, and tool approval settings for write restrictions.

Identify the error category

• Server missing — setup location, URL, or MCP support
• Sign-in does not open — authentication discovery or popup blocking
• Wrong projects appear — authenticated with another AiNecto account
• Permission denied — insufficient project, folder, or document permission
• Read-only behavior — workspace policy, security setting, or tool approval
• Connection failure — Agent version, network, or temporary service issue

A support request should include the Agent name and version, operating system, failed step, error message, and whether workspace and project listing works. Exclude secrets.