Brandsystem MCP — Build vs Openaffiliate MCP

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

Brandsystem MCP — Build logoBrandsystem MCP — BuildMarketing · Local subprocess (stdio)Build portable .brand runtimes from websites, Figma, and PDFs for use across AI tools.59GoodAuth: not declaredOpenaffiliate MCP logoOpenaffiliate MCPMarketing · Local subprocess (stdio)Search and discover affiliate programs with agent-ready data and commission details.65GreatAuth: no auth required

Verdict: choose Brandsystem MCP — Build for marketing work as a local process; 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?

Brandsystem MCP — Build logoChoose Brandsystem MCP — Build when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like brand_start, brand_status, brand_extract_web.
Explore Brandsystem MCP — Build

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.

SpecBrandsystem MCP — Build logoBrandsystem MCP — BuildOpenaffiliate MCP logoOpenaffiliate MCP
CategoryMarketingMarketing
Quality signal59/100 · Good65/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars15118
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools343

Tools & capabilities

Brandsystem MCP — Build tools 34

  • brand_startBegin here.** Creates a brand system from a website URL in under 60 seconds. Use `mode='auto'` for one-call setup with rendered and deep-site fallback on weak JS-rendered sites.
  • brand_statusCheck progress, get next steps, or see a getting-started guide if no brand exists yet.
  • brand_extract_webExtract logo (SVG/PNG), colors, and fonts from any website URL.
  • brand_extract_visualScreenshot the rendered page in headless Chrome and extract computed colors, fonts, and visual context from JS-heavy sites.
  • brand_extract_siteDiscover representative pages, render them across desktop and mobile, capture screenshots, sample multiple components, and persist `extraction-evidence.json`.
  • brand_generate_designmdGenerate `design-synthesis.json` and `DESIGN.md` from extracted evidence or the current brand state.
  • brand_extract_figmaExtract from Figma design files (higher accuracy). Two-phase: plan then ingest.
  • brand_set_logoAdd/replace logo via SVG markup, URL, or data URI.
  • brand_compileGenerate DTCG design tokens, brand runtime contract, and interaction policy from extracted data.
  • brand_clarifyResolve ambiguous brand values interactively (color roles, font confirmations).
  • brand_auditValidate .brand/ directory for completeness and correctness.
  • brand_reportGenerate portable HTML brand report. Upload to any AI chat as instant guidelines.
  • +22 more on 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.

Brandsystem MCP — Build

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "brandsystem-mcp-build": {
      "command": "npx",
      "args": [
        "-y",
        "@brandsystem/mcp"
      ]
    }
  }
}

Openaffiliate MCP

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

Frequently asked questions

Brandsystem MCP — Build is categorized under Marketing and uses a local stdio subprocess. Openaffiliate MCP belongs to Marketing and uses a local stdio subprocess. Pick Brandsystem MCP — Build 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.

Brandsystem MCP — Build 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 brandsystem-mcp-build and openaffiliate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Brandsystem MCP — Build has a quality signal of 59/100 (Good) with 0 views, 0 installs and 15 GitHub stars. Openaffiliate MCP has 65/100 (Great) with 2 views, 0 installs and 118 GitHub stars.