MCP Server Guide

Click your avatar in the bottom-left sidebar. The Profile modal opens.

Find the 🔒 MCP Agent Tokens section below your avatar. Click + New.

Enter a descriptive name (e.g. Claude Desktop). Select the scopes your agent needs:

• read:tasks — list and read your assigned tasks
• write:tasks — update task status
• write:commits — create commit history entries on tasks

The token is shown once only — copy it right away and store it securely. It will never be displayed again.

The MCP endpoint for your WORK-X instance is:

https://<your-instance>/api/mcp/rpc

For a local dev setup: http://localhost:4000/mcp/rpc

Open the Claude Desktop config file:

# macOS
~/Library/Application Support/Claude/claude_desktop_config.json

# Windows
%APPDATA%\Claude\claude_desktop_config.json

Add your MCP server under mcpServers:

{
  "mcpServers": {
    "work-x": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<your-instance>/api/mcp/rpc",
        "--header",
        "Authorization: Bearer <your-personal-token>"
      ]
    }
  }
}

Fully quit and relaunch Claude Desktop. In a new conversation, type 🔌 or click the MCP tools icon — you should see the WORK-X tools available.

Antigravity reads MCP servers from its config file located at:

~/.gemini/antigravity/mcp_config.json

Open the file (create it if it doesn't exist yet).

Add a new entry under mcpServers. Pass your token via the --header flag:

{
  "mcpServers": {
    "work-x": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://<your-instance>/api/mcp/rpc",
        "--header",
        "Authorization: Bearer <your-personal-token>"
      ]
    }
  }
}

For a local dev setup:

{
  "mcpServers": {
    "work-x": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "http://localhost:4000/mcp/rpc",
        "--header",
        "Authorization: Bearer <your-personal-token>"
      ]
    }
  }
}

If you already have other MCP servers configured (e.g. figma-dev-mode-mcp-server), simply add work-x as an additional key alongside them.

Restart or reload Antigravity. It will automatically spawn the mcp-remote bridge process and connect to your WORK-X instance. You'll see the WORK-X tools available in the tool palette.

POST https://<your-instance>/api/mcp/rpc
Authorization: Bearer <your-mcp-token>
Content-Type: application/json

# Request
curl -X POST https://<your-instance>/api/mcp/rpc \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

# Response
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "tools": [
      { "name": "listMyTasks", "scope": "read:tasks", "tokenType": "user", ... },
      { "name": "updateTaskStatus", "scope": "write:tasks", ... }
    ]
  }
}

# tools/call — execute a tool
curl -X POST https://<your-instance>/api/mcp/rpc \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "listMyTasks",
      "arguments": {}
    },
    "id": 2
  }'

Send multiple calls in one HTTP round-trip by wrapping them in a JSON array:

[
  {"jsonrpc":"2.0","method":"tools/call","params":{"name":"listMyTasks","arguments":{}},"id":1},
  {"jsonrpc":"2.0","method":"tools/call","params":{"name":"updateTaskStatus","arguments":{"taskId":"abc","status":"DONE"}},"id":2}
]