Blender MCP vs Slack MCP Server

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

	Blender MCP MCP Servers	Slack MCP Server MCP Servers
Tagline	Give Claude hands inside Blender — an MCP server for natural-language 3D modeling.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
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 / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
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	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
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 reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
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	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
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 Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →