Scenario for Blender vs Notch
A side-by-side look at the Scenario for Blender and Notch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Scenario for BlenderMultimedia ProcessBlender 5.0+ extension for Scenario AI images, video, 3D and PBR materials, with a local MCP server for agents.43FairAuth: api key requiredN
NotchMultimedia Process · Remote HTTP/SSETurn product pages and creative briefs into finished video and image ads from your AI chat.20EmergingAuth: not declaredVerdict: choose Scenario for Blender for multimedia process work; choose Notch for multimedia process over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Scenario for Blender when
- You need dedicated capabilities in the Multimedia Process domain.
- Its auth model fits you: API key required.
NChoose Notch when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Scenario for Blender | N Notch |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 43/100 · Fair | 20/100 · Emerging |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 562 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 29 views 12 installs 6 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Scenario for Blender | View Notch |
Tools & capabilities
Scenario for Blender tools
No tool names declared yet. Check the project README from the listing page.
Notch tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Scenario for Blender
No confirmed install command for Scenario for Blender yet — follow the setup steps linked from its listing page rather than a guessed package name.
Notch
{
"mcpServers": {
"notch": {
"url": "https://app.usenotch.ai/mcp/setup"
}
}
}
Frequently asked questions
Scenario for Blender is categorized under Multimedia Process and uses an install path we have not confirmed yet. Notch belongs to Multimedia Process and uses a remote HTTP/SSE transport. Pick Scenario for Blender for multimedia process work and Notch for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Scenario for Blender has no confirmed install command yet — follow its own setup instructions.
Scenario for Blender is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Notch has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add blender-plugin and notch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Scenario for Blender has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 562 GitHub stars. Notch has 20/100 (Emerging) with 29 views, 12 installs and 0 GitHub stars.