Hermoso
OfficialRelated Servers
Alternatives to Hermoso
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides Meta and Google Ads intelligence for AI assistants, enabling users to analyze performance, track competitors, and manage ad campaigns through natural language. It features 17 tools for generating creative concepts, scraping competitor ads, and performing deep account-level analysis.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, analyze, and optimize ad campaigns across Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Amazon Ads, and ChatGPT Ads through natural language using 400+ tools.93MIT
- AlicenseNot gradedqualityAmaintenanceManage ad campaigns across Meta, Google, and TikTok, create campaigns, analyze performance, spy on competitors, and generate AI creatives.13MIT
- FlicenseNot gradedqualityDmaintenanceSearches and analyzes competitor ads and content across Meta, Google, Instagram, TikTok, and YouTube with AI-powered creative analysis and cross-platform brand discovery.1-
- AlicenseAqualityAmaintenance50 tools for Meta Ads campaign management, creative analysis, audience building, and conversion tracking, accessible to any MCP-compatible AI agent.69236 npm13MIT
- AlicenseNot gradedqualityDmaintenanceGenerate AI UGC video ads from any product URL in 5 minutes. Realistic AI avatars, natural voiceover, proven ad templates. No actors, no editing, no experience required.87 npm1MIT
TDQS
Scored across 175 tools
Many tools cluster around the same action (post_to_*, search_*, generate_*/render_*), and clone_static/remix_static are literally the same operation under two names. However, the descriptions are unusually detailed and often explicitly route to the correct alternative, which mitigates most confusion.
The dominant pattern is verb_noun snake_case (post_to_x, list_meta_pages, create_sheet), which is predictable and readable. Deviations exist — noun_verb (store_get), noun_noun (hermoso_capabilities, billing_status), and bare verbs (remember, forget) — but they are relatively few.
175 tools is far beyond the 25+ threshold and creates a massive surface, even for a platform spanning publishing, ads, analytics, storage and admin. The enable_tools/find_tools roster mechanism mitigates practical burden, but the delivered set is still excessive and would be stronger consolidated into fewer composable tools.
The surface is nearly exhaustive for its domain: create/read/update/delete exists for posts, schedules, files, sheets, docs, brands, memory, playbooks, skills, creators, and connectors, plus research, performance, and billing. No obvious dead ends or missing lifecycle operations.