mcp-metricool
Related Servers
Alternatives to mcp-metricool
No user-submitted related servers found.
Related Servers
AlicenseAqualityFmaintenanceThis is a Multi-Agent Collaboration Protocol (MCP) server for interacting with the Metricool API. It allows AI agents to access and analyze social media metrics and campaign data from your Metricool account.2838Apache 2.0- AlicenseAqualityCmaintenanceMCP server for Instagram Graph API, Threads API & Meta platform — posting, insights, comments, messaging57360 npm26MIT
- AlicenseAqualityBmaintenanceMCP server for Publer social media management API, enabling AI assistants to schedule posts, upload media, pull analytics, and manage accounts across 15+ social networks.1529 npm21MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for organic Instagram analytics via the Meta Graph API, providing read-only tools for profiles, media, insights, audience, and optional publishing.GPL 3.0
- FlicenseNot gradedqualityDmaintenanceSpecialized MCP server for digital marketing and social media management, enabling content generation, hashtag optimization, planning, analytics, and engagement strategies.-
- FlicenseAqualityBmaintenanceMCP server for publishing posts and retrieving metrics on social platforms like Telegram, with planned support for YouTube and Instagram.3-
TDQS
Scored across 5 tools
Each tool targets a distinct action: listing brands, finding best times, scheduling, retrieving scheduled posts, and fetching analytics. No two tools overlap in purpose, so an agent can easily select the right one.
All tools use the metricool_ prefix followed by a consistent snake_case verb_noun pattern (get_brands, get_best_time, schedule_post, get_scheduled_posts, get_analytics). The convention is predictable and uniform.
Five tools are well-scoped for a LinkedIn social media management integration, covering the essential operations without unnecessary bloat. Each tool earns its place in the workflow.
The surface covers reading brands, scheduling posts, listing scheduled posts, and analytics, but lacks update or delete/cancel operations for scheduled posts. This is a notable gap for lifecycle management, though core workflows are partially supported.