Warp Cloud Agents MCP client setup

Warp Cloud Agents should use bearer headers. Do not configure OAuth for Warp cloud agents today.

Config

{
  "name": "orkestia-agent",
  "model_id": "WARP_SUPPORTED_MODEL",
  "system_prompt": "Use Orkestia workflow tools when workflow execution or status is requested.",
  "environment_id": "WARP_ENVIRONMENT_ID",
  "mcp_servers": {
    "orkestia-workflow": {
      "url": "https://mcp.orkestia.dev/mcp",
      "headers": {
        "Authorization": "Bearer {{ORKESTIA_AGENT_TOKEN}}"
      }
    }
  }
}

Store ORKESTIA_AGENT_TOKEN in the Warp environment, not in source control.

Token requirements

Use a scoped token per Warp agent or per Warp environment. The token should be revocable without affecting human OAuth clients.

Smoke test

1. Launch a Warp cloud agent with the MCP server configured.
2. Ask it to call whoami.
3. Ask it to list workflow types.
4. Rotate the token and confirm the old token fails.

Official docs

• Warp Cloud Agents MCP