Blender MCP vs Postgres MCP Pro

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

	Blender MCP MCP Servers	Postgres MCP Pro MCP Servers
Tagline	Give Claude hands inside Blender — an MCP server for natural-language 3D modeling.	Open-source Postgres MCP server with deterministic health checks, index tuning, and safe SQL execution.
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 paid tiers.
Model	Model-agnostic; commonly paired with Claude (Sonnet/Opus) via Claude Desktop, but works with any MCP-capable client	Model-agnostic (works with any MCP-capable LLM); optional OpenAI models for experimental LLM-based index tuning
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	AI-assisted query optimization in Cursor or Claude DesktopAutomated index recommendations for slow workloadsEXPLAIN plan review with hypothetical indexesProduction database health monitoring via LLM chatDetecting bloated, duplicate, or unused indexesVacuum and transaction-id wraparound risk auditsSafe read-only SQL exploration by AI agentsSchema introspection for LLM SQL generationShared team Postgres MCP endpoint over SSE
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	Deterministic index tuning based on the Anytime Algorithm plus hypopg what-if simulation, not LLM guesswork Comprehensive PgHero-derived health checks covering bloat, cache, connections, vacuum, replication, and sequences Restricted mode enforces read-only transactions and blocks COMMIT/ROLLBACK escapes via pglast SQL parsing Works with any MCP client (Claude Desktop, Cursor, Windsurf, Cline, Goose, Qodo Gen) and supports both stdio and SSE transports MIT-licensed and free; installs via Docker, pipx, uvx, or uv with clear per-client config recipes Cost-benefit index selection along the Pareto front with configurable performance-vs-storage threshold Actively maintained by Crystal DBA with Discord community and public roadmap on GitHub
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	Postgres-only; no MySQL, SQL Server, or other database support Full-featured tuning requires pg_stat_statements and hypopg extensions, which self-managed installs may need to install manually Only two coarse access modes (unrestricted vs restricted) with no per-table or column-level ACLs Credentials are supplied at startup via DATABASE_URI, so switching databases means restarting the server Experimental LLM-based index tuning requires an OpenAI API key and adds external cost/latency Workload compression is basic (query normalization, equal weighting), which can misrank importance in complex workloads
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 Postgres MCP Pro if

✅ Deterministic index tuning based on the Anytime Algorithm plus hypopg what-if simulation, not LLM guesswork
✅ Comprehensive PgHero-derived health checks covering bloat, cache, connections, vacuum, replication, and sequences
✅ Restricted mode enforces read-only transactions and blocks COMMIT/ROLLBACK escapes via pglast SQL parsing
✅ Works with any MCP client (Claude Desktop, Cursor, Windsurf, Cline, Goose, Qodo Gen) and supports both stdio and SSE transports

Compare a different pair →