Cituna Mcp vs Lhremote — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cituna Mcp vs Lhremote
In-depth architectural comparison of the Cituna Mcp and Lhremote MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Cituna Mcp
Marketing · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Lhremote
Marketing · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Cituna Mcp if you need specialized Marketing tools running via a local process. Choose Lhremote if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cituna Mcp when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Track how 6 AI engines cite your brand, daily, with live Google Search Console.
Open-source CLI and MCP server for LinkedHelper automation — 32 tools for campaign management, messaging, and profile queries via Chrome DevTools Protocol.
Cituna Mcp is categorized under Marketing and uses a local stdio subprocess. In contrast, Lhremote belongs to Marketing using local stdio subprocess. Select Cituna Mcp when you need capabilities focused on marketing and Lhremote when you require tools for marketing.
Keywords with real demand, each with the stage of the page behind it. Filter `stage: "none"` for demand nothing has been written for yet. Needs Pro (the keyword dataset is a Pro feature)
list_content_queue
What AutoSEO already has in flight, so you never queue a topic twice
queue_article
Queue a keyword so AutoSEO drafts it on the next run
mark_article_published
Tell Cituna a page is live, so it stops suggesting the topic and never writes a competing page
gsc_status
Google Search Console, if connected
run_scan
Trigger a fresh scan
Lhremote Tools (69)
find-app
Detect running LinkedHelper application instances and their CDP connection details.
launch-app
Launch the LinkedHelper application with remote debugging enabled.
quit-app
Quit the LinkedHelper application.
list-accounts
List available LinkedHelper accounts. Returns account ID, LinkedIn ID, name, and email for each account.
start-instance
Start a LinkedHelper instance for a LinkedIn account.
stop-instance
Stop a running LinkedHelper instance.
check-status
Check LinkedHelper connection status, running instances, and database health.
campaign-list
List existing campaigns with summary statistics.
campaign-create
Create a new campaign from YAML or JSON configuration.
campaign-get
Get detailed campaign information including action chain.