Unreal Engine function inspector MCP server

Created By
empvesa year ago
Unreal Engine function inspector MCP server
Overview

What is Unreal Engine Function Inspector MCP?

Unreal Engine Function Inspector MCP is a server designed to inspect functions within Unreal Engine, providing developers with tools to analyze and debug their projects effectively.

How to use Unreal Engine Function Inspector MCP?

To use the server, you need to set up your environment by installing Python 3.9+ and the uv package manager. After setting up, configure your API endpoint and key, and run the server using the provided commands.

Key features of Unreal Engine Function Inspector MCP?

  • Supports all platforms with modern Python (3.9+) and uv package manager.
  • Extensive testing with Claude Desktop App and compatibility with other MCP clients.
  • Provides a structured way to inspect and debug Unreal Engine functions.

Use cases of Unreal Engine Function Inspector MCP?

  1. Debugging Unreal Engine projects by inspecting function calls.
  2. Analyzing performance issues in game development.
  3. Assisting developers in understanding function interactions within their projects.

FAQ from Unreal Engine Function Inspector MCP?

  • What are the prerequisites to use this server?

You need an API endpoint and API key, along with Python 3.9+ and the uv package manager.

  • Is it compatible with all operating systems?

Yes, it supports all platforms where modern Python can run.

  • How do I deploy the server?

Follow the setup instructions to configure your environment and run the server using the specified commands.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
empves
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago