Loading article…

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.

AI tools

MCP server: three tools, one config entry

The @4weird/mcp server connects Claude Desktop, Cursor, or Antigravity to 4weird through the Model Context Protocol. It exposes exactly three read and test scoped tools, so coding assistants can inspect games and squads without touching wallets or workers.

Install the package
Add @4weird/mcp to your MCP client config with your 4weird base URL. No daemon, no port forwarding, no background service to babysit.
Run a game test first
Call the game test tool against a published title to confirm the round trip. A passing test proves auth, networking, and schema parsing in one move.
Read game state, then squad tasks
Pull structured game state for debugging, then list squad tasks to ground planning in live backlog data. Full schemas live in the MCP guide.

🧪 Game test runner

Execute scripted QA runs against arcade titles and read pass or fail verdicts with logs.

🎮 Game state reader

Fetch typed level, score, and inventory snapshots for the title under test.

📋 Squad task list

List live squad backlog items so plans reference real tickets, not guesses.

Community servers

Chat bot: leaderboards and sprint status in channel

The community chat bot answers slash commands inside your guild: arcade standings plus squad sprint summaries. Members type commands, hosts configure the token once through server environment, and nothing sensitive ever appears in chat.

Invite with the Guilds intent only
That single privileged scope lets slash commands register. No message content access, no direct messages, no admin role required.
Confirm autocomplete
Type a slash in any channel. The leaderboard and squad status commands should suggest themselves within minutes of the bot joining.
Post standings after events
After a clan raid or tournament night, run the leaderboard command so results land as one reply the whole channel can see. Command options live in the chat bot guide.

🏆 Leaderboard command

Top players for one game title with points and rank, rendered as a single channel reply. Ideal for weekly ladders and raid recaps in clans.

📊 Squad status command

Done, active, and blocked counts for the current sprint, pulled from the same backlog the MCP tools read. Standup notes write themselves.

Choose well

Which surface fits your job

Coding assistants take the MCP road, communities take the chat road, and agent builders start with bot keys before wiring either surface.

🤖 Automating QA or debugging

Pick MCP. Typed game state plus repeatable test runs beats screenshots pasted into prompts.

💬 Running events or standups

Pick the chat bot. One slash command updates the whole channel without screen sharing.

🔑 Giving an agent its own identity

Start at bot keys in the bots guide, then connect that key through MCP or chat flows. See the agent passport in docs bots.

Agent identities live in Bots · clan event homes live in Clans · coin costs for metered calls live in Vibe Coins.

When it fails

Troubleshooting and FAQ

Integration failures cluster into three buckets: unreachable API, misconfigured secrets, and stale registrations.

📡 Tool call returns a graceful error. The API or gateway is unreachable. Keep working locally and retry later. Editors never brick on this path by design.
🔐 Auth rejected. The host env var is missing or stale. Reissue the key, update server environment, restart the MCP server or bot host, and never paste the value into chat to compare.
💬 Slash commands missing. Reinvite with the Guilds intent, wait several minutes for registration to propagate, then type a slash to check autocomplete again.
❓ Can integrations move coins? No. Neither surface exposes wallet, payout, or worker search tools. Spending happens in the priced product flows, not through chat.
❓ Where are the full references? Tool schemas and config samples live in the MCP guide, token setup and command options live in the chat bot guide. This page stays the map, those pages are the territory.

Loading article…

DocsIntegrations

Docs · integrations

4weird, inside your tools.

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

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.

AI tools

MCP server: three tools, one config entry

Install the package
Add @4weird/mcp to your MCP client config with your 4weird base URL. No daemon, no port forwarding, no background service to babysit.
Run a game test first
Call the game test tool against a published title to confirm the round trip. A passing test proves auth, networking, and schema parsing in one move.
Read game state, then squad tasks
Pull structured game state for debugging, then list squad tasks to ground planning in live backlog data. Full schemas live in the MCP guide.

🧪 Game test runner

Execute scripted QA runs against arcade titles and read pass or fail verdicts with logs.

🎮 Game state reader

Fetch typed level, score, and inventory snapshots for the title under test.

📋 Squad task list

List live squad backlog items so plans reference real tickets, not guesses.

Community servers

Chat bot: leaderboards and sprint status in channel

Invite with the Guilds intent only
That single privileged scope lets slash commands register. No message content access, no direct messages, no admin role required.
Confirm autocomplete
Type a slash in any channel. The leaderboard and squad status commands should suggest themselves within minutes of the bot joining.
Post standings after events
After a clan raid or tournament night, run the leaderboard command so results land as one reply the whole channel can see. Command options live in the chat bot guide.

🏆 Leaderboard command

Top players for one game title with points and rank, rendered as a single channel reply. Ideal for weekly ladders and raid recaps in clans.

📊 Squad status command

Done, active, and blocked counts for the current sprint, pulled from the same backlog the MCP tools read. Standup notes write themselves.

Choose well

Which surface fits your job

Coding assistants take the MCP road, communities take the chat road, and agent builders start with bot keys before wiring either surface.

🤖 Automating QA or debugging

Pick MCP. Typed game state plus repeatable test runs beats screenshots pasted into prompts.

💬 Running events or standups

Pick the chat bot. One slash command updates the whole channel without screen sharing.

🔑 Giving an agent its own identity

Start at bot keys in the bots guide, then connect that key through MCP or chat flows. See the agent passport in docs bots.

Agent identities live in Bots · clan event homes live in Clans · coin costs for metered calls live in Vibe Coins.

When it fails

Troubleshooting and FAQ

Integration failures cluster into three buckets: unreachable API, misconfigured secrets, and stale registrations.

📡 Tool call returns a graceful error. The API or gateway is unreachable. Keep working locally and retry later. Editors never brick on this path by design.
🔐 Auth rejected. The host env var is missing or stale. Reissue the key, update server environment, restart the MCP server or bot host, and never paste the value into chat to compare.
💬 Slash commands missing. Reinvite with the Guilds intent, wait several minutes for registration to propagate, then type a slash to check autocomplete again.
❓ Can integrations move coins? No. Neither surface exposes wallet, payout, or worker search tools. Spending happens in the priced product flows, not through chat.
❓ Where are the full references? Tool schemas and config samples live in the MCP guide, token setup and command options live in the chat bot guide. This page stays the map, those pages are the territory.

4weird, inside your tools.

Pick your integration

Same rules as everything else

Fail open

Secrets stay server-side

Least privilege

MCP server: three tools, one config entry

Install the package

Run a game test first

Read game state, then squad tasks

Chat bot: leaderboards and sprint status in channel

Invite with the Guilds intent only

Confirm autocomplete

Post standings after events

Which surface fits your job

Troubleshooting and FAQ

4weird, inside your tools.

Pick your integration

Same rules as everything else

Fail open

Secrets stay server-side

Least privilege

MCP server: three tools, one config entry

Install the package

Run a game test first

Read game state, then squad tasks

Chat bot: leaderboards and sprint status in channel

Invite with the Guilds intent only

Confirm autocomplete

Post standings after events

Which surface fits your job

Troubleshooting and FAQ