NotFair GoogleAds vs Opinly
A side-by-side look at the NotFair GoogleAds and Opinly MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
O
OpinlyMarketing · Remote HTTP/SSESEO, competitor and AI-search data, plus blog management — draft, schedule and publish posts.37FairAuth: not declaredVerdict: choose NotFair GoogleAds for marketing work over a hosted endpoint; choose Opinly 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.
OChoose Opinly when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | O Opinly | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 49/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,046 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View NotFair GoogleAds | View Opinly |
Tools & capabilities
NotFair GoogleAds tools
No tool names declared yet. Check the project README from the listing page.
Opinly 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.
NotFair GoogleAds
{
"mcpServers": {
"notfair-googleads": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
}
Opinly
{
"mcpServers": {
"opinly": {
"url": "https://opinly.ai/mcp"
}
}
}
Frequently asked questions
NotFair GoogleAds is categorized under Marketing and uses a remote HTTP/SSE transport. Opinly belongs to Marketing and uses a remote HTTP/SSE transport. Pick NotFair GoogleAds for marketing work and Opinly 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. Opinly 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 notfair-googleads and opinly 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,046 GitHub stars. Opinly has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.