22 MCPs
🔌 What is an MCP?

A Model Context Protocol is a standardised bridge letting an AI model (like Claude) read and control external software such as a game engine, a 3D tool, or a GPU profiler, through a defined set of commands and data schemas.

🎮 Why does it matter for game dev?

Instead of copy-pasting code between your editor and a chat window, an MCP lets the AI directly modify your scene, generate shaders, query assets, or run physics sims, all without leaving your tool.

🔍 How to use this guide

Use the sidebar filters to narrow by engine, tool, status or complexity. Click any card to see full integration steps with one-click copy buttons, quality ratings, and community links.

🟢 What's covered

Game engines (Unity, Unreal, Godot, Roblox), 3D content tools (Blender, Maya, 3ds Max, Substance Painter, Quixel, Mixamo), and NVIDIA tools (Omniverse, RTX Remix, DLSS, PhysX, Nsight).

Security notice (Apr 16): MCP protocol vulnerability disclosed — prompt injection via tool descriptions. Ox Security researchers disclosed a design-level vulnerability in the MCP protocol affecting an estimated 200,000 servers and packages with 150M+ downloads. The attack vector is prompt injection through tool descriptions, enabling server takeover. Anthropic updated its guidance to treat STDIO-based MCP adapters with caution but declined to patch the protocol architecture. Practical steps: only install MCP servers from sources you trust, review what file system and network permissions each server requests, and prefer servers with active maintenance. Read the full disclosure: Ox Security · The Register
Showing 15 MCPs