⌕
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 July 2026): MCP protocol vulnerability — prompt injection via tool descriptions, no patch issued. NSA and CISA have now issued formal guidance. 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. The NSA and CISA have since issued formal security guidance on MCP. 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 spec finalizes July 28, 2026: The largest MCP revision since launch ships in days — stateless core, breaking changes. The 2026-07-28 MCP specification finalizes July 28 — the largest revision since the protocol launched. The core goes stateless: session IDs disappear from the wire, servers no longer need sticky sessions or shared session stores, and a plain round-robin load balancer is now sufficient. Also included: MCP Apps (server-rendered UIs), Tasks (long-running work), tighter OAuth/OpenID Connect authorization, and a 12-month deprecation clock that starts July 28 for older protocol versions. SSE transport is officially deprecated — Streamable HTTP is now the only standard. If you run an MCP server, check your GitHub repo for SDK beta updates before the deadline. Tier 1 SDKs (Python, TypeScript, Go) have already shipped beta support with backward compatibility preserved. Full details: MCP Blog · The Register
Showing 15 MCPs