Publora MCP Server
OfficialRelated Servers
Alternatives to Publora MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceOfficial MCP server for PostIdentity - Generate AI-powered social media posts, threads, and replies from any MCP-compatible AI assistant with identity management and refinement capabilities.14 npm1MIT
- AlicenseBqualityDmaintenanceThe official MCP server for Semantic Pen - an advanced AI article generator and SEO content writer. Create, manage, and optimize SEO-friendly articles directly from Claude Code and Cursor Windsurf with powerful AI automation.511 npm2MIT
- AlicenseAqualityBmaintenanceOfficial MCP server for creating and managing AI UGC video ads. Browse assets, estimate credit costs, generate videos, and retrieve completed outputs through eleven typed tools.1127 npmMIT
- 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

BlazingCDN-MCPofficial
AlicenseAqualityBmaintenanceOfficial MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Cloud Storage and Video CDN2964 npm2MIT- AlicenseAqualityDmaintenanceOfficial MCP server for FormaCV, enabling AI-powered CV formatting, anonymization, tailoring, and ATS push-back from AI agents like Claude Desktop and Cursor.831 npm1MIT
TDQS
Scored across 18 tools
Each tool targets a distinct resource and action. The LinkedIn tools are clearly grouped, workspace user tools are separate, and post tools handle different CRUD operations without overlap.
Mixed conventions: post tools use verb_noun (create_post), workspace tools mix verb_noun and noun_verb (create_workspace_user vs workspace_detach_user), while LinkedIn tools consistently use linkedin_ prefix followed by action_object. This inconsistency may confuse.
With 18 tools, the server covers workspace management, posting, and LinkedIn analytics. Slightly above the typical 3-15 range, but still reasonable given the scope. Not excessive.
Covers core workflows: post CRUD with scheduling, LinkedIn engagement and stats, workspace user lifecycle (except update/delete user). Minor gaps like missing user update and lack of platform-specific tools for non-LinkedIn accounts, but overall sufficient.