Transform any blog post or article URL into ready-to-post social media content — powered by AI.
Content To Social MCP server exists for a simple reason — assistants are far more useful when they can act on Content To Social directly instead of describing what you should do. Transform any blog post or article URL into ready-to-post social media content — powered by AI.
Once Content To Social is connected, these are the calls the assistant has available:
transform-content — Transform URL into content for ALL 5 platformstransform-for-platform — Transform URL for a single platformextract-article — Preview extracted article content (free)You will need one environment variable: YOUR_APIFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Content To Social's toolset — transform-content, transform-for-platform, extract-article — is a fair guide to whether it matches your workflow. It is maintained by lebedinskas; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| transform-content | Transform URL into content for ALL 5 platforms |
| transform-for-platform | Transform URL for a single platform |
| extract-article | Preview extracted article content (free) |
{
"mcpServers": {
"content-to-social": {
"url": "https://godberry--content-to-social-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer YOUR_APIFY_TOKEN"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_APIFY_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.