A side-by-side look at the Notch and SeaOtter Dispatch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Notch for multimedia process work over a hosted endpoint; choose SeaOtter Dispatch for developer tools. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | N Notch | S SeaOtter Dispatch |
|---|---|---|
| Category | Multimedia Process | Developer Tools |
| Quality signal | 45/100 · Fair | 12/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 26 views 12 installs 6 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Notch | View SeaOtter Dispatch |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"notch": {
"url": "https://app.usenotch.ai/mcp/setup"
}
}
}
No confirmed install command for SeaOtter Dispatch yet — follow the setup steps linked from its listing page rather than a guessed package name.
