Most social media tools assume you'll open a dashboard, click through a composer, pick a time and repeat for every network. That works until you're managing several brands, or you've already done the thinking in an AI assistant and just want the post to go out.
Feedlio's MCP server lets you skip the dashboard. You connect it to an AI assistant that supports the Model Context Protocol, such as Claude, and then you plan, write, schedule and check posts in plain language, in the same conversation where you did the thinking.
This post explains what that looks like in practice, how to set it up, and where it saves the most time.
What MCP is, in one paragraph
The Model Context Protocol is an open standard for connecting AI assistants to external tools and data. An MCP server exposes a set of tools, each with a name, a description and typed inputs, and the assistant decides when to call them based on what you ask. It's the same idea as a plugin, but standardised, so one server works with every assistant that speaks the protocol.
What Feedlio's MCP server can do
Feedlio is an AI social media manager that publishes to 12 platforms from one place: Facebook, Instagram, LinkedIn, YouTube, TikTok, Threads, Bluesky, Pinterest, Mastodon, Dev.to, Dribbble and Lemmy. The MCP server exposes the core of that to your assistant:
- Workspaces and accounts: list your workspaces (one per brand or client) and the social accounts connected to each.
- Posts: create a post for one or several platforms, publish now or schedule it, then list, reschedule, cancel or delete scheduled posts.
- Media: add an image or video to your media library from a URL, list what's there, and attach it to posts.
Because each workspace is separate, an agency can say "schedule this for the client workspace, LinkedIn and Facebook only" and the assistant picks the right accounts.
Setting it up
The server URL is:
https://mcp.feedlio.io/mcp
In Claude, add it as a custom connector using that URL, then sign in to your Feedlio account when prompted. The same URL works in other assistants that support remote MCP servers. Feedlio's server is also listed on the official MCP Registry, Smithery and mcpservers.org.
You'll need a Feedlio account with at least one social account connected in the web app first. Connecting a social network uses that network's own sign-in, which happens in Feedlio's dashboard, not in the chat.
What it looks like in practice
Here are the kinds of requests that work well once it's connected.
Plan and schedule a week:
"We're launching a new feature on Thursday. Draft a LinkedIn post and a shorter Facebook post announcing it, then schedule LinkedIn for Thursday 10:00 and Facebook for 11:00, Kuala Lumpur time."
The assistant writes both drafts, shows them to you, and after you approve, calls the tools to schedule each one on the right account.
Repurpose something you already wrote:
"Here's our latest blog post. Turn it into three LinkedIn posts for next Monday, Wednesday and Friday at 9:00, each with a different angle."
Check what's going out:
"What's scheduled for the client workspace this week? Move Wednesday's post to Thursday."
Add media:
"Add this image URL to the media library and use it on the Thursday post."
The pattern is the same each time: you describe the outcome, review what the assistant proposes, and approve. Nothing is posted until the assistant calls the tool, and good assistants show you the post before they do.
Where it saves the most time
- Agencies and multi-brand teams. Switching between workspaces in a conversation is faster than switching tabs, and the assistant keeps track of which account is which.
- Content you already drafted with AI. No more copying text from the chat into a composer, platform by platform.
- Bulk changes. "Push every post this week back a day" is one sentence, not a dozen clicks.
- Quick checks. "Did Tuesday's post go out on all platforms?" gets an answer without opening the dashboard.
A few honest limits
- Connecting a new social account still happens in the Feedlio dashboard, because each network requires its own sign-in flow.
- Image formats matter. Some networks reject certain formats, so PNG or JPG is the safe choice for images.
- The assistant is only as careful as your instructions. Ask it to show you each post before scheduling, and it will.
Try it
Create a free account at feedlio.io, connect one social account, then add https://mcp.feedlio.io/mcp to your assistant and ask it to list your workspaces. If that works, you're set.
If you're building with MCP yourself, we'd like to hear what you'd want from a social media MCP server. Leave a comment.
Top comments (0)