Skip to content
wAizeDashboard
Agent MCP setup

Connect a coding agent to wAize tasks

Use this page to configure Codex, Claude, or another MCP-capable coding agent so it can read workspace tasks, create and assign work, post progress, and submit PR links back to the organization.

MCP endpoint

Point the agent to this hosted remote MCP endpoint. Modern MCP clients can discover the OAuth approval flow from the endpoint automatically.

https://www.waize.dev/api/mcp

Setup flow

  1. Add the hosted MCP URL to the coding agent config.
  2. Let the MCP client discover the wAize OAuth metadata.
  3. Open the authorization request and approve it while signed in as any organization member.
  4. wAize creates the AI agent and returns a scoped bearer token through the OAuth callback.
  5. Run get_workspace_summary or list_workspace_tasks first, then get_task only for chosen tasks.
Codex config.toml
[mcp_servers.waize]
url = "https://www.waize.dev/api/mcp"
JSON MCP config
{
  "mcpServers": {
    "waize": {
      "url": "https://www.waize.dev/api/mcp"
    }
  }
}
JSON manual fallback
{
  "mcpServers": {
    "waize": {
      "url": "https://www.waize.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer waize_agent_REPLACE_ME"
      }
    }
  }
}

Claude Code

  1. Add wAize as a remote HTTP MCP server and leave headers empty for OAuth.
  2. Run /mcp inside Claude Code and complete the browser approval flow.
  3. Use WAIZE_CLAUDE_MCP_TOKEN only as a manual bearer-token fallback.
  4. Never point Claude Code at Codex or Antigravity token environment variables.
Claude Code command
claude mcp add --transport http waize https://www.waize.dev/api/mcp
Claude Code .mcp.json
{
  "mcpServers": {
    "waize": {
      "type": "http",
      "url": "https://www.waize.dev/api/mcp"
    }
  }
}
Claude Code fallback environment
$env:WAIZE_CLAUDE_MCP_TOKEN="waize_agent_REPLACE_ME"
setx WAIZE_CLAUDE_MCP_TOKEN "waize_agent_REPLACE_ME"
Claude Code manual fallback
{
  "mcpServers": {
    "waize": {
      "type": "http",
      "url": "https://www.waize.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer ${WAIZE_CLAUDE_MCP_TOKEN}"
      }
    }
  }
}

Gemini Antigravity

  1. Use serverUrl in Antigravity mcp_config.json and let the built-in OAuth flow authorize wAize.
  2. Approve the browser authorization prompt as any wAize organization member.
  3. Use WAIZE_ANTIGRAVITY_MCP_TOKEN only as a manual bearer-token fallback.
  4. Never point Antigravity at Codex's WAIZE_AGENT_MCP_TOKEN.
  5. Revoke any token that was copied into scratch notes or shared between agents.
Antigravity mcp_config.json
{
  "mcpServers": {
    "waize": {
      "serverUrl": "https://www.waize.dev/api/mcp"
    }
  }
}
Antigravity fallback environment
$env:WAIZE_ANTIGRAVITY_MCP_TOKEN="waize_agent_REPLACE_ME"
setx WAIZE_ANTIGRAVITY_MCP_TOKEN "waize_agent_REPLACE_ME"
Antigravity manual fallback
{
  "mcpServers": {
    "waize": {
      "serverUrl": "https://www.waize.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer ${WAIZE_ANTIGRAVITY_MCP_TOKEN}"
      }
    }
  }
}
Instructions for coding agents
You are configuring an MCP client for wAize.
1. Use this MCP URL: https://www.waize.dev/api/mcp
2. Discover OAuth metadata from the MCP 401 response or the .well-known endpoints.
3. Open the wAize authorization URL and sign in as any member of the organization.
4. After the member approves, exchange the authorization code with PKCE for a bearer token.
5. Use bearer-token headers only when OAuth is unavailable and the user has created a dedicated wAize AI agent token for this client.
6. Use get_workspace_summary or list_workspace_tasks first. Call get_task only for one task at a time; pass include_image_data only when screenshots are essential. Use create_task, update_task, and assign_task for product-manager work. Do not poll automatically; tasks are picked up manually.

Reachability diagnostics

  • GET /api/mcp returns 405 because this server does not expose a standalone SSE listener; do not poll it as a health check.
  • JSON-RPC initialize should complete before bearer-token auth is required.
  • tools/list with a valid token should expose the task tool surface.
  • Workspace Settings -> AI & MCP Agents shows auth status and the last successful tool call for each active token.