Enginy MCP vs NotFair
A side-by-side look at the Enginy MCP and NotFair MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Enginy MCP for marketing work; choose NotFair 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 when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | E Enginy MCP | |
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 37/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 4,046 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Enginy MCP | View NotFair |
Tools & capabilities
Enginy MCP tools
No tool names declared yet. Check the project README from the listing page.
NotFair 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.
Enginy MCP
No confirmed install command for Enginy MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
NotFair
{
"mcpServers": {
"notfair": {
"url": "https://notfair.co/api/mcp/notfair"
}
}
}