Bento MCP vs Opus Growth

In-depth architectural comparison of the Bento MCP and Opus Growth MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

B

Choose Bento MCP when:

• You need dedicated capabilities in the Marketing domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: WORKSPACE_COOKIE_SIGNING_KEY, SUPABASE_PROJECT_ID, SUPABASE_DB_URL, MIGRATION_CONFIRMATION.
• Primary tools included: Remote OAuth MCP access, Page-scoped WebMCP, Link pages and digital product storefront.

Explore Bento MCP Details

Choose Opus Growth when:

• You need dedicated capabilities in the Marketing domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: OAuth 2.0 (Freemium).
• Primary tools included: Hosted MCP endpoint, Google OAuth sign-in, Five supported advertising platforms.

Feature & Specification Comparison

Specification	B Bento MCP Marketing	Opus Growth VerifiedMarketing
Summary	Run your Bento creator store from any AI assistant: manage link-in-bio pages, digital products, bookings, discount codes, social posts and auto-DMs. Bento is an open-source Stan Store alternative.	Hosted, OAuth-protected MCP server for advertising operations. One connector covers Google Ads, Meta Ads, Microsoft Advertising, TikTok Ads and LinkedIn Ads, plus Search Console, GA4, YouTube, Tag Manager and Google Business Profile. Every write returns a dry-run preview and is applied only after explicit confirmation.
Category & Scope

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "bento-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bento-mcp"
      ],
      "env": {
        "WORKSPACE_COOKIE_SIGNING_KEY": "YOUR_WORKSPACE_COOKIE_SIGNING_KEY_HERE",
        "SUPABASE_PROJECT_ID": "YOUR_SUPABASE_PROJECT_ID_HERE",
        "SUPABASE_DB_URL": "YOUR_SUPABASE_DB_URL_HERE",
        "MIGRATION_CONFIRMATION": "YOUR_MIGRATION_CONFIRMATION_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "opus-growth": {
      "url": "https://mcp.opus-growth.com/mcp"
    }
  }
}

Related MCP Server Comparisons