There is a difference between an AI assistant that can write you a caption and one that can actually publish it, reply to the comments it earns, and pull the performance report a week later. The first is a text generator. The second is an agent with hands, and the thing that gives it hands is the Model Context Protocol.
Eclincher runs a remote MCP server that connects AI assistants directly to your social accounts. As of 2026 it is live and installable in two major clients, in review at another, and in development for a fourth. This guide covers what it does, exactly where you can use it today, and how to connect it, with the honest status of each platform rather than a wish list.
The short answer
The Eclincher MCP server is a remote Model Context Protocol server at https://app.eclincher.com/mcp that gives AI assistants full-stack control of social media: publishing, inbox engagement, and analytics across 12 or more networks, through 26 tools. It is live today in Claude and Cursor, connects over OAuth in about a minute, and requires no installation or local setup.
What is the Eclincher MCP server?
The Eclincher MCP server is a remote server that implements the Model Context Protocol, an open standard that lets AI assistants connect directly to external software. Instead of copying content between your AI assistant and your social media dashboard, the assistant operates your accounts directly, in plain language.
Three things make it practical rather than theoretical. It is remote, so there is no npm install and no local process to keep running; you point your client at a URL and authenticate. It is full-stack, covering publishing, the social inbox, and analytics rather than scheduling alone. And it is broad, reaching across Facebook, Instagram, X, LinkedIn, TikTok, Pinterest, YouTube, Google Business Profile, WordPress, Reddit, and Threads.
If you want the concept rather than the setup, our explainer on what MCP is and why it matters covers the protocol itself.
Where can you use it right now?
This is the question most people actually arrive with, so here is the current status without spin.
Two clarifications worth making. First, a directory listing is a convenience, not a requirement: any client that speaks MCP can connect to the server URL manually today, including Claude Desktop, Windsurf, and others, whether or not a listing exists. Second, "in review" means exactly that. ChatGPT support depends on OpenAI's approval process and timeline, not Eclincher's, so treat it as pending rather than promised, and check the Eclincher MCP page for the current state before planning around it.
What can AI agents actually do with it?
The server exposes 26 tools across several categories. In practice, that means you can ask an assistant to do the following in plain language.
The inbox capability is the genuinely unusual one. Plenty of tools let an AI schedule a post; far fewer let it read and respond to the conversations that follow. That is what turns "draft me a caption" into "check what came in overnight, draft replies to the questions, and flag anything negative for me."
For concrete examples of what to ask, see our walkthrough of seven things you can do with the Eclincher MCP server.
How do you connect it?
Connection takes about a minute in OAuth-capable clients. Here is the process for each.
The server details you will need:
Server URL: https://app.eclincher.com/mcp
Transport: Streamable HTTP
Auth: OAuth 2.0, or static x-eclincher-api-key header
Claude
Claude supports OAuth, so this is the simplest path. Open the Eclincher listing in the Claude Directory and add it, or add the server URL manually in your connector settings. Authorize Eclincher in the browser window that opens, and you are done. No key to copy, no file to edit.
Cursor
Cursor also supports OAuth. Install from the Cursor Directory listing, or add the server manually in Cursor Settings under Tools and Integrations. For a manual project-level setup, add the server to .cursor/mcp.json in your project root, or to ~/.cursor/mcp.json to make it available everywhere, then authorize when prompted.
Claude Desktop and other MCP clients
Any client that supports remote MCP servers can connect using the same URL. In clients that support OAuth, add the server URL and authorize in the browser. In clients without OAuth, authenticate with a static API key sent as an x-eclincher-api-key header. Generate that key in Eclincher under Settings, then API.
ChatGPT
Not available yet. The Eclincher plugin is currently in review with OpenAI. Once approved, it will connect through the OpenAI plugin directory.
Grok
Not yet live. Support is in development, with no confirmed date.
How does authentication and security work?
Two methods are supported, and the right one depends on your client.
OAuth 2.0 is the recommended path. Clients that support it, including Claude and Cursor, connect with just the server URL plus a one-time browser authorization. Eclincher uses Dynamic Client Registration under RFC 7591, with discovery at /.well-known/oauth-authorization-server. Nothing sensitive is copied or stored by you, and you can revoke access from your Eclincher account.
A static API key is the alternative for existing users, scripts, and clients without OAuth support. Generate it in Settings, then API, and send it as an x-eclincher-api-key header. Treat it like a password: never commit it to a repository or paste it into a shared config.
On the question people reasonably ask, whether it is safe to give an AI access to live social accounts, the honest answer is that the risk is real and manageable. The agent acts with your permissions, so scope matters: start by letting it draft and report rather than publish autonomously, keep a human approving anything that goes public, and revoke access if a workflow stops making sense. That measured approach is the same one behind agentic social workflows, where the balance between automation and oversight matters most.
What does it cost?
MCP access is part of an Eclincher subscription rather than a separate product, so there is no additional MCP fee. Eclincher plans start at $149 per month for Standard and $349 per month for Professional, and a 14-day free trial is available if you want to test the server before committing. Pricing was accurate as of June 2026, so confirm current rates on the pricing page.
Who is this actually for?
Being honest about fit saves everyone time.
It is a strong fit if you already manage social media at some volume and want to cut the dashboard-switching out of your day, if you work in an AI assistant most of the day and want your social stack reachable from there, if you run an agency handling multiple brands and want reporting and drafting on demand, or if you are technical and want to script agentic workflows.
It is probably not for you if you post occasionally to one or two channels, since the overhead is not worth it, or if you are not already an Eclincher user and would be buying the platform mainly for MCP access. It is a capability layer on a full platform, not a standalone tool.
Frequently asked questions
What is the Eclincher MCP server?
It is a remote Model Context Protocol server at https://app.eclincher.com/mcp that lets AI assistants control social media directly, covering publishing, inbox engagement, and analytics across 12 or more networks through 26 tools. It requires no installation: you point an MCP-compatible client at the URL and authenticate.
Which AI assistants support the Eclincher MCP server?
It is live today in Claude and Cursor, both of which have directory listings. Support for ChatGPT is in review with OpenAI, and Grok support is in development. Any MCP-compatible client, including Claude Desktop and Windsurf, can connect manually using the server URL.
Does ChatGPT work with the Eclincher MCP server?
Not yet. The Eclincher plugin is currently in review in the OpenAI plugin directory, and availability depends on OpenAI's approval process. Claude and Cursor are live today, and any MCP-compatible client can connect manually in the meantime.
How do I connect Eclincher to Claude?
Open the Eclincher listing in the Claude Directory and add it, or add the server URL https://app.eclincher.com/mcp manually in your connector settings. Claude supports OAuth, so you authorize once in the browser and you are connected. There is no key to copy and no configuration file to edit.
Do I need to install anything or write code?
No. The Eclincher MCP server is remote, so there is no npm install and no local process to run. In OAuth-capable clients like Claude and Cursor, connecting is a URL plus a one-time browser authorization. Only clients without OAuth require a manually generated API key.
Is it safe to give an AI assistant access to my social accounts?
The agent acts with the permissions you grant, so manage scope deliberately. Start with drafting and reporting rather than autonomous publishing, keep a human approving anything public, use OAuth where available, and revoke access from your Eclincher account if a workflow is no longer needed.
Does the MCP server cost extra?
No. MCP access is included with an Eclincher subscription rather than sold separately. Plans start at $149 per month, and a 14-day free trial lets you test the server before committing. Confirm current pricing on the Eclincher pricing page.
The bottom line
The gap between an AI that talks about your social media and one that runs it comes down to whether it has a real connection to your accounts. The Eclincher MCP server is that connection, and it is live today in Claude and Cursor, reachable manually from any MCP-compatible client, with ChatGPT in review and Grok in development.
If you already use Eclincher, connecting takes about a minute and costs nothing extra. If you do not, the 14-day trial is the fastest way to see whether an agent with hands changes how you work. Full technical details live on the Eclincher MCP page.
Start your free trial or explore the Eclincher MCP server
