Magic Insights vs Atlas
A side-by-side look at the Magic Insights and Atlas MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic Insights for developer tools work over a hosted endpoint; choose Atlas for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Magic Insights when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_workspace, list_studies, get_study.
Choose Atlas when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| 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 | 2 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 13 | Not listed |
| Full listing | View Magic Insights | View Atlas |
Tools & capabilities
Magic Insights tools 13
get_workspaceOne-call overview: plan, study count, connected platforms, tags, total feedback, date range, overall sentiment.list_studiesList all studies with description and date range.get_studyA study's summary, generated report, and top themes (with sentiment, ids, and example feedback).list_topicsA study's topics and the themes grouped under each.get_theme_feedbackAll feedback under one theme, most relevant first.list_suggestionsA study's AI-synthesized recommended actions (problem, solution, priority).get_suggestion_feedbackThe individual feedback behind a single suggestion.search_feedbackSearch and filter feedback by keyword, sentiment, platform, tag, or date range.get_feedbackOne feedback item in full — content, translation, AI summary, and source metadata.get_statsAggregate stats: total count, sentiment breakdown, date range.get_trendsFeedback volume and sentiment over time, bucketed by week or month.list_tagsThe workspace's custom tags and how many items carry each.- +1 more on the listing page
Atlas 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.
Magic Insights
{
"mcpServers": {
"magic-insights": {
"url": "https://app.magicinsights.ai/api/mcp"
}
}
}
Atlas
{
"mcpServers": {
"atlas-2": {
"command": "bunx",
"args": [
"@useatlas/mcp"
]
}
}
}
Frequently asked questions
Magic Insights is categorized under Developer Tools and uses a remote HTTP/SSE transport. Atlas belongs to Developer Tools and uses a local stdio subprocess. Pick Magic Insights for developer tools work and Atlas for developer tools.
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.
Magic Insights has no declared pricing — check the project's own site. Atlas 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 magic-insights and atlas-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic Insights has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Atlas has 43/100 (Fair) with 3 views, 0 installs and 1 GitHub stars.