publiar-mcp
Related Servers
Alternatives to publiar-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.2MIT
- AlicenseNot gradedqualityBmaintenanceA production-ready MCP server that enables AI agents to autonomously create, manage, and engage with LinkedIn content through the official LinkedIn REST API.74 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for LinkedIn publishing from AI coding assistants. Dry run by default, SKILL.md for safe workflows, 28 unit tests. MIT licensed.33 npm2MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables LinkedIn content generation through Claude, offering brand setup, playbooks, on-brand PDF/PNG rendering, and post tracking with per-client tokens.MIT
- AlicenseAqualityDmaintenanceHigh-performance autonomous MCP server that turns LinkedIn into an API for AI workflows, enabling profile management, job search, content posting, and document generation.141MIT
- AlicenseAqualityDmaintenanceFully featured MCP server that provides automation tools for LinkedIn, supporting browser-based scraping and API-based operations for content management, media uploads, and reactions.63MIT
TDQS
Scored across 19 tools
There is some overlap between generate_lead_magnet and the legacy generate_pair, and between render_visual and render_gif, which could cause misselection. However, the descriptions explicitly guide the agent toward the preferred tool, so the ambiguity is manageable.
Almost all tools follow a clear snake_case verb_noun pattern (e.g., render_visual, list_published, set_published_status). The only outlier is 'whoami', a standard command-style name, which is a minor deviation rather than a break in the pattern.
With 19 tools, the server is on the heavy side. Several tools are legacy (generate_pair, poll_published_now) or auxiliary (whoami), inflating the count. The core functionality could likely be served with fewer, more focused tools.
The core workflow is well covered: generate, render, publish, update, track, and handle comments. Minor gaps include the lack of a delete/unpublish operation and no way to read back entries from the memory store (add_memory only writes), but these are not critical for the main purpose.