Humanify MCP vs NotFair GoogleAds
A side-by-side look at the Humanify MCP and NotFair GoogleAds MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Humanify MCP for marketing work as a local process; choose NotFair GoogleAds 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 Humanify MCP when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HUMANIFY_API_KEY. - You want tools like
humanify_transform.
Choose NotFair GoogleAds when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 52/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | HUMANIFY_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3,959 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Humanify MCP | View NotFair GoogleAds |
Tools & capabilities
Humanify MCP tools 1
humanify_transformTransform AI-generated marketing copy into human-sounding, GEO-optimised content that gets cited by AI search engines. Returns transformed copy, a human-readability score (0-100), and a list of improvements made.
NotFair GoogleAds 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.
Humanify MCP
{
"mcpServers": {
"humanify-mcp": {
"command": "npx",
"args": [
"-y",
"@morebetterclaw/humanify-mcp"
],
"env": {
"HUMANIFY_API_KEY": "YOUR_HUMANIFY_API_KEY_HERE"
}
}
}
}
NotFair GoogleAds
{
"mcpServers": {
"notfair-googleads": {
"command": "npx",
"args": [
"-y",
"notfair@latest"
]
}
}
}
Frequently asked questions
Humanify MCP is categorized under Marketing and uses a local stdio subprocess. NotFair GoogleAds belongs to Marketing and uses a local stdio subprocess. Pick Humanify MCP for marketing work and NotFair GoogleAds 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.
Humanify MCP has no declared pricing — check the project's own site. NotFair GoogleAds 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 humanify-mcp and notfair-googleads as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Humanify MCP has a quality signal of 52/100 (Good) with 2 views, 0 installs and 0 GitHub stars. NotFair GoogleAds has 51/100 (Good) with 1 views, 0 installs and 3,959 GitHub stars.