AgentUX Editions

How AgentUX Connects to Claude

AgentUX runs as a local MCP server on your machine. Claude Code calls it through Anthropic's MCP protocol, the same way it calls any other MCP tool. AgentUX never makes API calls to Anthropic, never handles OAuth tokens, and never acts as a third-party API client. Your Claude Pro or Max plan allotment is consumed exactly as it would be for any other MCP-enabled workflow.

This is a deliberate design choice. MCP is the protocol Anthropic ships as the supported integration surface for tools that extend Claude. AgentUX was designed to work with your subscription rather than around it: the intent is to maximize what you get from a plan you already have, without introducing the policy risk that comes from API-proxying or OAuth-bypass approaches.

For organizations evaluating AgentUX: when subscription models or compliance posture change over time, AgentUX continues to work because the way it connects to Claude depends on the protocol Anthropic supports, not on us interpreting their terms for you.

A second design principle compounds this. Anything your AI accomplishes through AgentUX, you can capture as a Python script, a CLI command, or an editor hook. Once captured, that operation runs again at zero token cost forever. The methods are pure JSON-RPC, so successful AI sessions become reusable automation rather than one-shot interactions.

Feature Comparison

Why Pro

Free gives your AI full editor control: 662 methods, multi-source inventory, the Environment and creative toolkit, the Community script library, and the safety system. Pro gives your AI understanding of the engine across its entire history, the ability to learn from your mistakes session over session, and the build pipeline to index your own engine forks. Free customers run any script Pro customers or Team Studio customers publish, at zero token cost. Pro customers write and share those scripts -- the knowledge base, session memory, and build pipeline turn one studio's hard-won API fluency into a compounding library everyone benefits from.

Your AI knows every UE release

Pro indexes more than 16 million source nodes across all 27 UE5 versions, from 5.0.0 through 5.7.4 plus NvRTX. Porting a project from 5.4 to 5.7? Ask Claude what changed in the API you depend on. One call to get_version_diff shows exactly which functions were added, removed, or renamed between any two versions. No more digging through release notes or guessing whether your code will compile.

It learns from your mistakes

Pro includes an experience system that captures gotchas and non-obvious API behaviors as you work. Hit a silent failure because you used location instead of position on a camera? Pro records that. Next session, before you make the same mistake, your AI already knows the correct approach. The knowledge base accumulates session over session with tiered importance levels that protect critical discoveries from pruning.

Index your own engine

Running NvRTX? A custom studio fork with proprietary plugins? Pro includes the full Python build pipeline that scanned stock Unreal. Point it at your source tree, run rebuild.py, and your AI now understands your engine. DLSS frame generation parameters, your custom gameplay framework, internal subsystems that Claude has never seen in training data. All of it becomes queryable through the same 34 MCP tools.

Build scripts that others can run for free

Scripts you create with Pro work on the Community edition. Write a lighting rig automation, a material pipeline, a batch asset processor. Share it with your team, your community, or sell it. Community users install the free plugin, run your script, and it works. Every script you share puts AgentUX in front of new users. Your tooling becomes distribution.

Cross-project asset analytics, from local to graph

The Free Asset Inventory already gives every edition substantial cross-project visibility: scan multi-source projects (Fab + GameWalk + USD + Manual) into a shared local catalog, browse across projects in the Slate panel, rank assets by reuse with the Asset Usage Report, find every project that uses a given asset with one call, and migrate assets between projects with full hard-package dependency cascade. The cascade walker, the usage report, and the multi-source scan together deliver the everyday cross-project workflows: which assets are reused where, what does it take to move one of them, what's living in two places that shouldn't be.

Pro extends that foundation into a graph database. One call mirrors the local SQLite inventory into Neo4j as :InventoryAsset, :InventoryProject, and :InventoryCollection nodes with project membership and collection edges. The local editor.inventory.* surface answers focused questions one root at a time; Cypher answers shapes the JSON-RPC surface can't easily express, like multi-hop dependency walks across many roots simultaneously. Ask Claude in plain language: "show me every Texture used by a Material attached to a StaticMesh that's used in 3 or more of my projects, sorted by texture size." Claude translates that 3-hop walk into Cypher, runs it, and returns results in seconds. Or write Cypher directly for repeatable, deterministic searches in CI pipelines and shared studio tooling. Natural language for exploration. Query language for precision. Same data, two access modes, the second one available when the first one stops being enough.

Spawn a walkable showcase grid in the editor to browse matches visually. Full guide here.

Save and reuse Blueprint patterns

The Blueprint pattern store captures working node graphs and makes them searchable. Built a combat damage calculation? Save the pattern. Next project, search for "damage calculation" and get the exact node setup with connection details. Patterns survive across projects and accumulate into a personal library of proven implementations.

Full Python source

Pro ships with the complete Python source for the GraphRAG pipeline, MCP bridge, build scripts, parsers, and knowledge management tools. Read how the indexer works, modify the query tools, extend the MCP server with custom tools. All editions include SDK headers (Public/*.h) for writing custom C++ handlers that plug into the AgentUX router.

Team Studio

Team Studio is built for studios that need every developer working from the same engine knowledge, the same scripted automation library, and the same C++ extension surface. Pricing is $150 per seat with a 10-seat minimum, sold direct rather than through Fab or Gumroad.

Every seat gets everything in Pro. The team also gets full C++ source for the AgentUX plugin, so your engineers can extend handlers, fork the router, build studio-specific subsystems, and ship those extensions to the rest of the team. The Pro tier ships Python source for the GraphRAG pipeline; Team Studio adds the C++ that the plugin itself is built from.

AgentUX runs on UE 5.6 and 5.7 (662 methods on 5.7, 577 on 5.6). The Pro knowledge base covers all 27 UE5 versions, so your AI has accurate API data for whatever version you're building against. If your studio runs NvRTX, a custom engine fork, or has proprietary plugins, the included Python build scripts scan and index your codebase into the shared knowledge base; every developer queries the same indexed engine.

The infrastructure difference: Team Studio requires a retail Neo4j license (not Community Edition) for shared, multi-user knowledge base access. We help you stand it up.

Contact support@williamscloudtechnology.com for setup, onboarding, and an invoice.

Frequently Asked Questions

Does AgentUX use my Claude subscription?

Yes, and it works exactly like any other MCP tool in Claude Code. AgentUX runs as a local MCP server on your machine. Claude Code calls it through Anthropic's own MCP protocol. AgentUX never makes API calls to Anthropic, never handles OAuth tokens, and never acts as a third-party API client. Your Pro or Max plan allotment is consumed through Claude Code as normal. This is unaffected by Anthropic's restrictions on third-party tools that bypass Claude Code.

Can I upgrade from Free to Pro?

Yes. Buy Pro on Fab or Gumroad, download it, and run the installer. Your projects and existing work are untouched. Settings, workspace, and any scripts you've already collected continue to work.

Do I need Neo4j?

Not for Free. The local Asset Inventory and the entire editor-control surface work without any database. Pro uses Neo4j Community (free, open source) to host the engine knowledge graph; the installer walks you through it. Team Studio uses retail Neo4j for shared multi-user access.

Does the free edition run demo scripts?

Yes. All 15 demo scripts and the Community script library run on the Free edition. Free has access to all 45 handlers and 662 methods (gated only on the 9 plugin-dependent handlers, which require the corresponding UE plugin to be enabled). You can also run any script created by Pro or Team Studio users at zero token cost.

Can I extend AgentUX with custom handlers?

All editions include SDK headers (the public handler interface). You can write custom handlers that register with the AgentUX router, compile them against the SDK headers, and load them alongside the pre-compiled plugin DLL. The Pro Edition adds Python build scripts for indexing custom engine forks into the knowledge base.

Can I use AgentUX with a custom engine fork?

Yes, with the Pro edition. Pro includes Python build scripts that can scan and index any UE 5.x source tree. Point them at your NvRTX build, your studio's custom fork, or a tree with proprietary plugins, and they'll extract classes, functions, properties, and module structure into the knowledge base. Once indexed, all the MCP tools work against your codebase the same way they work against stock Unreal. If your team needs shared access, Team Studio makes the indexed knowledge base available to everyone.

Where to Buy

You can grab AgentUX on the Fab Marketplace or Gumroad. Community Edition is free on both.