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

Docs · Pricing · MCP Info · Get Started

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?

Related MCP server: @posteverywhere/mcp

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. See OAuth 2.0 for the full flow.

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

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

OAuth 2.0

The recommended way to connect. OAuth-capable MCP clients — Claude.ai, Claude Desktop, Cursor, Windsurf, and others — connect with nothing but the server URL. There's no API key to generate, copy, or rotate: on first connect your client opens a browser window where you sign in to Eclincher and grant access, and tokens are handled for you from there.

How it works

Eclincher implements the MCP authorization spec on top of standard OAuth 2.0, so everything is discovered and registered automatically — there's no "create an app, copy a client ID and secret" step.

Your client reads the authorization and token endpoints from the metadata document, so there's nothing to hardcode beyond the server URL itself.

Connection flow

1. Client fetches server metadata from the .well-known endpoint.

2. Client registers itself automatically (DCR) and receives credentials.

3. Client opens the authorization URL in your browser.

4. You sign in to Eclincher and approve the connection.

5. Client exchanges the authorization code (with PKCE) for an access token.

6. Client calls the MCP server with the bearer token, refreshing automatically as needed.

In practice: paste the server URL → click Authorize → done.

OAuth client config

OAuth config is identical to the static-key examples below — just drop the headers block and let the client handle browser authorization:

{
  "mcpServers": {
    "eclincher": {
      "url": "https://app.eclincher.com/mcp"
    }
  }
}

This applies to every client in Client configurations: use the same snippet, without headers. For clients with a built-in connector UI (Claude.ai, Cline), just add the server URL and authorize when prompted.

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"
      }
    }
  }
}

(For OAuth, omit the headers block and authorize when prompted.)

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"
    }
  }
}

(For OAuth, omit the headers block and authorize when prompted.)

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"
      }
    }
  }
}

(For OAuth, omit the headers block and authorize when prompted.)

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"
        }
      }
    }
  ]
}

(For OAuth, omit the headers block and authorize when prompted.)

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

Publishing

Inbox

Inbox → CRM & ticketing

Analytics

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 jobs — create_post and some analytics reports return a jobId; poll get_post_status / get_analytics_job_status until complete.

• Timestamps — Unix seconds (not milliseconds).

• Timeframes — today, 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:

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.

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

Rate limits

Per API key (shared across all team members).

Rate limit headers are included in every response.

Links

• Developer Portal

• MCP Info

• Pricing

• Auto-discovery

• Support

License

MIT — see LICENSE.