Adds Storybook component and story documentation tools to an MCP server you run yourself.
Ue MCP
db-lyon · MCP server
Gives your AI assistant read and write access to the Unreal Editor. Through a C++ bridge plugin deployed into your project, it can place and move actors, author Blueprint graphs, create materials, work with animation, Niagara effects, landscape, foliage, audio, UI and gameplay systems, run the console and build the project. Reading INI settings, C++ headers and asset listings still works with the editor closed.
Written by ooruby from the README of ue-mcp 1.3.10.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can drive the Unreal Editor in plain English instead of you clicking through each panel and graph.
What you could do with it
- Ask your assistant to place a warm white point light 300 units above the player start.
- Create an emissive material that pulses and apply it to every cube in the level.
- Build the project in Development and have the compile errors reported back to you.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Unreal Engine MCP server - 26 tools, 1975+ actions for AI-driven editor control
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 1.3.10, the file with digest sha512-HTmFmkc+05tXMNtBrik6Y7hMz4SVA4DHdolZFPfVD5tSygNekWFwIPwGz+IyY81nXgO4q8XfiXLG3aGNsFvKCQ==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"ue-mcp": {
"command": "npx",
"args": [
"-y",
"-p",
"ue-mcp@1.3.10",
"ue-mcp"
]
}
}
}Or run it directly.
npx -y -p ue-mcp@1.3.10 ue-mcpPinned to 1.3.10, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- ue-mcp
- Version read
- 1.3.10
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/db-lyon/ue-mcp
- Commit
- 992854927ec2
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/ue-mcp)About this listing
- Kind
- MCP server
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-09
Similar MCP servers
All MCP serversLets your agent control and inspect a live Chrome browser using Chrome DevTools.
Pulls version-specific library docs and code examples straight into your agent's context.
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.