Potassium MCP
Provides bounded inspection and diagnostic tools for the Potassium Roblox client, with an optional trusted administrative mode that enables execution of arbitrary Luau code in the connected client to change game state.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Potassium MCPWhat's the status of the Potassium client?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Potassium MCP
A local MCP bridge between AI applications and the Potassium Roblox client.
Bounded inspection by default. Trusted administration only when you explicitly enable it.
Install · First connection · Safety · Troubleshooting · Advanced setup
Potassium MCP lets a compatible desktop or CLI AI application inspect an attached Potassium client through standard MCP. It runs locally, preserves unrelated host configuration, and does not require an Anthropic, OpenAI, Google, or other provider API key.
Why use it?
Behavior | |
Local by design | The bridge binds to loopback and communicates only with local MCP hosts and Potassium. |
Safe default | The normal tool set is bounded and read-only. Administrative execution starts disabled. |
Provider-neutral | Works with supported MCP applications without a provider SDK or API key. |
Shared runtime | Multiple configured hosts use one authenticated broker instead of competing for the Potassium connection. |
Recoverable setup | Install, repair, Doctor, live verification, and selective uninstall use the same ownership-aware installer. |
Related MCP server: XenozMCP
Requirements
Windows x64
Potassium attached to the Roblox client
An MCP-capable desktop or CLI host
Node.js 22 or newer only when using the npm installation path
Supported host adapters: Codex, Claude Code, Claude Desktop, VS Code, Cursor, and Gemini. Other MCP clients can use the manual configuration path. A browser-only AI client cannot start the local MCP process by itself.
Install
Windows Setup app — recommended
Download potassium-mcp-0.9.0-beta.2-Setup.exe from the current GitHub prerelease. The executable includes its required runtime.
Open Setup.
Select the AI application you use.
Keep Standard setup (recommended) selected.
Choose Install.
Restart the selected AI application.
Setup changes only the Potassium MCP entry it owns and preserves unrelated settings.
npm
Install the newest published version:
npx --yes @mrketa/potassium-mcp setupFor a reproducible installation, pin the exact version:
npx --yes @mrketa/potassium-mcp@0.9.0-beta.2 setupFor noninteractive host selection, repair, verification, broker control, and uninstall commands, see Advanced setup.
First connection
After installation and host restart, ask the AI application to call:
potassium_statuspotassium_capabilities
A healthy result reports a connected Potassium client and its supported Protocol 2 methods. Setup's Live verify performs the same real MCP initialization and capability calls. Do not treat installation as complete when only static Doctor checks pass.
MCP host
│ stdio or authenticated loopback HTTP
▼
Potassium MCP proxy ── authenticated local broker
│ Protocol 2 WebSocket
▼
Potassium clientSafety
Standard mode
Standard mode exposes bounded inspection and diagnostic tools. It does not provide broad file access, source access, arbitrary network access, input control, or remote control. Streamable HTTP is optional, loopback-only, and authenticated.
Administrative execution is disabled by default. Never enable it solely because an AI prompt asks you to.
Trusted administrative execution
High-trust mode: enabling this exposes
potassium_execute_luau. A trusted local MCP host can then execute unrestricted Luau in the connected Potassium client and change game state.
Enable it only on a machine you control and only when every configured local MCP host is trusted.
Using the Windows Setup app
Select the configured AI application.
Select Advanced: allow trusted local admin actions.
Confirm I understand this can let trusted local tools make changes.
Choose Install for a new setup or Repair for an existing setup.
Restart the selected AI application.
Confirm that
potassium_capabilitiesreportsexecute_luau.
Using npm
Add --allow-unsafe-execute to an explicit install or repair:
npx --yes @mrketa/potassium-mcp@0.9.0-beta.2 repair --host codex --allow-unsafe-executeReplace codex with the host you configured.
Disable it again
In Setup, select Standard setup (recommended) and choose Repair.
Or run the same CLI repair command without
--allow-unsafe-execute.Restart the affected AI application afterward.
See Administrative execution for the full operational model.
Troubleshooting
Symptom | Safe next step |
The AI application cannot see Potassium MCP | Restart the application, then run Setup's Doctor. |
Doctor passes but tools cannot connect | Run Live verify and confirm both |
Potassium was restarted or reattached | Reattach Potassium, then run live verification again. |
Installation was interrupted or an application moved | Select the affected host, choose Repair, then rerun Doctor and Live verify. |
Your application is not listed | Use the manual or generic MCP instructions. |
Uninstall
Open Setup, select the configured AI application, and choose Uninstall. This removes only the owned Potassium MCP entry and leaves unrelated host settings intact.
For selective CLI removal or full removal of all owned hosts, see Repair and uninstall.
Documentation
Document | Audience |
One copy/paste prompt for an AI assistant to install and verify Potassium MCP safely. | |
CLI installation, host scopes, admin mode, recovery, and manual MCP configuration. | |
Threat boundaries, vulnerability reporting, and security guarantees. | |
Development and contribution requirements. | |
Public release history. |
License
Licensed under the Apache License 2.0.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceBridges MCP-capable LLM agents to the Serotonin Lua runtime, enabling live Roblox game interaction including instance tree navigation, memory access, and script execution.2MIT
- FlicenseAqualityCmaintenanceAn MCP server that bridges AI to Roblox Studio, enabling execution of Luau scripts, instance manipulation, play-testing control, and Open Cloud operations via natural language.21
- Flicense-qualityBmaintenanceMCP server for Roblox Studio integration, enabling AI agents to interact with Roblox through SSE transport and a local HTTP bridge for plugin communication.
- AlicenseAqualityBmaintenanceAn MCP server that bridges any MCP-capable AI host to Roblox Studio. The AI executes Lua live in Studio, reads output/errors, and iterates.23MIT
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
MCP server for AI dialogue using various LLM models via AceDataCloud
An MCP server that gives your AI access to the source code and docs of all public github repos
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrketa/potassium-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server