CrimsonEditorUtilities · Lesson 2 of 4

Enable Crimson MCP

Beginner3 minSetupTooling

Before you start

  • Completed: What Lives Here
  • CrimsonEditorUtilities enabled in Edit → Plugins
Video coming soon

Chapters

1. Flip the master switch

Project Settings → Crimson → Crimson MCP → Enable Crimson MCP. It's off by default — Crimson never exposes editor tooling to agents unless you opt in. The MCP toolbar button's menu can flip the same switch.

Project Settings → Crimson MCP → Enable Crimson MCP, then restart the editor.
Restart required
The flag is read once at module startup — the toolsets register during the next editor launch. Flipping the switch without restarting looks enabled but registers nothing.

2. Start the MCP server

Editor Preferences → Model Context Protocol → Auto Start Server (or run ModelContextProtocol.StartServer in the console). The server binds to http://127.0.0.1:8000/mcp and the Output Log prints the bind address — raise detail with Log LogModelContextProtocol Verbose.

Loopback only — keep it that way
The server has no authentication and binds to the local machine only. Never forward or expose the port to a network.

Resources