Loading 4weird…

DocsIntegrations

Docs · integrations

4weird, inside your tools.

Two official integration surfaces: the @4weird/mcp Model Context Protocol server for AI coding tools, and the chat bot for clan raids, leaderboards, and squad status. Both read from the same APIs — no risky worker search tools, no secrets in chat.

3: mcp tools
2+: slash commands
API-keyed: server side only
Fail: open, never bricked

Two surfaces

Pick your integration

MCP guide →

@4weird/mcp server

Point Claude Desktop, Cursor, or Antigravity at 4weird: game tests, game state, squad tasks.

Chat guide →

Chat bot

Slash commands for leaderboards and squad status; env-only token setup.

Ground rules

Same rules as everything else

Integrations obey the remastery axioms: fail-open behavior when an external service is unreachable, standard events on the interop bus, and secrets only in server-side environment — never in chat, docs, or committed files.

Fail open
If the 4weird API or chat gateway is unreachable, integrations degrade to graceful error states — they never brick navigation.
Secrets stay server-side
Tokens and keys live in environment variables on the host. If a setup step asks for a token, it names the env var — never a value.
Least privilege
The MCP server exposes exactly three tools; the bot answers slash commands in-guild. Neither can search workers or touch wallets.

4weird, inside your tools.

Pick your integration

Same rules as everything else

Fail open

Secrets stay server-side

Least privilege

4weird, inside your tools.

Pick your integration

Same rules as everything else

Fail open

Secrets stay server-side

Least privilege