Log inSubmit server

MarketCore vs Hermoso

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

M
MarketCoreMarketingCreate on-brand marketing deliverables and GTM docs with AI-powered blueprints and brand guidelines.38FairAuth: not declaredHermoso 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

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

Which MCP server should you choose?

M
Choose MarketCore when

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

Hermoso logoChoose Hermoso when

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

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
M
MarketCore		Hermoso logoHermoso
CategoryMarketingMarketing
Quality signal38/100 · Fair56/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredFreemium
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—2
Directory activity 0 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView MarketCore View Hermoso

Tools & capabilities

MarketCore tools

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

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

MarketCore

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

Hermoso

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

Frequently asked questions

MarketCore is categorized under Marketing and uses an install path we have not confirmed yet. Hermoso belongs to Marketing and uses a local stdio subprocess. Pick MarketCore for marketing work and Hermoso 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.

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

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

Popular comparisons with MarketCore

Popular comparisons with Hermoso