MCP integration guide

Point any agent at one endpoint.

Automated Operations exposes a single Model Context Protocol server. Every MCP-compatible client — and a few that aren't yet — connects to it the same way. Pick your client below.

One-command setup

bash

npx @ao-mcp/setup

Detects which clients you have installed (all pre-selected — deselect any you don’t want), writes each config with a backup, and verifies the connection. Works on macOS, Linux, and Windows; needs Node 20+. Prefer to edit configs yourself? Every client below has the manual snippet.

Endpoint

https://mcp.automatedoperations.com

Same URL for every client. Streamable HTTP transport. SSE supported for clients that require it.

Auth

Sign in with your AO account

The first time you connect a client, a browser opens to sign in to AO. After that, your client signs in for you. Nothing to copy into config files, nothing to share — teammates each use their own AO account.

Quick connectivity test

bash

curl -i https://mcp.automatedoperations.com/.well-known/oauth-protected-resource

A 200 means the endpoint is reachable from your network. Run it anywhere to check connectivity — no sign-in needed.

Claude Code

Anthropic's terminal-native coding agent.

bash

claude mcp add --transport http AutomatedOperations https://mcp.automatedoperations.com

Run /mcp inside Claude Code to sign in on first use. After that, your client signs in for you.

json · .mcp.json

{
  "mcpServers": {
    "AutomatedOperations": {
      "url": "https://mcp.automatedoperations.com"
    }
  }
}

Safe to commit — there are no secrets in the file. Each teammate signs in with their own AO account on first use.

Claude Desktop

Anthropic desktop app for Mac and Windows.

bash

https://mcp.automatedoperations.com

Settings → Connectors → Add custom connector → paste the URL. Available on all plans; no config file needed.

json · ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "AutomatedOperations": {
      "command": "npx",
      "args": ["-y", "mcp-remote@^0.1.38", "https://mcp.automatedoperations.com/"]
    }
  }
}

The config file takes stdio servers only, so the remote endpoint is wrapped in mcp-remote (needs Node 18+ on your PATH). Fully restart Claude Desktop afterwards.

json · %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "AutomatedOperations": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "mcp-remote@^0.1.38", "https://mcp.automatedoperations.com/"]
    }
  }
}

Windows spawns commands without a shell and npx is a .cmd shim there — hence the cmd /c wrapper.

Cursor

AI-first IDE.

json · ~/.cursor/mcp.json

{
  "mcpServers": {
    "AutomatedOperations": {
      "url": "https://mcp.automatedoperations.com"
    }
  }
}

Windsurf

Codeium's agentic IDE.

json · ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "AutomatedOperations": {
      "serverUrl": "https://mcp.automatedoperations.com"
    }
  }
}

Windsurf uses serverUrl (not url) for remote servers.

Codex CLI

OpenAI's coding CLI.

toml · ~/.codex/config.toml

[mcp_servers.AutomatedOperations]
url = "https://mcp.automatedoperations.com"

Then run `codex mcp login AutomatedOperations` once to sign in — Codex doesn’t open the browser automatically.

Grok Build

xAI's full-screen TUI and agentic engineering environment.

bash

grok mcp add --transport http AutomatedOperations https://mcp.automatedoperations.com

Then open /mcps inside Grok Build and press "i" on the AutomatedOperations server to sign in.

Zed

High-performance collaborative editor.

json · ~/.config/zed/settings.json

{
  "context_servers": {
    "AutomatedOperations": {
      "url": "https://mcp.automatedoperations.com"
    }
  }
}

JetBrains IDEs

Junie coding agent + AI Assistant (IntelliJ IDEA, PyCharm, GoLand…).

json · ~/.junie/mcp/mcp.json

{
  "mcpServers": {
    "AutomatedOperations": {
      "command": "npx",
      "args": ["-y", "mcp-remote@^0.1.38", "https://mcp.automatedoperations.com/"]
    }
  }
}

Works in Junie CLI and the IDE plugin (needs Node 18+). The mcp-remote shim opens your browser to sign in on first use. Project-scoped alternative: .junie/mcp/mcp.json in the repo.

json

{
  "mcpServers": {
    "AutomatedOperations": {
      "command": "npx",
      "args": ["-y", "mcp-remote@^0.1.38", "https://mcp.automatedoperations.com/"]
    }
  }
}

Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add → As JSON, then paste. AI Assistant has no config file and no native OAuth yet — the mcp-remote shim handles sign-in.

VS Code

GitHub Copilot Chat / agent mode.

json · .vscode/mcp.json

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

Don’t see your client?

If your tool speaks MCP over streamable HTTP or SSE, the configuration above will work — just rename the keys to match your client’s schema. If it doesn’t, open the chat in the corner and tell us which client and we’ll wire it up the same day.

Get started