Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Track Unreal-version and editor-tool compatibility as the expansion grows
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Extending Unreal Engine 5.8 native MCP with deeper editor toolsets
What we know
Unreal Engine plugin that expands the engine's built-in MCP server with terrain, audio, animation, Niagara, UMG, gameplay and profiling toolsets.
Maintenance / activity evidence
- Observed (UTC)Merge pull request 638 from kevinpbuckley/5-8
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Broad Unreal Editor project authority. Writes: Modify project assets; Terrain/animation/FX/UI changes.
- Inherited from Unreal native MCP; optional terrain API key.
- Sensitive access: Unreal project assets
- The expansion can make broad editor/project changes through Unreal's native MCP endpoint.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
702 repository stars
Stars observed Sep 25, 2026.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.
All limitations / Review context
Which Unreal Engine versions and editor operations are currently supported?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- The expansion can make broad editor/project changes through Unreal's native MCP endpoint.
- Broad Unreal Editor project authority.
- Inherited from Unreal native MCP; optional terrain API key.
- Project/editor assets are processed locally; terrain tools may call an external service.
- Reviewed write actions: Modify project assets; Terrain/animation/FX/UI changes
- Sensitive access: Unreal project assets
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- Requires Unreal Engine 5.8+ native MCP and Editor Tools first.
- Real-world terrain tools use a free API key.
Original activity observations
- 2026-10-01T21:27:28Z: Merge pull request 638 from kevinpbuckley/5-8
Technical identity
github.com/kevinpbuckley/vibeue- Exact implementation source
- https://github.com/kevinpbuckley/vibeue ↗
- Reviewed resource type
- Framework
- Repository identity
- kevinpbuckley/vibeue
- Service endpoint
- http://127.0.0.1:8000/mcp
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
kevinpbuckley/vibeue
Recorded repository material and project history.
Includes references whose attribution is not established.
Setup · Watchlist
Framework setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsVibeUE is an Unreal Engine 5.8+ plugin layered on Unreal native MCP; it is not a standalone MCP server.
Unreal Editor → Plugins → install/enable VibeUE according to its repository installation guide; configure Unreal native MCP extension/endpoint. No standalone npm server.
Configure / authenticate
Publisher instructionsVibeUE exposes MCP from the Unreal Editor plugin at local /mcp, not a separately installed daemon. Follow Unreal plugin setup, generate client config, and acquire publisher key where required.
Check connection
Suggested checkCheck locally published MCP endpoint and discover tools without editing project assets.
Remove / uninstall / revoke
Suggested checkIn Unreal Editor Plugins disable VibeUE and restart the editor; remove any agent-side generated MCP entry from host settings. Project plugin files are separate from editor integration.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
What it does
Unreal Engine plugin that expands the engine's built-in MCP server with terrain, audio, animation, Niagara, UMG, gameplay and profiling toolsets.
- Capability
- Developer Tools
- Resource type
- Framework
- Industry
- Sports & Entertainment
- Best fit
- Extending Unreal Engine 5.8 native MCP with deeper editor toolsets
Representative uses
- Edit landscapes/foliage
- Author audio/animation/FX/UI
- Inspect performance
- Drive editor services through native Unreal MCP
Limitations
- Requires Unreal Engine 5.8+ native MCP and Editor Tools first.
- Real-world terrain tools use a free API key.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Inherited from Unreal native MCP; optional terrain API key.
- Permissions
- Broad Unreal Editor project authority.
- Data handling
- Project/editor assets are processed locally; terrain tools may call an external service.
- Cost
- free
- Risk and cautions
- The expansion can make broad editor/project changes through Unreal's native MCP endpoint.
Access scope and cautions
- Write actions
- Modify project assets Terrain/animation/FX/UI changes
- Sensitive access
- Unreal project assets
- Risk level
- high
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What setup and authentication are documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
Kevin Buckley is listed as Community implementation in MCP100’s current evidence.