LabscoMCP early access ↗
talmMCP SERVER · OFFICIAL PROJECT

Eclincher

Publish, schedule and edit posts across a dozen social networks, then work the inbox — replies, likes, tags, sentiment and CRM handoff — from one hosted MCP endpoint.

by talm ↗Social Media Accounts & Posting✓ Official

LABSCO SUMMARY

Inbox actions, not just publishing.

Most social connectors stop at posting; this one replies to a DM, tags it, assigns it to a teammate, sets its sentiment and closes it — which is the part of social management that actually takes time. Two things to plan for: publishing and some reports are asynchronous, so the answer is a job id you poll, and a key reaches every brand on the account, so it is not a way to scope an assistant to one client.

What it is

A remote MCP server for Eclincher, covering social publishing and, unusually, the whole social inbox. Nothing installs locally: you point a client at the URL and authenticate. Work is scoped by brand, so the first call is always to list brands and the second to list the profiles under one.

What you get

  • Accounts — list_brands first for your brand IDs, then list_accounts for the profile IDs everything else needs, and create_brand to add one
  • Publishing — create_post with text, image or video across a list of profiles, immediately or at Unix timestamps; it returns a jobId you poll with get_post_status
  • Scheduled posts — get_scheduled_posts with time range, profile, type and text-search filters, and edit_post to change text, targets, schedule or media (pass attachments back to keep them)
  • Inbox reading — list_inbox over a range of up to 90 days, filtered by event type, profile, tag, role, sentiment, read and completed state; list_inbox_tags and list_inbox_roles supply the valid filter values
  • Inbox acting — reply_to_inbox_event with optional media, like_inbox_event, twitter_inbox_actions for retweet, follow, block or mute, set_inbox_events to apply tags, roles, feeds and sentiment in bulk, complete_inbox_event to close or reopen
  • Handoff to your ticketing system — salesforce_inbox_request, zendesk_inbox_request, servicenow_inbox_request
  • Analytics — get_builtin_report, get_comparison_report, get_cross_channel_report, list_custom_reports and get_custom_report, list_competitor_reports and get_competitor_report, with get_analytics_job_status for the ones that run asynchronously
  • 26 tools in total, across Facebook, Instagram, X/Twitter, LinkedIn, TikTok, Pinterest, YouTube, Google Business, WordPress, Reddit and Threads

Requirements

An Eclincher account — there is a 14-day free trial, and API access starts at the Standard plan. Add https://app.eclincher.com/mcp as a Streamable HTTP server. Clients that support OAuth 2.0 need only the URL and a one-time browser authorization, using Dynamic Client Registration discovered at /.well-known/oauth-authorization-server. Otherwise generate a key under Settings → API and send it as the x-eclincher-api-key header. Note that a key is scoped to the whole account, every brand and profile included, and you can hold at most 3 active keys.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen

See installation options