Openaffiliate MCP

What openaffiliate-mcp does

openaffiliate-mcp gives MCP-compatible AI clients access to the OpenAffiliate registry, an open collection of affiliate program records maintained by Affitor. It is intended for developers and agents that need to discover programs, compare their terms, or recommend programs based on a user’s requirements.

The registry stores program information in structured records. A returned program can include commission details, cookie duration, payout terms, approval requirements, restrictions, signup information, and instructions for agents. When a program has been scored, its details also include the OpenAffiliate Score, grade, and report link.

How it works

The server supports two connection methods:

• A hosted MCP endpoint at https://openaffiliate.dev/mcp for remote clients. https://openaffiliate.dev/api/mcp provides the same tools for clients using the earlier path.
• A local stdio process launched with npx openaffiliate-mcp, which is useful when tools should run locally or when a project needs to pin a package version.

The hosted endpoint is public and does not require an API key. Its read operations query the OpenAffiliate registry. Program submissions are handled as a review-queue operation rather than an immediate listing; a submitted program must be verified before it is published.

Setup and configuration

For a remote MCP client, add the hosted endpoint as an HTTP MCP server:

{
  "mcpServers": {
    "openaffiliate": {
      "url": "https://openaffiliate.dev/mcp"
    }
  }
}

For local stdio access, configure the client to run:

{
  "mcpServers": {
    "openaffiliate": {
      "command": "npx",
      "args": ["openaffiliate-mcp"]
    }
  }
}

No environment variables or authentication keys are required for the hosted read-only access described by the project.

Tools and capabilities

The primary read-only tools are:

• search_programs searches by keyword, category, or commission type. The registry also supports filtering by minimum commission and verification status through its broader search functionality.
• get_program retrieves a complete record for a selected program, including agent instructions, commission terms, restrictions, signup information, and available OAS data.
• list_categories returns the available affiliate-program categories and the number of programs in each.

The MCP interface also provides submit_program and get_submission_status. These tools let an agent queue a missing program for review and check the resulting submission status. They do not publish a program instantly.

Limitations and notes

OpenAffiliate data reflects registry records and verification work, so terms should be checked against the relevant brand’s current program page before making a business decision. A submission enters a review queue and is not listed or scored until maintainers verify it. The server is designed for discovery and structured research; it does not enroll a user in an affiliate program or complete signup on the user’s behalf.

The hosted MCP service is read-only for ordinary discovery operations. Submission operations are the exception, but they only queue a program for verification. The project also exposes the registry through a CLI, REST API, SDK, and markdown pages, although those interfaces are separate from the MCP connection.