Blender MCP vs Sentry MCP

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

	Blender MCP MCP Servers	Sentry MCP MCP Servers
Tagline	Give Claude hands inside Blender — an MCP server for natural-language 3D modeling.	Official Sentry MCP server: give Claude Code, Cursor, and other AI agents real access to your errors, traces, and triage.
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.	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month
Model	Model-agnostic; commonly paired with Claude (Sonnet/Opus) via Claude Desktop, but works with any MCP-capable client	Bring-your-own LLM (OpenAI, Anthropic, Azure OpenAI, or OpenRouter) for natural-language search skills; agent-side model is whatever your MCP client runs.
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	Debug production error from IDE agentRoot-cause a latency regression via trace lookupTriage new issues (assign, resolve, comment) from chatCorrelate a failing test with recent Sentry eventsNatural-language search across eventsPost-deploy error-rate investigationPull stack trace and open the offending file for a fixSummarize top issues for a standupQuery self-hosted Sentry from an internal coding agent
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	Official first-party server from Sentry — kept in step with API changes, not a community wrapper Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx Works with self-hosted Sentry, not only sentry.io One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector Fine-grained skill toggles let you scope which tools the agent can call Covers the full debugging loop: issues, events, traces, search, and triage actions like assign/resolve/comment Open source, so the tool surface and prompts can be audited or extended
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	You still need a paid Sentry plan to get useful volumes of events, retention, and org seats Natural-language search tools require you to bring your own OpenAI/Anthropic/Azure/OpenRouter key — extra cost and setup Value collapses if your team is not already invested in Sentry as its error/APM backend Remote server is single-tenant per token — sharing across a team means each engineer wires their own auth MCP itself is still young; some clients handle remote servers with headers imperfectly and stdio is often the fallback Read/write tools mean a misbehaving agent can resolve or reassign real issues — human-in-the-loop is not optional
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 Sentry MCP if

✅ Official first-party server from Sentry — kept in step with API changes, not a community wrapper
✅ Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx
✅ Works with self-hosted Sentry, not only sentry.io
✅ One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector

Compare a different pair →