Connect Another MCP Agent

Every AiNecto Agent connection uses MCP. An Agent that supports a remote HTTP MCP server and browser authentication can connect with these values:

• Name: AiNecto
• Transport: HTTP or Streamable HTTP
• Server URL: https://ainecto.com/mcp
• Authentication: follow the browser sign-in presented by the server

If npm is available

On a device with Codex, Claude Code, or Cursor installed, AiNecto CLI detects supported Agents and configures their MCP connection.

npx -y ainecto@latest setup

This is the default route when you do not want to edit each app's configuration manually. Review the success, not-installed, and failed result for every detected Agent.

Configure Cursor directly

If you are not using AiNecto CLI, add this server to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "ainecto": {
      "url": "https://ainecto.com/mcp"
    }
  }
}

Restart Cursor, confirm that AiNecto is active in its MCP connection screen, and complete browser authentication.

VS Code with GitHub Copilot Agent mode

Add this server to .vscode/mcp.json at the project root:

{
  "servers": {
    "ainecto": {
      "type": "http",
      "url": "https://ainecto.com/mcp"
    }
  }
}

Switch Copilot Chat to Agent mode and enable AiNecto in the tools picker.

Other Agents

Find the product's remote MCP server settings and enter the common values above. If the product has no such settings or supports only local processes, it cannot connect directly through this method.

MCP capabilities and setup locations for products such as Gemini or Windsurf vary by product and version. Check the product's current MCP guidance for remote HTTP, browser authentication, and write-tool support.

Verify the connection

Show me the AiNecto workspaces and projects I can access.

If the expected list appears, the connection works. If it differs, check the connected account and sharing permissions. For errors, go to CLI and Connection Troubleshooting.