Log inSubmit server

Nashboard Merchants vs Opus Growth

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

N
Nashboard MerchantsMarketingMerchant intelligence for AI agents: brand/operator/location hierarchy + industry codes.12EmergingAuth: not declaredOpus Growth logoOpus GrowthMarketing · Remote HTTP/SSEHosted, 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.75GreatAuth: oauth 2.0

Verdict: choose Nashboard Merchants for marketing work; choose Opus Growth for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

N
Choose Nashboard Merchants when

  • You need dedicated capabilities in the Marketing domain.
Explore Nashboard Merchants

Opus Growth logoChoose Opus Growth when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore Opus Growth

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
N
Nashboard Merchants		Opus Growth logoOpus Growth
CategoryMarketingMarketing
Quality signal12/100 · Emerging75/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars—0
Directory activity 0 views 0 installs 0 upvotes 6 views 0 installs 1 upvotes
ToolsNot listedNot listed
Full listingView Nashboard Merchants View Opus Growth

Tools & capabilities

Nashboard Merchants tools

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

Opus Growth 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.

Nashboard Merchants

No confirmed install command for Nashboard Merchants yet — follow the setup steps linked from its listing page rather than a guessed package name.

Opus Growth

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "opus-growth": {
      "url": "https://mcp.opus-growth.com/mcp"
    }
  }
}

Frequently asked questions

Nashboard Merchants is categorized under Marketing and uses an install path we have not confirmed yet. Opus Growth belongs to Marketing and uses a remote HTTP/SSE transport. Pick Nashboard Merchants for marketing work and Opus Growth 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. Nashboard Merchants has no confirmed install command yet — follow its own setup instructions.

Nashboard Merchants has no declared pricing — check the project's own site. Opus Growth is listed as freemium — a free tier with paid plans. Auth: oauth 2.0. 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 nashboard-merchants and opus-growth as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Nashboard Merchants has a quality signal of 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Opus Growth has 75/100 (Great) with 6 views, 0 installs and 0 GitHub stars.

Popular comparisons with Nashboard Merchants

Popular comparisons with Opus Growth