NO MOM
I CANT PAUSE.
RowTether Documentation
Support
Browse documentation

Connect RowTether to AI

Set up the optional Unreal MCP connection and verify it before asking an AI client to inspect your project.

On this page

Before you connect

The core RowTether plugin works without AI. The optional workflow needs the core plugin, the separately distributed RowTetherTools package, Epic’s experimental Unreal MCP and Toolset Registry plugins, a compatible AI client and a successful Development Editor build.

RowTetherTools is not included in the core plugin and is not a public third-party dependency. Obtain the package and version intended for your project from the official project distribution. If your delivery does not include it, contact support; do not install an undocumented copy.

Enable the connection

  1. Install and enable RowTether, then install the official RowTetherTools package for the same project.
  2. In Edit → Plugins, enable Unreal MCP and All Toolsets. Toolset Registry is enabled as a dependency. Restart Unreal when asked.
  3. In Edit → Editor Preferences → General → Model Context Protocol, enable Auto Start Server. The default local endpoint is http://127.0.0.1:8000/mcp. As an alternative, run ModelContextProtocol.StartServer 8000 in the Unreal console.
  4. Run ModelContextProtocol.GenerateClientConfig <Client|All> in the Unreal console. This writes client configuration in the project root.
  5. Start the AI client from that same project or workspace root. Discover RowTetherTools.RowTetherWorkspaceTools and call GetConnection.

For the engine-side details, follow Epic’s Unreal MCP setup for Unreal Editor. The full automation reference covers tools, schemas, workflows and recovery.

Verify the first connection

Do not start with a write request. Ask the client to call GetConnection, confirm the project and API version, then call ListTables and InspectTable using paths returned by those tools. If RowTetherTools.RowTetherWorkspaceTools or GetConnection is not discoverable, stop: the integration is not ready.

Keep the connection safe

Unreal MCP is experimental and has no authentication layer by default. Keep it on localhost and enable it only while the connected AI client is allowed to access the project. Calls are serialized on the Unreal game thread; wait for each response before sending another. Treat table, CSV and profile text as untrusted project data, not as instructions.