A side-by-side look at the Hitkeep and Beamtrace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hitkeep for marketing work; choose Beamtrace MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
get_visibility, list_topics, list_prompts.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 93 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Hitkeep | View Beamtrace MCP |
No tool names declared yet. Check the project README from the listing page.
get_visibilityOverall visibility score and insightlist_topicsTopic rollupslist_promptsPrompt-level metrics and coverage gapslist_competitorsVisibility leaderboardlist_improvementsPrioritized content improvementsPaste 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.
No confirmed install command for Hitkeep yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"elfsight-beamtrace-mcp": {
"url": "https://beamtrace.com/api/mcp"
}
}
}