A side-by-side look at the AI Brand Visibility Tracker and Momentic MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AI Brand Visibility Tracker for marketing work; choose Momentic for marketing. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | A AI Brand Visibility Tracker | M Momentic |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 37/100 · Fair | 41/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| 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 | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AI Brand Visibility Tracker | View Momentic |
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.
No confirmed install command for AI Brand Visibility Tracker yet — follow the setup steps linked from its listing page rather than a guessed package name.
No confirmed install command for Momentic yet — follow the setup steps linked from its listing page rather than a guessed package name.