Log inSubmit server

Hermoso vs MarketCore

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

Hermoso logoHermosoMarketing · Local subprocess (stdio)AI ad studio for agents: generate finished video, image, and UGC avatar ads for any brand (script, voiceover, music, brand end card), and research competitor ads across the Meta, Google, and LinkedIn ad libraries plus TikTok/Instagram/YouTube organic. 52 tools. Install: npx -y hermoso mcp, or connect to the hosted endpoint at app.hermoso.ai/mcp. Free signup grant, no card.56GoodAuth: not declared
M
MarketCoreMarketingCreate on-brand marketing deliverables and GTM docs with AI-powered blueprints and brand guidelines.38FairAuth: not declared

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

Which MCP server should you choose?

Hermoso logoChoose Hermoso when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
Explore Hermoso

M
Choose MarketCore when

  • You need dedicated capabilities in the Marketing domain.
Explore MarketCore

Feature & specification comparison

Rows where the two servers differ are marked.

SpecHermoso logoHermoso
M
MarketCore
CategoryMarketingMarketing
Quality signal56/100 · Good38/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingFreemiumNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2—
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView Hermoso View MarketCore

Tools & capabilities

Hermoso tools

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

MarketCore 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.

Hermoso

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "hermoso-ai-hermoso": {
      "command": "npx",
      "args": [
        "-y",
        "hermoso"
      ]
    }
  }
}

MarketCore

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

Frequently asked questions

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

Hermoso is listed as freemium — a free tier with paid plans. MarketCore has no declared pricing — check the project's own site. 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 hermoso-ai-hermoso and marketcore as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Hermoso has a quality signal of 56/100 (Good) with 2 views, 0 installs and 2 GitHub stars. MarketCore has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.

Popular comparisons with Hermoso

Popular comparisons with MarketCore