Enginy MCP vs Openaffiliate MCP

A side-by-side look at the Enginy MCP and Openaffiliate MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

E
Enginy MCPMarketing
B2B prospecting from your Enginy workspace: find, enrich, and reach contacts and companies.37FairAuth: not declared
Openaffiliate MCP logoOpenaffiliate MCPMarketing · Local subprocess (stdio)Search and discover affiliate programs with agent-ready data and commission details.65GreatAuth: no auth required

Verdict: choose Enginy MCP for marketing work; choose Openaffiliate MCP for marketing as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

E
Choose Enginy MCP when

  • You need dedicated capabilities in the Marketing domain.
Explore Enginy MCP

Openaffiliate MCP logoChoose Openaffiliate MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_programs, get_program, list_categories.
Explore Openaffiliate MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
E
Enginy MCP
Openaffiliate MCP logoOpenaffiliate MCP
CategoryMarketingMarketing
Quality signal37/100 · Fair65/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—118
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed3

Tools & capabilities

Enginy MCP tools

No tool names declared yet. Check the project README from the listing page.

Openaffiliate MCP tools 3

  • search_programsSearch affiliate programs by keyword, category, or commission type
  • get_programGet full details of an affiliate program including agent instructions, commission terms, restrictions, and signup info
  • list_categoriesList all affiliate program categories with the number of programs in each

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.

Openaffiliate MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openaffiliate-mcp": {
      "command": "npx",
      "args": [
        "openaffiliate-mcp"
      ]
    }
  }
}

Frequently asked questions

Enginy MCP is categorized under Marketing and uses an install path we have not confirmed yet. Openaffiliate MCP belongs to Marketing and uses a local stdio subprocess. Pick Enginy MCP for marketing work and Openaffiliate MCP 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. Enginy MCP has no confirmed install command yet — follow its own setup instructions.

Enginy MCP has no declared pricing — check the project's own site. Openaffiliate MCP is listed as free. Auth: no auth required. 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 mcp-12 and openaffiliate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Enginy MCP has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Openaffiliate MCP has 65/100 (Great) with 2 views, 0 installs and 118 GitHub stars.