Quick start: connect your AI
Gamentic is an MCP server. Point your assistant at one URL with one key, and it gains 72 tools for writing, illustrating, scoring, testing and publishing HTML5 games — while you keep your own model and your own context window.
The two values you need
| Setting | Value |
|---|---|
| Endpoint | https://mcp.gamentic.net/mcp — MCP Streamable HTTP |
| Auth header | Authorization: Bearer gi_… |
Two ways to connect. Claude (web, Desktop and mobile) and ChatGPT connect by signing in to
Gamentic — there is no key to copy. Other clients, including Cursor, VS Code and Codex, send an MCP key
in the Authorization header.
1. Create an MCP key
-
Sign in
Go to gamentic.net/account. If you do not have an account yet, create one — the Free plan comes with free credits every 30 days.
-
Open MCP Keys
In the account sidebar, choose MCP Keys, then + New key.
-
Name it after the client
Use one key per AI client —
claude-desktop-laptop,codex-work. Then you can see which machine is generating, and revoke just that one if you need to. -
Copy it now
The key starts with
gi_. The table only ever shows a truncated form afterwards, so paste it into your client's config before you leave the page.
A key spends your credits. Anything an AI generates while holding it is billed to your wallet. Treat it like a payment credential: never commit it to a public repository, and revoke it from the same page the moment you suspect it has leaked.
2. Add the server to your client
Pick your AI below — each one has its exact steps. Claude and ChatGPT connect by signing in; every other client uses the key from step 1. Not listed? Enter the two values at the top of this page in your client’s own MCP settings.
Claude Sign-in
Works on every Claude plan; the Free plan allows one custom connector. On Team and Enterprise, an Owner adds it, and connectors must be turned on for the organization first.
-
Open Customize → Connectors.
-
If you don't see Add custom connector, click + first.
-
Click Add custom connector.
-
Enter
Gamenticin Name. -
Enter
https://mcp.gamentic.net/mcpin MCP server URL. -
Leave Advanced settings and Request headers empty.
-
Click Add.
-
Click Connect.
-
Sign in to Gamentic in the window that opens, then click Allow.
-
Open + → Connectors.
-
Choose On for Gamentic.
-
On a phone: add it on the web or in the desktop app first, and it then appears in the mobile app.
The dialog has two steps (Authentication and OAuth client)
-
Open Customize → Connectors.
-
Click Add custom connector.
-
Enter
Gamenticin Name. -
Enter
https://mcp.gamentic.net/mcpin MCP server URL. -
Choose Sign in now for Authentication.
-
Choose Use Claude's published identity for OAuth client.
-
Click Add.
-
Click Connect.
-
Sign in to Gamentic in the window that opens, then click Allow.
Team or Enterprise: an Owner adds it once, then each member clicks Connect and signs in
-
Open Organization settings → Connectors.
-
Click Add.
-
Click Custom.
-
Click Web.
-
Enter
https://mcp.gamentic.net/mcpin MCP server URL. -
Click Add.
-
Open Customize → Connectors.
-
Click Connect.
-
Sign in to Gamentic in the window that opens, then click Allow.
ChatGPT Sign-in
Needs ChatGPT on the web with Plus, Pro, Business, Enterprise or Edu; not available in the mobile apps. On Business only admins can use developer mode; on Enterprise and Edu an admin must grant access.
-
Open Settings → Security and login.
-
Choose On for Developer mode.
-
Open Plugins.
-
Click +.
-
If you see Create app first, click it, then choose Create MCP App.
-
Click Create MCP App.
-
Enter
gamenticin Name. -
If the form asks for a Description, enter Gamentic.
-
Enter
https://mcp.gamentic.net/mcpin Server URL. -
Choose OAuth for Authentication.
-
If the form shows an OAuth client ID or secret field, leave it empty.
-
Tick I understand and want to continue.
-
Click Create.
-
Sign in to Gamentic in the window that opens, then click Allow.
-
In a new chat, pick gamentic from the + menu (or under More) to use it.
Workspace admin (Workspace settings layout)
-
Open Workspace settings → Apps.
-
Click Create.
-
Enter
gamenticin Name. -
Enter
https://mcp.gamentic.net/mcpin Server URL. -
Choose OAuth for Authentication.
-
Click Scan Tools.
-
Sign in to Gamentic in the window that opens, then click Allow.
-
Click Create.
Claude Code Sign-in or key
Claude Code must be installed and signed in. The same command works in bash, zsh, PowerShell and Command Prompt.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Run this in a terminal:
bashclaude mcp add --transport http --scope user gamentic https://mcp.gamentic.net/mcp --header "Authorization: Bearer gi_your_key_here" -
Run
claude mcp listand check that gamentic shows as connected.
Sign in instead of using a key
-
Update Claude Code to the latest version first.
-
Run this in a terminal:
bashclaude mcp add --transport http --scope user gamentic https://mcp.gamentic.net/mcp -
Run this in a terminal:
bashclaude mcp login gamentic -
Sign in to Gamentic in the window that opens, then click Allow.
-
Run
claude mcp listand check that gamentic shows as connected.
Share .mcp.json with your team (key in an environment variable)
-
Save your key in the environment variable
GAMENTIC_API_KEY(reopen your terminal and apps afterwards so they pick it up):macOS (zsh)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.zshrcLinux (bash)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.bashrcWindows (PowerShell)setx GAMENTIC_API_KEY "gi_your_key_here" -
Open
<project>/.mcp.json(create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "type": "http", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer ${GAMENTIC_API_KEY}" } } } } -
Restart Claude Code so it loads the new server.
-
When Claude Code asks whether to use this project's servers, approve gamentic.
-
Run
/mcpand check that gamentic shows as connected.
Codex Uses a key
You need Codex signed in, through a ChatGPT plan that includes Codex or an OpenAI API key. The CLI, the IDE extension and the ChatGPT desktop app share one config.toml.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Save your key in the environment variable
GAMENTIC_API_KEY(reopen your terminal and apps afterwards so they pick it up):macOS (zsh)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.zshrcLinux (bash)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.bashrcWindows (PowerShell)setx GAMENTIC_API_KEY "gi_your_key_here" -
Run this in a terminal:
bashcodex mcp add gamentic --url https://mcp.gamentic.net/mcp --bearer-token-env-var GAMENTIC_API_KEY -
Start Codex from a new terminal window so it can read GAMENTIC_API_KEY.
-
Run
/mcpand check that gamentic shows as connected.
Codex IDE extension (VS Code, Cursor, Windsurf)
-
Save your key in the environment variable
GAMENTIC_API_KEY(reopen your terminal and apps afterwards so they pick it up):macOS (zsh)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.zshrcLinux (bash)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.bashrcWindows (PowerShell)setx GAMENTIC_API_KEY "gi_your_key_here" -
Open ⚙ → Codex Settings → Open config.toml.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
toml[mcp_servers.gamentic] url = "https://mcp.gamentic.net/mcp" bearer_token_env_var = "GAMENTIC_API_KEY" -
Restart VS Code / Cursor / Windsurf so it loads the new server.
-
Check that gamentic shows as connected in ⚙ → MCP servers.
ChatGPT desktop app, or when Codex cannot see the environment variable
-
Open
~/.codex/config.toml(%USERPROFILE%\.codex\config.tomlon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
toml[mcp_servers.gamentic] url = "https://mcp.gamentic.net/mcp" http_headers = { "Authorization" = "Bearer gi_your_key_here" } -
If there is already an [mcp_servers.gamentic] section, replace it with this one. The file now holds your key, so never share it.
-
Restart Codex so it loads the new server.
-
Run
/mcpand check that gamentic shows as connected.
Gemini CLI Uses a key
Since 2026-06-18, Gemini CLI is available only with Gemini Code Assist Standard/Enterprise and paid API keys. Free and Google AI Pro/Ultra accounts should use the Antigravity CLI instead.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Run this in a terminal:
bashgemini mcp add -s user -t http -H "Authorization: Bearer gi_your_key_here" gamentic https://mcp.gamentic.net/mcp -
Restart Gemini CLI so it loads the new server.
-
Choose Trust folder for Do you trust the files in this folder?.
-
Run
/mcp listand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.gemini/settings.json(%USERPROFILE%\.gemini\settings.jsonon Windows; create it if it does not exist). -
Keep the other settings already in this file and only add the mcpServers part.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "type": "http", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Gemini CLI so it loads the new server.
-
Choose Trust folder for Do you trust the files in this folder?.
Antigravity CLI Uses a key
Needs Antigravity CLI 1.1.16 or later; works on every Antigravity plan, including free.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Antigravity CLI to the latest version first.
-
Run this in a terminal:
bashagy mcp add --header "Authorization: Bearer gi_your_key_here" gamentic https://mcp.gamentic.net/mcp -
Restart Antigravity CLI so it loads the new server.
-
Run
/mcpand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.gemini/config/mcp_config.json(%USERPROFILE%\.gemini\config\mcp_config.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "serverUrl": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Antigravity CLI so it loads the new server.
GitHub Copilot CLI Uses a key
You need GitHub Copilot CLI signed in with a Copilot plan. An organization MCP allowlist can block it.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Run this in a terminal:
bashcopilot mcp add --transport http --header "Authorization: Bearer gi_your_key_here" --timeout 120000 gamentic https://mcp.gamentic.net/mcp -
Run
copilot mcp listand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.copilot/mcp-config.json(%USERPROFILE%\.copilot\mcp-config.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "type": "http", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" }, "tools": [ "*" ], "timeout": 120000 } } } -
Restart GitHub Copilot CLI so it loads the new server.
-
Run
/mcpand check that gamentic shows as connected.
Qwen Code Uses a key
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Run this in a terminal:
bashqwen mcp add -s user -t http -H "Authorization: Bearer gi_your_key_here" gamentic https://mcp.gamentic.net/mcp -
Restart Qwen Code so it loads the new server.
-
Run
qwen mcp listand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.qwen/settings.json(%USERPROFILE%\.qwen\settings.jsonon Windows; create it if it does not exist). -
Keep the other settings already in this file and only add the mcpServers part.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "httpUrl": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Qwen Code so it loads the new server.
Qwen Code Desktop app
-
Open ⋮ Workspace actions → MCP.
-
Click Add.
-
Enter
gamenticin Name. -
Choose Global for Location.
-
Delete the sample text in Configuration (JSON), then paste this.
json{ "httpUrl": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } -
Click Add.
Cline CLI Uses a key
Needs Cline CLI 3.0.30 or later.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Run this in a terminal:
bashnpm install -g cline@latest -
Run this in a terminal:
bashcline mcp install gamentic --transport http https://mcp.gamentic.net/mcp --header "Authorization: Bearer gi_your_key_here" --yes -
Restart Cline CLI so it loads the new server.
-
The Cline extensions for VS Code and JetBrains share this setting, so they get gamentic too.
Interactive setup
-
Run this in a terminal:
bashcline mcp -
Choose Add server for What would you like to do?.
-
Enter
gamenticin Server name. -
Choose Remote (HTTP) for Server type.
-
Enter
https://mcp.gamentic.net/mcpin Server URL. -
Choose Static headers for Authentication.
-
Enter
Authorization:Bearer gi_your_key_herein Headers (KEY:VALUE, comma-separated). -
Choose Exit for What would you like to do?.
Edit the config file by hand
-
Open
~/.cline/data/settings/cline_mcp_settings.json(%USERPROFILE%\.cline\data\settings\cline_mcp_settings.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "type": "streamableHttp", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Cline CLI so it loads the new server.
OpenCode Uses a key
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update OpenCode to the latest version first.
-
Run this in a terminal:
bashopencode mcp add gamentic --url https://mcp.gamentic.net/mcp --header "Authorization=Bearer gi_your_key_here" -
If opencode --version shows 2.x, use the OpenCode 2 option instead.
-
Run
opencode mcp listand check that gamentic shows as connected.
OpenCode 2 (opencode --version shows 2.x)
-
Run this in a terminal:
bashopencode mcp add gamentic --global --url https://mcp.gamentic.net/mcp --header "Authorization=Bearer gi_your_key_here" -
Run
opencode mcp listand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.config/opencode/opencode.json(%USERPROFILE%\.config\opencode\opencode.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "$schema": "https://opencode.ai/config.json", "mcp": { "gamentic": { "type": "remote", "url": "https://mcp.gamentic.net/mcp", "oauth": false, "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart OpenCode so it loads the new server.
-
Run
opencode mcp listand check that gamentic shows as connected.
Amp Uses a key
Needs an Amp account. Enterprise workspaces can block servers that are not on their allowlist.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open
~/.config/amp/settings.json(%USERPROFILE%\.config\amp\settings.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "amp.mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Amp so it loads the new server.
Crush Uses a key
Needs Crush 0.88.0 or later; older versions only read crush.json.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Crush to the latest version first.
-
Open
~/.config/crush/crushrc(%USERPROFILE%\.config\crush\crushrcon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
bashmcp add gamentic --type http --url "https://mcp.gamentic.net/mcp" --header Authorization "Bearer gi_your_key_here" -
Restart Crush so it loads the new server.
-
Check that gamentic shows as connected in MCPs.
Legacy crush.json (older Crush versions)
-
Open
~/.config/crush/crush.json(%USERPROFILE%\.config\crush\crush.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "$schema": "https://charm.land/crush.json", "mcp": { "gamentic": { "type": "http", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Crush so it loads the new server.
Warp Uses a key
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open Settings → Agents → MCP servers.
-
Click + Add.
-
Paste this into the editor that opens, then save.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Click Start.
-
Check that gamentic shows as connected in Settings → Agents → MCP servers.
Edit the config file by hand
-
Open
~/.warp/.mcp.json(%USERPROFILE%\.warp\.mcp.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Check that gamentic shows as connected in Settings → Agents → MCP servers.
Cursor Uses a key
Use the latest Cursor; versions 3.5 and older may fail to connect with a key. MCP may need a paid plan.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Cursor to the latest version first.
-
Open
~/.cursor/mcp.json(%USERPROFILE%\.cursor\mcp.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Keep your key in this personal file only, never in a project's .cursor/mcp.json that you share with others.
-
Restart Cursor so it loads the new server.
-
Check that gamentic shows as connected in Customize → MCPs.
Cursor CLI (agent) only
-
Run this in a terminal:
bashagent update -
Open
~/.cursor/mcp.json(%USERPROFILE%\.cursor\mcp.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Run
agent mcp listand check that gamentic shows as connected.
Keep the key out of the file (environment variable)
-
Update Cursor to the latest version first.
-
Save your key in the environment variable
GAMENTIC_API_KEY(reopen your terminal and apps afterwards so they pick it up):macOS (zsh)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.zshrcLinux (bash)echo 'export GAMENTIC_API_KEY="gi_your_key_here"' >> ~/.bashrcWindows (PowerShell)setx GAMENTIC_API_KEY "gi_your_key_here" -
Open
~/.cursor/mcp.json(%USERPROFILE%\.cursor\mcp.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer ${env:GAMENTIC_API_KEY}" } } } } -
Restart Cursor so it loads the new server.
-
Check that gamentic shows as connected in Customize → MCPs.
VS Code Uses a key
Needs GitHub Copilot signed in. On Copilot Business/Enterprise an admin must turn on MCP servers in Copilot.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open View → Command Palette... → MCP: Open User Configuration.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "inputs": [ { "type": "promptString", "id": "gamentic_api_key", "description": "Gamentic API key", "password": true } ], "servers": { "gamentic": { "type": "http", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer ${input:gamentic_api_key}" } } } } -
Click Start, which appears just above gamentic in the file.
-
Enter
gi_your_key_herein Gamentic API key. -
Open View → Command Palette... → Chat: Open Chat.
-
Choose Local for Session Target.
-
Choose Agent for agent picker.
-
Check that gamentic shows as connected in View → Command Palette... → MCP: List Servers.
Command line (macOS / Linux)
-
On a Mac, if the code command is not found, first run Shell Command: Install 'code' command in PATH from the Command Palette.
-
Run this in a terminal:
bashcode --add-mcp '{"name":"gamentic","type":"http","url":"https://mcp.gamentic.net/mcp","headers":{"Authorization":"Bearer ${input:gamentic_api_key}"},"inputs":[{"type":"promptString","id":"gamentic_api_key","description":"Gamentic API key","password":true}]}' -
Open View → Command Palette... → Chat: Open Chat.
-
Choose Local for Session Target.
-
Choose Agent for agent picker.
-
Open View → Command Palette... → MCP: List Servers.
-
Click gamentic.
-
Click Start Server.
-
Click Trust.
-
Enter
gi_your_key_herein Gamentic API key.
Visual Studio Uses a key
Windows only: Visual Studio 2026, or Visual Studio 2022 17.14 with the latest update. Sign in with a GitHub account that has Copilot.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Visual Studio to the latest version first.
-
Open
%USERPROFILE%\.mcp.json(create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "servers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "requestInit": { "headers": { "Authorization": "Bearer gi_your_key_here" } } } } } -
Open View → GitHub Copilot Chat.
-
Choose Agent for mode.
-
Click Tools.
-
Choose gamentic for Tools.
Add it from the chat window
-
Open View → GitHub Copilot Chat.
-
Choose Agent for mode.
-
Click Tools.
-
Click +.
-
In Visual Studio 2022 the dialog opens right after you click +, so skip the next step.
-
Click Add custom MCP server.
-
Enter
gamenticin Server ID. -
Choose HTTP/SSE for Type.
-
Enter
https://mcp.gamentic.net/mcpin URL. -
Under Headers, add a header named Authorization.
-
Enter
Bearer gi_your_key_herein Authorization. -
Click Save.
-
Click Tools.
-
Choose gamentic for Tools.
JetBrains Uses a key
Junie and AI Assistant need a JetBrains AI license (trial, paid or AI Free); the Copilot plugin needs a Copilot plan.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open Settings → Tools → Junie → MCP Settings.
-
Click Add.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Check that gamentic shows as connected in Settings → Tools → Junie → MCP Settings.
AI Assistant chat
-
Open Settings → Tools → AI Assistant → Model Context Protocol (MCP).
-
Click Add.
-
Click HTTP.
-
Replace all the sample text in the box with this.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Choose Global for Server level.
-
Click OK.
-
Click Apply.
GitHub Copilot plugin
-
Open GitHub Copilot → Open Chat → Agent.
-
Click Configure your MCP server.
-
Click Add MCP Tools.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "servers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "requestInit": { "headers": { "Authorization": "Bearer gi_your_key_here" } } } } }
Devin Desktop (Windsurf) Uses a key
The Devin Local agent must be on. The one-line command needs Devin CLI; if it is not installed, use the config file option instead.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Run this in a terminal:
bashdevin mcp add -s user gamentic https://mcp.gamentic.net/mcp -H "Authorization: Bearer gi_your_key_here" -
Restart Devin Desktop so it loads the new server.
-
Run
/mcpand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.config/devin/mcp_config.json(%APPDATA%\devin\mcp_config.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Devin Desktop so it loads the new server.
Legacy Windsurf (Cascade)
-
Open Cascade → … → MCPs.
-
Click Open MCP config file.
-
Older Windsurf builds without this menu keep the file at ~/.codeium/windsurf/mcp_config.json.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "serverUrl": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Windsurf so it loads the new server.
-
Check that gamentic shows as connected in Cascade → … → MCPs.
Zed Uses a key
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open Settings → AI → MCP Servers.
-
Click Add Server.
-
Click Add Remote Server.
-
Replace all the sample text in the box with this.
json{ "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } -
Click Configure Server.
-
Check that gamentic shows as connected in Settings → AI → MCP Servers.
Edit the config file by hand
-
Open
~/.config/zed/settings.json(%APPDATA%\Zed\settings.jsonon Windows; create it if it does not exist). -
Keep your other settings, and put context_servers inside the file's outermost braces.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "context_servers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } }
Antigravity Uses a key
Works on every Antigravity plan, including free. The desktop app, the IDE and the Antigravity CLI share one config file.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Antigravity to the latest version first.
-
Open
~/.gemini/config/mcp_config.json(%USERPROFILE%\.gemini\config\mcp_config.jsonon Windows; create it if it does not exist). -
This is Antigravity's own file, not Gemini CLI's settings.json.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "serverUrl": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Antigravity so it loads the new server.
-
Check that gamentic shows as connected in Settings → Customizations → Installed MCP Servers.
Antigravity IDE: open the file from the MCP menu
-
Open … → MCP Servers → Manage MCP Servers → View raw config.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "serverUrl": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Restart Antigravity so it loads the new server.
-
Check that gamentic shows as connected in … → MCP Servers → Manage MCP Servers.
Cline Uses a key
Needs Cline 4.x. An enterprise admin can block personal remote MCP servers.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Cline to the latest version first.
-
Open Customize → MCP → Installed.
-
Click Edit Configuration.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "type": "streamableHttp", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Do not use the Add Remote Server form, because it has no field for your key.
-
Check that gamentic shows as connected in Customize → MCP → Installed.
-
If an Authenticate button appears next to gamentic, your key is wrong or missing; Cline cannot connect by signing in.
Edit the config file by hand
-
Open
~/.cline/data/settings/cline_mcp_settings.json(%USERPROFILE%\.cline\data\settings\cline_mcp_settings.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "type": "streamableHttp", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } }
Kilo Code Uses a key
Needs Kilo Code 7.x.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update Kilo Code to the latest version first.
-
Open Settings.
-
Click Global Config.
-
If a list of files appears, choose kilo.jsonc.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "$schema": "https://app.kilo.ai/config.json", "mcp": { "gamentic": { "type": "remote", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" }, "oauth": false, "enabled": true } } } -
Keep the oauth line set to false; Kilo Code cannot use Gamentic sign-in.
-
Restart VS Code / JetBrains so it loads the new server.
-
Check that gamentic shows as connected in Settings → Agent Behaviour → MCP Servers.
Kilo CLI
-
Run this in a terminal:
bashnpm install -g @kilocode/cli@latest -
Run this in a terminal:
bashkilo mcp add gamentic --url https://mcp.gamentic.net/mcp --header "Authorization=Bearer gi_your_key_here" -
Run
kilo mcp listand check that gamentic shows as connected.
Edit the config file by hand
-
Open
~/.config/kilo/kilo.jsonc(%USERPROFILE%\.config\kilo\kilo.jsoncon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "$schema": "https://app.kilo.ai/config.json", "mcp": { "gamentic": { "type": "remote", "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" }, "oauth": false, "enabled": true } } } -
Restart VS Code / JetBrains so it loads the new server.
Kiro Uses a key
Use the latest Kiro, with MCP support turned on in Settings.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open Command Palette → Kiro: Open user MCP config (JSON).
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
If gamentic does not appear, search Settings for MCP and turn MCP support on.
-
Check that gamentic shows as connected in Kiro → MCP Servers.
Kiro CLI
-
Open
~/.kiro/settings/mcp.json(%USERPROFILE%\.kiro\settings\mcp.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Run
/mcpand check that gamentic shows as connected.
TRAE Uses a key
TRAE passes at most 40 MCP tools to the model.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open Settings → MCP.
-
Click Add.
-
Click Add Manually.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Click Confirm.
-
In your agent's tool list, untick the Gamentic tools you don't need.
-
Check that gamentic shows as connected in Settings → MCP.
Mistral Le Chat Uses a key
Only admins can add custom connectors; on personal plans the account owner is the admin.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Open Context → Connectors.
-
Click + Add Connector.
-
Click Custom MCP Connector.
-
Enter
gamenticin Connector name. -
Enter
https://mcp.gamentic.net/mcpin Server URL. -
Choose API Token Authentication for Authentication method.
-
Mistral may preselect OAuth2.1, which cannot connect to Gamentic, so be sure to change it.
-
Enter
Authorizationin Header name. -
Choose Bearer for Header type.
-
Enter
gi_your_key_herein Header value. -
Choose Private for Visibility.
-
Click Create.
-
If gamentic under My Connectors asks for a Bearer token, enter your key and click Connect.
-
Check that gamentic shows as connected in Connectors → My Connectors.
The form has a single Default header field
-
Open Context → Connectors.
-
Click + Add Connector.
-
Click Custom MCP Connector.
-
Enter
gamenticin Connector name. -
Enter
https://mcp.gamentic.net/mcpin Server URL. -
Choose API Token Authentication for Authentication method.
-
Enter
Authorization: Bearer gi_your_key_herein Default header. -
Choose Private for Visibility.
-
Click Create.
goose Uses a key
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Extensions is in the sidebar; open it with the button in the top-left corner.
-
Open Extensions.
-
Click Add custom extension.
-
Enter
gamenticin Extension Name. -
Choose Streamable HTTP for Type.
-
Enter
https://mcp.gamentic.net/mcpin Endpoint. -
Enter
Authorizationin Header name. -
Enter
Bearer gi_your_key_herein Value. -
Click Add.
-
Click Add Extension.
-
Check that gamentic shows as connected in Extensions.
Edit the config file by hand
-
Open
~/.config/goose/config.yaml(%APPDATA%\Block\goose\config\config.yamlon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
yamlextensions: gamentic: enabled: true type: streamable_http name: gamentic uri: "https://mcp.gamentic.net/mcp" headers: Authorization: "Bearer gi_your_key_here" env_keys: [] envs: {} timeout: 300 -
Restart goose so it loads the new server.
LM Studio Uses a key
Needs LM Studio 0.3.17 or later.
Replace gi_your_key_here with a key you create under MCP keys on your account page.
-
Update LM Studio to the latest version first.
-
Program is a tab in the right-hand sidebar.
-
Open Program → Install → Edit mcp.json.
-
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Check that gamentic shows as connected in Program.
Edit the config file by hand
-
Open
~/.lmstudio/mcp.json(%USERPROFILE%\.lmstudio\mcp.jsonon Windows; create it if it does not exist). -
Add this and save the file. If it already lists other servers, add gamentic next to them.
json{ "mcpServers": { "gamentic": { "url": "https://mcp.gamentic.net/mcp", "headers": { "Authorization": "Bearer gi_your_key_here" } } } } -
Check that gamentic shows as connected in Program.
3. Check that it worked
Start a fresh conversation and ask for something read-only:
List my Gamentic games.
Your assistant should call list_games and come back with your library — an empty
list is a pass too, if the account is new. If instead you see an authentication error, work through
these in order:
| Symptom | Cause |
|---|---|
401, or a prompt to authenticate | The header is missing or malformed. It must read exactly Bearer gi_… — with the space, and with the gi_ prefix kept. |
| “MCP key required” | The server saw no usable key at all. Check the header name is Authorization. |
| No Gamentic tools offered | The client has not reloaded its config. Restart it, then confirm the server shows as connected in its MCP panel. |
| Tools appear, then stop mid-task | Normal reconnection. A server restart invalidates the session and clients re-initialize transparently; if it persists, restart the client. |
4. Fit your agent's modules
Before your first build, open gamentic.net/start. This is the Agent Lab: eleven modules you wire in or cut out, which change the instructions every connected AI receives. It takes effect immediately — the next build follows the new loadout.
| Module | Wire it in when… |
|---|---|
| New game questionnaire | You want a genre-aware form instead of being asked questions one at a time in chat. |
| Auto-feed gameplay templates | You want proven blueprints for known genres rather than mechanics invented from scratch. Leave this on. |
| Budget mode | You want to state a budget up front and be told what it buys before anything is spent. |
| Loop engineer | You want the agent to keep iterating toward a genuinely shippable game. Pair it with Budget mode. |
| Self-test before delivery | Always. The agent runs a playtest checklist before claiming it is done. |
| Self-learning | You want each build to record what it learned so later builds start better. |
| Unstable connection mode | Your connection drops. Games upload in resumable chunks instead of one long call. |
| Character design first | You want to approve concept art before any game code is written. |
| Image engine | You want sprites, backgrounds, CGs and covers. Off means no image generation at all. |
| Audio | You want sound effects, music and voice. Off means a silent game. |
5. Build something
Make me a bubble shooter. Cute pastel art, about 3000 credits of budget.
Tell me the plan before you spend anything.
A well-behaved run then goes roughly like this:
-
It reads the rules first
get_conventionandget_skillreturn the marker convention, the balance guidance and — for a known genre — a gameplay blueprint taken from a real shipped game. This is free and it is what stops the AI guessing at mechanics. -
It prices the work and asks
With Budget mode on, you see the scope and the subtotal before any credits move.
-
It builds shell-first
create_gamelands a smallgame.htmlshell, thenwrite_game_filefills in one file per character, scene and system. The real headless-browser test runs when the last file lands. -
It generates and wires the art
generate_asset,character_sprite,generate_sound,generate_music. The bytes go straight into your game; only names come back to the model. -
It hands you an editor link
https://gamentic.net/edit/<id>. From here the tuning is yours — see The Editor.
Your model tokens are not billed by Gamentic. You already pay your own provider for those. Gamentic credits pay only for generation on the platform, so a 3,000-credit budget converts almost entirely into art and audio — there is no thinking overhead to hold money back for.