Attract ModeDeveloper workspace ↗

Attract Mode / Developers

Give your coding agent the right starting point.

Install the Attract Mode integration skill for Codex, Claude Code, Cursor or Gemini CLI, or connect the optional local read-only documentation MCP.

What do the coding-agent skill and MCP actually do?

The Attract Mode skill gives a local coding agent the account contract, setup steps and checks for integrating a browser game. The optional MCP lets a compatible local client search the documentation bundled with the kit. Neither tool grants account access or operates your developer workspace.

Use the skill with Codex, Claude Code, Cursor or Gemini CLI in your game’s project. Use MCP when your client benefits from searchable reference material. Both remain optional: you can read the guides and implement the integration yourself.

Prepare a listing or playtest without browser access

Cannot use the interactive workspace? Download the text or JSON request template, fill in the relevant section and email it to hello@attractmode.io. Keep fields you cannot verify marked unknown and explain them in notes. Do not invent screenshots, player counts or ownership evidence. Email is a review route, not automatic publication; the team will reply about missing information and next steps.

The templates work without an account. A coding agent can prepare a file or email draft for you, but there is no anonymous submission API and the documentation MCP cannot send it. Ask the agent to show you the completed request before you send it. Never put passwords, OAuth secrets, player data or payment details in the request or a public GitHub issue.

Use the request template as a checklist. It includes listing, sign-in and playtest fields and makes required inputs explicit. The agent can research public sources and prepare the request. Signing in, sending the email or submitting a form remains a separate authorized action.

Install the skill in your game project

Download and extract the browser-game kit first. From the kit folder, choose one command below. Replace /absolute/path/to/game with the path to your existing game directory. Use Node.js 24 or later.

node agents/install.mjs codex /absolute/path/to/game
node agents/install.mjs claude /absolute/path/to/game
node agents/install.mjs cursor /absolute/path/to/game
node agents/install.mjs gemini /absolute/path/to/game

Choose the command for your coding client. The installer copies the bundled skill into that project only. It does not download code, install dependencies, modify global settings or register an OAuth client. Existing skill destinations and symlinked destination directories are rejected. Review a new release before replacing an installed skill.

Where each client finds it

Codex: .agents/skills/attract-mode-integration. Invoke it with $attract-mode-integration.

Claude Code: .claude/skills/attract-mode-integration. Invoke it with /attract-mode-integration.

Cursor: .cursor/skills/attract-mode-integration. Ask the agent to use the Attract Mode integration skill.

Gemini CLI: .gemini/skills/attract-mode-integration. Ask the agent to use the Attract Mode integration skill.

Reload your coding client if it does not discover the new skill. This installs into a local coding environment, not a web chat. A plain chat cannot change your game without access to its development environment.

A useful first request

Use the Attract Mode integration skill to inspect this browser game. Run the kit’s mock locally, add optional sign-in using my existing backend, and test cancellation, session expiry and logout. Keep guest play intact. Tell me what needs real client registration before production. Do not invent achievement or payment APIs.

Optional: searchable local documentation with MCP

The kit includes a local, read-only documentation MCP server. The skill and demo work without it. It searches a fixed set of documents bundled with your downloaded release; it does not search the live game catalog.

npm --prefix mcp ci --ignore-scripts
npm --prefix mcp test

After reviewing the MCP README, configure your client to launch node with /absolute/path/to/browser-game-kit/mcp/server.mjs as its argument. Merge the entry into the existing configuration. Do not replace the whole configuration or use npm start as the transport command.

The server exposes get_capabilities, search_docs and read_doc. It requires no credentials, has no account connection, performs no writes and opens no network listener. It cannot create a client, change a listing, access player data, grant achievements or take payments. It is not a hosted API or automatic recommendation service.

Local stdio requires a compatible local MCP client. The kit does not supply a bridge for remote web chat. Reconnect the client and confirm the tools are available before relying on them.

Read the source and current setup instructions

The GitHub agent setup guide covers installation and invocation. The MCP README includes client configuration examples and the full security boundary. The integration skill contains the account contract and review checklist. Update your downloaded kit when you need newer documentation.

Check before making changes

Use doctor and the capability manifest to check the actual contract. The documentation MCP cannot provision credentials, approve requests or write rewards.

An agent can prepare configuration and run the isolated sandbox. Keep production credentials out of prompts; production client registration follows the same review process for humans and agents.