On this page

MCP Server

GuaraCloud exposes a hosted Model Context Protocol endpoint at:

https://mcp.guaracloud.com/mcp

Use it from MCP-compatible AI clients to inspect projects, manage services, deploy, query logs, work with cron workers, manage domains, and run the same remote operations available in the GuaraCloud CLI.

Authentication

The MCP server authenticates with GuaraCloud API keys. Create an API key in the dashboard and pass it as either:

X-API-Key: gk_live_...

or:

Authorization: Bearer gk_live_...

X-API-Key is checked first; Authorization: Bearer is supported for clients that only allow Authorization headers (it is normalised to the same upstream call).

Read-only API keys can list and inspect resources. Tools that mutate resources require a write-scoped API key.

Client configuration

Claude Code

The fastest way to wire GuaraCloud into Claude Code is the built-in claude mcp add command:

claude mcp add guaracloud https://mcp.guaracloud.com/mcp \
  -h "X-API-Key: gk_live_..." \
  --transport http

Replace gk_live_... with the API key you created in the GuaraCloud dashboard. Claude Code persists the entry in its MCP registry and the tools become available on the next session.

Other MCP clients

Most MCP clients (Cursor, Continue.dev, custom integrations) accept a streamable HTTP transport entry. Point them to the hosted endpoint:

{
  "mcpServers": {
    "guaracloud": {
      "url": "https://mcp.guaracloud.com/mcp",
      "headers": {
        "X-API-Key": "gk_live_..."
      }
    }
  }
}

Available tools

The MCP server publishes one tool per remote-capable CLI command. Tool names use MCP-safe underscores, including:

  • projects_list, projects_create, projects_info, projects_map, projects_observatory
  • services_list, services_create, services_info, services_start, services_stop, services_restart, services_resize, services_delete
  • deploy, deployments_list, rollback, status, logs, build_logs, scale
  • env_list, env_set, env_unset
  • domains_list, domains_add, domains_remove
  • catalog_list, catalog_info, catalog_schema, catalog_query, catalog_deploy
  • crons_list, crons_create, crons_info, crons_update, crons_delete, crons_suspend, crons_resume, crons_trigger, crons_runs
  • services_metrics, services_traces_list, services_traces_get, services_vulnerabilities, services_profiles_get

Local-only CLI commands such as login, logout, and local config file updates are represented as MCP-safe authentication or context checks because MCP clients do not store the CLI keychain or .guara.json file.

Example request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "services_list",
    "arguments": {
      "projectSlug": "my-project"
    }
  }
}
  1. Create a read-only API key for inspection workflows.
  2. Create a separate write-scoped API key only for agents allowed to deploy or mutate resources.
  3. Store keys in your MCP client’s secret manager or environment variable support.
  4. Revoke keys from the GuaraCloud dashboard when rotating access.