AgentStack
MCP verified MIT Self-run

Eclincher Mcp Server

mcp-talm-eclincher-mcp-server · by talm

Full-stack social media MCP server — publish, inbox, analytics across 8 networks

No reviews yet
0 installs
11 views
0.0% view→install

Install

$ agentstack add mcp-talm-eclincher-mcp-server

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Eclincher Mcp Server? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Eclincher MCP Server

Full-stack social media management for AI agents.

Publish, schedule, edit, and engage — plus full inbox management and analytics across Facebook · Instagram · X/Twitter · LinkedIn · TikTok · Pinterest · YouTube · Google Business · WordPress · Reddit · Threads

[](https://modelcontextprotocol.io) [](#tools) [](#supported-networks) [](#authentication) [](LICENSE)

Docs · Pricing · MCP Info · [Get Started](#quick-start)


What is this?

Eclincher MCP is a remote Model Context Protocol server that gives AI agents — Claude, ChatGPT, Cursor, Windsurf, and others — full-stack control of social media: publishing, inbox engagement, and analytics across 12+ networks.

No npm install. No local process. Point your MCP client at our URL and authenticate.

Server URL:  https://app.eclincher.com/mcp
Transport:   Streamable HTTP
Auth:        OAuth 2.0 (Dynamic Client Registration) — or static x-eclincher-api-key header
Tools:       26

What can it do?

| Category | What AI agents can do | |---|---| | Publishing | Schedule, publish, and edit posts across 12+ networks — text, images, video. Retrieve scheduled posts (with attachments) and track async publish jobs. | | Inbox | Read and act on DMs, comments, mentions, and reviews: reply, like/favorite/follow, Twitter actions (retweet, follow, block, mute), assign tags/roles/sentiment, and mark complete. The only MCP server with full social inbox access. | | Inbox → CRM & ticketing | Push inbox events into Salesforce, Zendesk, or ServiceNow. | | Analytics | Pull performance, comparison, custom, competitor, and cross-channel reports, with async job-status checks. | | Account management | List brands and connected profiles; create new brands. |


Quick start

1. Connect

OAuth 2.0 — recommended. MCP clients that support OAuth (Claude.ai, Claude Desktop, Cursor, and others) connect with just the server URL and a one-time browser authorization — no key to copy. Eclincher uses Dynamic Client Registration (RFC 7591), discovered at /.well-known/oauth-authorization-server.

Static API key — alternative. Existing Eclincher users, scripts, and clients without OAuth can authenticate with a key. Sign up at eclincher.com/pricing (free 14-day trial), go to Settings → API to generate one, and send it as the x-eclincher-api-key header.

2. Add to your MCP client

Pick your client below. The examples use static-key auth; for OAuth, use the same server URL without the headers block and authorize when prompted.


Authentication

| Method | Best for | How | |---|---|---| | OAuth 2.0 + DCR (RFC 7591) | Claude.ai, Cursor, Claude Desktop, and other OAuth-capable MCP clients | Add the server URL; authorize in the browser. Discovery: https://app.eclincher.com/.well-known/oauth-authorization-server · Registration: https://app.eclincher.com/oauth/register · Scope: mcp | | Static API key | Existing users, scripts, REST API, clients without OAuth | Header x-eclincher-api-key: YOUR_API_KEY. Generate in Settings → API (max 3 active keys per account). |

For direct REST API calls, also include version: v5 and Content-Type: application/json.


Client configurations

Claude Desktop

Edit your config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Linux: ~/.config/claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "eclincher": {
      "url": "https://app.eclincher.com/mcp",
      "headers": {
        "x-eclincher-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Restart Claude Desktop after saving. (For OAuth, omit the headers block and authorize when prompted.)


Claude.ai (web)

  1. Go to Settings → Connectors → Add custom connector
  2. Server URL: https://app.eclincher.com/mcp
  3. Authorize in the browser (OAuth), or add the custom header x-eclincher-api-key to use a static key.

Cursor IDE

Create .cursor/mcp.json in your project root (or add to global settings):

{
  "mcpServers": {
    "eclincher": {
      "url": "https://app.eclincher.com/mcp",
      "headers": {
        "x-eclincher-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Windsurf IDE

Go to Settings → MCP Servers → Add Server, or add to your config:

{
  "eclincher": {
    "serverUrl": "https://app.eclincher.com/mcp",
    "headers": {
      "x-eclincher-api-key": "YOUR_API_KEY"
    }
  }
}

VS Code (GitHub Copilot MCP)

Create .vscode/mcp.json in your project root:

{
  "servers": {
    "eclincher": {
      "type": "http",
      "url": "https://app.eclincher.com/mcp",
      "headers": {
        "x-eclincher-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Continue.dev (VS Code / JetBrains)

Edit ~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "eclincher",
      "transport": {
        "type": "streamable-http",
        "url": "https://app.eclincher.com/mcp",
        "headers": {
          "x-eclincher-api-key": "YOUR_API_KEY"
        }
      }
    }
  ]
}

Cline (VS Code extension)

  1. Open Cline Settings → MCP Servers → Add Remote Server
  2. Transport: Streamable HTTP
  3. URL: https://app.eclincher.com/mcp
  4. Authorize via OAuth, or add the header x-eclincher-api-key.

Tools

26 tools across publishing, inbox, analytics, and account management.

Brands & accounts

| Tool | Description | |---|---| | list_brands | List all brands for the authenticated user. Call this first — other tools need a brandId. | | create_brand | Create a new brand. | | list_accounts | List connected social profiles for a brand. Returns profile IDs for publishing and analytics. |

Publishing

| Tool | Description | |---|---| | create_post | Schedule or publish a post (text, image/video). Runs async — returns a jobId. | | edit_post | Edit a scheduled post. Keep existing attachments (pass them back from get_scheduled_posts), add new image/video URLs, or replace the video (one video supported). | | get_scheduled_posts | Retrieve scheduled posts by filters (time range, profiles, post types, search). Includes each post's attachments with S3 URLs. | | get_post_status | Check the status of an async create_post job by jobId. |

Inbox

| Tool | Description | |---|---| | list_inbox | List inbox messages — DMs, comments, mentions — with filters (event types, profiles, tags, roles, sentiment, search, read/completed state). | | list_inbox_tags | List inbox tags available for a brand (valid values for the list_inbox tags filter). | | list_inbox_roles | List team members/roles for the account (valid values for the list_inbox roles filter). | | reply_to_inbox_event | Reply to a message or comment on a social profile, with optional image/video attachments. | | like_inbox_event | Like, favorite, or follow an inbox event. | | twitter_inbox_actions | Twitter-specific actions: retweet, follow, block, or mute. | | set_inbox_events | Update inbox event metadata — assign tags, roles, feeds, sentiments, or mark events. | | complete_inbox_event | Mark an inbox event complete, or reopen it (completion audit record generated server-side). |

Inbox → CRM & ticketing

| Tool | Description | |---|---| | salesforce_inbox_request | Create or update a Salesforce record from an inbox event. | | zendesk_inbox_request | Create or update a Zendesk ticket from an inbox event. | | servicenow_inbox_request | Create or update a ServiceNow incident from an inbox event. |

Analytics

| Tool | Description | |---|---| | get_builtin_report | Built-in performance report for a brand/profile. | | get_comparison_report | Compare analytics across profiles. | | get_cross_channel_report | Aggregated analytics across networks. | | list_custom_reports | List custom analytics reports for a brand. | | get_custom_report | Get data for a specific custom report. | | list_competitor_reports | List competitor analysis reports. | | get_competitor_report | Get competitor benchmark data. | | get_analytics_job_status | Check the status of an async analytics job by jobId. |

Key data formats

  • brandId — opaque identifier returned by list_brands; pass it back exactly as received, never construct or parse it.
  • profile vs profileIds — publishing (create_post) takes a profile array of IDs; analytics take profileIds as a single UUID (get_builtin_report) or pipe-delimited uuid1|uuid2 (max 20) for comparison/cross-channel.
  • Async jobscreate_post and some analytics reports return a jobId; poll get_post_status / get_analytics_job_status until complete.
  • Timestamps — Unix seconds (not milliseconds).
  • Timeframestoday, yesterday, last7days, last30days, thisweek, lastweek, thismonth, lastmonth, thisyear, lastyear.
  • Account types (analytics) — facebook, instagram, twitter, linkedin, pinterest, tiktok, youtube, google_business.

Supported networks

Full-stack support — publish, inbox, and analytics on every network:

| Network | Publish | Inbox | Analytics | |---|---|---|---| | Facebook | ✅ | ✅ | ✅ | | Instagram | ✅ | ✅ | ✅ | | X / Twitter | ✅ | ✅ | ✅ | | LinkedIn | ✅ | ✅ | ✅ | | TikTok | ✅ | ✅ | ✅ | | Pinterest | ✅ | ✅ | ✅ | | YouTube | ✅ | ✅ | ✅ | | Google Business | ✅ | ✅ | ✅ | | WordPress | ✅ | ✅ | ✅ | | Reddit | ✅ | ✅ | ✅ | | Threads | ✅ | ✅ | ✅ |


Example conversations

Publishing > "Schedule a post about our new product to Instagram, LinkedIn, and TikTok for tomorrow at 9 AM"

> "Move my Friday post to Saturday and swap in this new image"

Inbox > "Show me all unanswered DMs and comments from the last 24 hours"

> "Reply to Sarah's comment thanking her, then mark it complete"

> "Open a Zendesk ticket from this complaint and tag it as urgent"

Analytics > "How did our Instagram perform this month vs last month?"

> "Give me a cross-channel summary of all our social accounts for Q1"

> "How do we compare to our competitors on engagement?"


Pricing

API and MCP access is included with all Eclincher plans.

| Plan | Price | Brands | Users | Social profiles | |---|---|---|---|---| | Standard | $149/mo | 1 | 1 (max 2) | 15 (max 20) | | Professional | $349/mo | Unlimited | 5 (max 10) | 25 (max 40) | | Enterprise | Custom | Unlimited | Custom | Custom |

Free 14-day trial. Cancel anytime. eclincher.com/pricing


Rate limits

Per API key (shared across all team members).

| Dimension | Standard | Professional | Enterprise | |---|---|---|---| | Requests per minute | 30 | 90 | Custom | | Daily credits | 5,000 | 15,000 | Custom | | Concurrent requests | 2 | 10 | Custom | | Posts per day | 50 | 200 | Custom |

Rate limit headers are included in every response.


Links


License

MIT — see [LICENSE](LICENSE).

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.