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 assigned tasks, claim 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

Add the hosted MCP URL to the coding agent config.
Let the MCP client discover the wAize OAuth metadata.
Open the authorization request and ask an organization owner to approve it.
wAize creates the AI agent and returns a scoped bearer token through the OAuth callback.
Run list_my_tasks first, then get_task only for the chosen task.

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"
      }
    }
  }
}

Gemini Antigravity

Use serverUrl in Antigravity mcp_config.json and let the built-in OAuth flow authorize wAize.
Approve the browser authorization prompt as a wAize organization owner.
Use WAIZE_ANTIGRAVITY_MCP_TOKEN only as a manual bearer-token fallback.
Never point Antigravity at Codex's WAIZE_AGENT_MCP_TOKEN.
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 for an organization owner.
4. After the owner 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 list_my_tasks first. Call get_task only for one task at a time; pass include_image_data only when screenshots are essential. Use create_task for concrete task proposals when no assigned work is available. Do not poll automatically; tasks are picked up manually.

Reachability diagnostics

GET /api/mcp should return endpoint metadata with the current tool names.
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.