Blender MCP vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Blender MCP MCP Servers	MCP Everything Server MCP Servers
Tagline	Give Claude hands inside Blender — an MCP server for natural-language 3D modeling.	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open-source (MIT license). No hosted service, no subscription; you supply your own MCP-capable client (Claude Desktop, Cursor, VS Code, OpenCode) and pay only for whatever LLM the client uses.	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model	Model-agnostic; commonly paired with Claude (Sonnet/Opus) via Claude Desktop, but works with any MCP-capable client	—
Editorial score	—	—
Use cases	AI-assisted 3D scene blockingGenerative prop and mesh creation via Hyper3D RodinPoly Haven HDRI and texture stagingSketchfab asset search and importMaterial and lighting iteration by chatViewport screenshot review loopsBlender Python scripting via natural languageReference-image to 3D model workflowsRapid product render setup	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros	Extremely popular and actively maintained MCP server (25k+ GitHub stars) with a clear install path Real two-way integration: the LLM can inspect the scene, act, then look at a screenshot and iterate Bundled asset integrations (Poly Haven, Sketchfab, Hyper3D Rodin) let the agent pull in production-ready models and HDRIs Works with several major MCP clients (Claude Desktop, Cursor, VS Code, OpenCode), not locked to one vendor MIT-licensed and fully local — no cloud rendering, no telemetry, your .blend files never leave the machine The execute_blender_code tool is a genuine power-user escape hatch for anything the higher-level tools don't cover	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons	execute_blender_code runs arbitrary Python in your Blender session, which is a real security risk if you paste in untrusted prompts Requires a manual setup dance (install add-on, edit client JSON, run uvx server) that will trip up non-technical artists Quality depends entirely on the connected LLM — small or cheap models struggle to plan multi-step scene edits Complex operations often need to be broken into small steps or they silently fail or produce garbage geometry No GUI feedback inside the client beyond screenshots — long agent runs can drift from what the artist actually wanted Sketchfab/Hyper3D asset integrations depend on third-party accounts and API keys with their own quotas and terms	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Website	github.com	github.com

Pick Blender MCP if

✅ Extremely popular and actively maintained MCP server (25k+ GitHub stars) with a clear install path
✅ Real two-way integration: the LLM can inspect the scene, act, then look at a screenshot and iterate
✅ Bundled asset integrations (Poly Haven, Sketchfab, Hyper3D Rodin) let the agent pull in production-ready models and HDRIs
✅ Works with several major MCP clients (Claude Desktop, Cursor, VS Code, OpenCode), not locked to one vendor

Pick MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →