NotFair GoogleAds vs PumpGTM MCP server
A side-by-side look at the NotFair GoogleAds and PumpGTM MCP server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose NotFair GoogleAds for marketing work over a hosted endpoint; choose PumpGTM MCP server for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose NotFair GoogleAds when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 70/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,040 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 34 |
| Full listing | View NotFair GoogleAds | View PumpGTM MCP server |
Tools & capabilities
NotFair GoogleAds tools
No tool names declared yet. Check the project README from the listing page.
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
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.
NotFair GoogleAds
{
"mcpServers": {
"notfair-googleads": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
}
PumpGTM MCP server
{
"mcpServers": {
"pumpgtm-mcp-server": {
"url": "https://mcp.pumpgtm.com/mcp"
}
}
}
Frequently asked questions
NotFair GoogleAds is categorized under Marketing and uses a remote HTTP/SSE transport. PumpGTM MCP server belongs to Marketing and uses a remote HTTP/SSE transport. Pick NotFair GoogleAds for marketing work and PumpGTM MCP server 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.
NotFair GoogleAds has no declared pricing — check the project's own site. Auth: oauth 2.0. PumpGTM MCP server 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 notfair-googleads and pumpgtm-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, NotFair GoogleAds has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 4,040 GitHub stars. PumpGTM MCP server has 70/100 (Great) with 3 views, 0 installs and 3 GitHub stars.