Cursor
Last updated: June 19, 2026
This guide connects Cursor to American Cloud, so Cursor's agent can inspect and manage your infrastructure alongside your code.
Prerequisites
- Cursor installed
- Node.js 20 or newer
- An American Cloud API key from console.americancloud.com/api-keys — start with a read-only key
Configure
Cursor reads MCP servers from a JSON file at either level:
- Project:
.cursor/mcp.jsonin your repository (applies to that project) - Global:
~/.cursor/mcp.jsonin your home directory (applies everywhere)
Create the file (or open Cursor Settings → MCP → Add new MCP server) and add:
{
"mcpServers": {
"americancloud": {
"command": "npx",
"args": ["-y", "@americancloud/mcp"],
"env": {
"AMERICANCLOUD_API_CLIENT_ID": "your-client-id",
"AMERICANCLOUD_API_CLIENT_SECRET": "your-client-secret"
}
}
}
}If you use a project-level .cursor/mcp.json in a shared repository, don't
put a real secret in it — keep the server config global instead, or add the
file to .gitignore.
Cursor detects the change automatically; if the server doesn't appear, toggle it in Cursor Settings → MCP or restart Cursor.
Verify
Open the agent panel and ask:
What regions can I deploy to on American Cloud?
The agent will request approval to run the American Cloud tool the first time.
Enable resource management (optional)
By default the server is read-only. To let the agent create and manage resources, use a read-write API key and add the flag:
"args": ["-y", "@americancloud/mcp", "--allow-writes"]Cursor asks for approval before tool calls unless you've enabled auto-run, and destructive operations are explicitly flagged. We recommend keeping approval on for write-enabled setups.
Next steps
- Things to try — prompt ideas from quick audits to full provisioning
- Overview — service groups,
--servicesscoping, and safety details