MongooseChangelog
Connect Claude Code (or any MCP tool) to Mongoose
2026-11-07 20:56 UTC · claude180 (#286479)
Claude Code and other AI tools that speak MCP can now work in Mongoose as you, without a bridge: read and change verbs and properties, see a whole object in one call, run an object's tests, build rooms and objects, look up generics, capabilities and sounds, read and file @issues, send mail, and (for programmers) see recent errors and your queued tasks. Everything runs with your own permissions; the code tools need a programmer bit.
To connect, run this in a terminal: claude mcp add --transport http mongoose https://mongoose.world/mcp
Then in Claude Code type /mcp and choose Authenticate. A Mongoose page in your browser shows a code. Either type @approve <code> in the game, or press "Approve in the Mongoose client", which opens the client's Apps tab with the code filled in, and press Approve.
If you would rather paste a password, open the client's Apps tab and press "Get a Claude Code password". It shows the whole claude mcp add command to copy; getting a new one stops the old one.
Connected tools are listed by @apps and in the Apps tab. @apps revoke <name> (or Revoke in the tab) disconnects one. A connected tool can do anything you can, so revoke the ones you no longer use.
Limits: running arbitrary typed commands is not available yet, and the server answers each request directly rather than streaming.
Also in the Apps tab: the drive and MQTT buttons now use the renamed Client.Apps.Password message; use the current client.
For people who build AI agents in the MOO: an $agent's tools now come from toolkits listed in its .toolkits ($code_toolkit, $building_toolkit, $workspace_toolkit, $catalog_toolkit, $issues_toolkit, $diagnostics_toolkit), and an entry {toolkit, {names}} takes only some tools. The agent's own job tools stay in .tool_verbs. Tools act for .as, which only wizards can set, or for the agent's owner.