Your AI tools, plugged into 4weird.

The official @4weird/mcp Model Context Protocol server exposes 4weird capabilities — game QA runs, game state, squad tasks — to Claude Desktop, Cursor, and Antigravity. Three tools, typed schemas, zero risky worker search.

3: tools total
stdio: transport
Typed: input schemas
0: marketplace risk

Connect

Point your MCP client at the server

Install the @4weird/mcp package and register it as a stdio MCP server in your client. The server reads the API base URL from server-side environment only.

claude_desktop_config.json — server entry

your machine

{
  "mcpServers": {
    "4weird": {
      "command": "npx",
      "args": ["-y", "@4weird/mcp"],
      "env": {
        "FOURWEIRD_API_URL": "https://4weird.com"
      }
    }
  }
}

Tools reference

Three tools, typed inputs

ListTools advertises exactly these three tools. Every argument is validated against its input schema before any fetch runs.

@4weird/mcp — tool catalog

3 tools

run_vcw_game_test

Trigger an automated VibeCodeWorker game QA run and return detected bugs.

gameSlug* · captureMode: screenshot | state_data | full_state · durationSeconds (default 30)

get_game_state

Fetch live leaderboards, save state, and catalog metadata for a game.

gameSlug* (e.g. gravegain3d, xonotic)

query_squad_tasks

Retrieve active Kanban sprint cards and tasks for a squad.

squadId* (UUID)

Try it

First calls in three steps

Ask for game state
Prompt: “Using the 4weird MCP server, fetch the live state for gravegain3d.” The client calls get_game_state with your slug.
Trigger a QA run
Prompt: “Run a 30-second screenshot QA pass on xonotic.” The client calls run_vcw_game_test and returns detected bugs.
Check squad work
Prompt: “What is active on my squad sprint?” The client calls query_squad_tasks with the squad UUID.

Your AI tools, plugged into 4weird.

Point your MCP client at the server

Three tools, typed inputs

First calls in three steps

Ask for game state

Trigger a QA run

Check squad work

Your AI tools, plugged into 4weird.

Point your MCP client at the server

Three tools, typed inputs

First calls in three steps

Ask for game state

Trigger a QA run

Check squad work