A side-by-side look at the Rank Tracker and Seo Audit Console MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Rank Tracker for marketing work over a hosted endpoint; choose Seo Audit Console for marketing as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Rank Tracker when
You need dedicated capabilities in the Marketing domain.
No tool names declared yet. Check the project README from the listing page.
Seo Audit Console 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.
Rank Tracker is categorized under Marketing and uses a remote HTTP/SSE transport. Seo Audit Console belongs to Marketing and uses a local stdio subprocess. Pick Rank Tracker for marketing work and Seo Audit Console for marketing.
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.
Rank Tracker has no declared pricing — check the project's own site. Seo Audit Console 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 rank-tracker and seo-audit-console as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Rank Tracker has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Seo Audit Console has 48/100 (Fair) with 1 views, 0 installs and 56 GitHub stars.