⌕
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 (unresolved as of June 2026): MCP protocol vulnerability — prompt injection via tool descriptions, no patch issued. Ox Security 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 — this remains unresolved. Note: the July 28 spec update addresses authorization hardening separately and does not fix this issue. 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. Full disclosure: Ox Security · The Register
Protocol update (July 28, 2026): MCP spec RC published May 21 — stateless core, breaking changes shipping July 28. The MCP 2026-07-28 release candidate is the largest protocol revision since launch. Key changes: stateless core (servers no longer need sticky sessions or shared session stores), Extensions framework (MCP Apps for server-rendered UIs, Tasks for long-running work), OAuth/OpenID Connect authorization hardening, and a formal deprecation policy. SSE transport is officially deprecated — Streamable HTTP is now the only standard. Breaking changes are included — server maintainers need to update before July 28. Check your MCP server's GitHub for compatibility updates. Full details: MCP Blog
Showing 15 MCPs