PumpGTM MCP server vs RankControl
A side-by-side look at the PumpGTM MCP server and RankControl MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PumpGTM MCP server for marketing work over a hosted endpoint; choose RankControl 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 PumpGTM MCP server when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You want tools like
get_cold_message_examples, get_company, get_lead_profile.
Choose RankControl when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 70/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Paid service | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 5 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 34 | Not listed |
| Full listing | View PumpGTM MCP server | View RankControl |
Tools & capabilities
PumpGTM MCP server tools 34
get_cold_message_examplesnoneget_companynoneget_lead_profilenoneget_pipelinenoneget_workspacenoneget_x_play_reviewnonelist_leadsnonelist_pending_repliesnonelist_sequencesnonelist_signal_eventsnonelist_signal_typesnonesearch_known_peoplenone- +22 more on the listing page
RankControl 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.
PumpGTM MCP server
{
"mcpServers": {
"pumpgtm-mcp-server": {
"url": "https://mcp.pumpgtm.com/mcp"
}
}
}
RankControl
{
"mcpServers": {
"rankcontrol": {
"command": "npx",
"args": [
"-y",
"rankcontrol"
]
}
}
}
Frequently asked questions
PumpGTM MCP server is categorized under Marketing and uses a remote HTTP/SSE transport. RankControl belongs to Marketing and uses a local stdio subprocess. Pick PumpGTM MCP server for marketing work and RankControl 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.
PumpGTM MCP server is listed as a paid service. Auth: oauth 2.0. RankControl is listed as a paid service. Auth: oauth 2.0. 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 pumpgtm-mcp-server and rankcontrol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PumpGTM MCP server has a quality signal of 70/100 (Great) with 3 views, 0 installs and 3 GitHub stars. RankControl has 56/100 (Good) with 3 views, 0 installs and 5 GitHub stars.