Claude Code and Codex Plugins
The Portals plugin turns Claude Code or Codex into a Portals web-game editor. It ships two things: the portals-web-games MCP server, which reaches your games on My Games, and a set of skills that carry the platform documentation, so the assistant loads the rules for the SDK, multiplayer, Coins, or Guardian avatars when it needs them instead of guessing.
Both plugins contain the same server and the same skills. Install the one for your editor.
This is the plugin for hosted web games — JavaScript projects you push, preview, and publish. To connect an assistant to the Portals room editor instead, follow the MCP setup guide.
Requirements
- A Portals account.
- Node.js 18 or newer. The MCP server is a self-contained bundle inside the plugin, so there is nothing else to install.
Install in Claude Code
claude plugin marketplace add portals-labs/portals-plugin-claude
claude plugin install portals-plugin-claude@portals
Restart the session to load it. Source: portals-labs/portals-plugin-claude.
Install in Codex
codex plugin marketplace add portals-labs/portals-plugin-openai
codex plugin add portals-plugin-openai@portals
Then start a new Codex session — an open one does not see a freshly installed plugin. To take a later release, run codex plugin marketplace upgrade and then codex plugin add portals-plugin-openai@portals again. Source: portals-labs/portals-plugin-openai.
Sign in
Ask the assistant to call the authenticate tool. It opens Portals sign-in in your browser and stores the resulting access key locally, so later sessions connect without asking again.
If you prefer to supply the key yourself, copy it from portals.to/mcp and set PORTALS_ACCESS_KEY in the environment the editor launches. The server reads it on startup and authenticates with no prompt. Treat the key like a password: it is tied to your account, and you can revoke it by generating a new one on the same page.
What the server can do
| Area | What it covers |
|---|---|
| Game projects | List your games, create one, push local source up, pull the current source back down, and get a share link. |
| Publishing | Update game settings and publish a version for players. |
| Multiplayer testing | Mint a short-lived development token so a local build can join sessions. |
| Coin products | Read and update the product catalog, and run a sandbox purchase before going live. |
| Generated assets | Generate images, textures, 3D models, speech, sound effects, and music, then save them to a game. |
| Marketplace and avatars | Browse and claim marketplace assets, and list or save avatar wearables. |
What the skills cover
Each skill is the same material as the guide it is named after, packaged so the assistant can pull it on demand:
| Skill | Guide |
|---|---|
portals-web-games |
The platform rules for a hosted game: injected SDK, host-owned UI, sandbox limits, and asset handling |
portals-sdk |
Portals SDK |
portals-game-economy |
Sell game products for Coins |
portals-guardian-avatars |
Guardian Avatars |
portals-pose-tuner |
Pose Tuner |
portals-multiplayer-and-voice |
Multiplayer, Chat, and Voice |
portals-server-scripts |
Server Scripts |
portals-server-sim |
Server-Simulated Games |
First workflow
- Ask the assistant to authenticate, then to list your games. If both work, the plugin is connected.
- Create a new game, or pull the source of one you already own.
- Make one small change, push it, and open the share link to check it in the browser.
- Publish when the player path works.
Work on a test game before pointing the assistant at a published one, and read what it proposes before approving a push: a push replaces the project source that a later publish ships.