monolith MCP Server
tumourlove/monolith
[](https://agentrank-ai.com/tool/tumourlove--monolith/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge) MCP plugin for Unreal Engine 5.7 & 5.8 — gives AI assistants full read/write access to Blueprints, Materials, Niagara, Animation, Mesh, AI, GAS, Logic Driver, ComboGraph, UI, Audio, plus Reflection Intelligence (decision / risk / C++ reflection / replication queries). 1,400+ actions across 25+ namespaces. Native C++, zero Python dependency.
claude mcp add agentrank -- npx -y agentrank-mcp-server Overview
tumourlove/monolith is a C++ tool licensed under MIT. MCP plugin for Unreal Engine 5.7 & 5.8 — gives AI assistants full read/write access to Blueprints, Materials, Niagara, Animation, Mesh, AI, GAS, Logic Driver, ComboGraph, UI, Audio, plus Reflection Intelligence (decision / risk / C++ reflection / replication queries). 1,400+ actions across 25+ namespaces. Native C++, zero Python dependency. Topics: ai, ai-tools, animation, blueprint, claude, claude-code, cursor, material-editor, mcp, model-context-protocol, niagara, ue5-plugin, unreal-engine, unreal-engine-5, unreal-engine-plugin, vfx, gameplay-ability-system, mesh, procedural-generation, audio.
Ranked #2257 out of 24846 indexed tools.
In the top 10% of all indexed tools.
Has 14 contributors.
Ecosystem
Score Breakdown
330 stars → growing community
Last commit 1mo ago → moderate activity
56/74 issues closed → decent issue management
14 contributors → active community
No dependents → no downstream usage
Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →
How to Improve
Matched Queries
From the README
# Monolith
**One plugin. Every Unreal domain. Zero dependencies.**
---
## Why I built this
Most MCP integrations for Unreal register every action as a separate tool. That floods the AI's context window with hundreds of tool names before you've asked a single question — and the actually useful stuff gets buried. I built Monolith because I wanted my AI to spend its context on my problem, not on memorising a tool catalogue.
One plugin. One MCP endpoint. A handful of namespace-dispatch tools instead of ~1,400+. The AI calls `monolith_discover()` and `monolith_guide()` when it needs to know what's available, and otherwise just hits `blueprint_query("create_blueprint", ...)`, `material_query("compile", ...)`, and so on. `monolith_discover()` is terse by default — each action returns just a name and a one-line description, so listing a namespace costs almost nothing; the full param schema is one `describe_query("action_schema", ...)` call (or `detail=true`) away when the AI actually need Read full README on GitHub → Get the weekly AgentRank digest
Top movers, new tools, ecosystem insights — straight to your inbox.