Other clients

The local American Cloud MCP server works with any client that supports MCP stdio servers. This page covers Windsurf and VS Code, plus the generic configuration that applies to everything else. A client that supports remote servers with OAuth sign-in can use the hosted server instead; that path is verified with Claude, Claude Code, ChatGPT, Codex, Cursor and Grok.

In every case you need:

• Node.js 20 or newer
• An American Cloud API token from console.americancloud.com/api-tokens — start with the Read-only preset. An API key from before tokens existed (a client ID and secret) still works: set AMERICANCLOUD_API_CLIENT_ID and AMERICANCLOUD_API_CLIENT_SECRET instead of the token.

Windsurf

Windsurf reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Open it from the Cascade panel (MCP icon → Configure) or edit it directly:

{
  "mcpServers": {
    "americancloud": {
      "command": "npx",
      "args": ["-y", "@americancloud/mcp"],
      "env": {
        "AMERICANCLOUD_API_TOKEN": "your-api-token"
      }
    }
  }
}

Refresh the MCP server list in Cascade (or restart Windsurf), then ask:

What regions can I deploy to on American Cloud?

VS Code

VS Code configures MCP servers for agent mode in .vscode/mcp.json (workspace) or your user profile. VS Code uses a servers key and supports prompted inputs, so you never write the token into the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "ac-api-token",
      "description": "American Cloud API token",
      "password": true
    }
  ],
  "servers": {
    "americancloud": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@americancloud/mcp"],
      "env": {
        "AMERICANCLOUD_API_TOKEN": "${input:ac-api-token}"
      }
    }
  }
}

VS Code prompts for the token the first time the server starts and stores it securely. Start the server from the MCP view (or when an agent first uses it), then test with the same regions question in Copilot's agent mode.

Any other MCP client

The server is a standard MCP stdio server. Whatever your client's configuration looks like, the three things it needs are:

Optional flags go after the package name in the arguments — for example --services all or --allow-writes. See the overview for what they do.

Enable resource management (optional)

By default the server is read-only in every client. To enable create/update/delete tools, use a token with Full access and add --allow-writes to the arguments:

"args": ["-y", "@americancloud/mcp", "--allow-writes"]

Destructive operations are flagged, so clients that support confirmations will prompt you before running them.

Next steps

• Things to try — prompt ideas from quick audits to full provisioning
• Overview — service groups, --services scoping, and safety details