CrimsonEditorUtilities · Lesson 3 of 4
Connect Your AI Client
Before you start
- Completed: Enable Crimson MCP
Chapters
1. Generate the client config
In the editor console: ModelContextProtocol.GenerateClientConfig ClaudeCode — also accepts Cursor, VSCode, Gemini, Codex, or All. For Claude Code it writes .mcp.json into the project root; open your agent in that project and the editor server is available.
2. Verify
Ask your agent to call the `list_toolsets` meta-tool. You should see three Crimson entries; then prove the loop with a real call — ReadFile on Config/DefaultEngine.ini is a safe first request.
The three toolsets
| Toolset | Tools |
| CrimsonSourceToolset | ReadFile, ListFiles |
| CrimsonPluginToolset | ListPlugins, ValidateDependencies, ScaffoldPlugin |
| CrimsonAssetToolset | FindAssets, InspectAsset, CreateAsset, SetAssetProperty, FindTags |
Names come from reflection
Toolset and tool names derive from class and function names — confirm the live set with
list_toolsets / describe_toolset rather than assuming. ValidateDependencies audits Build.cs files against the suite's no-cross-dependency rule.