MCP server · Live
The MCP server for social media publishing
Connect Claude, Cursor, or any MCP client to Solnk and publish to 9 platforms straight from your AI — no custom API wiring. Tell it what to post; it drafts, schedules, and ships.
Draft a launch post and schedule it to all our platforms tomorrow morning.
solnk.create_draftdonesolnk.upload_mediadonesolnk.scheduledonecreate_draftWrite a post per platformscheduleQueue it for a future timepublishSend it live nowlist_accountsSee connected accountsupload_mediaAttach images or videoWhat the Solnk MCP server does
The Model Context Protocol is the now-standard way to hand an AI agent a set of tools it can call. Solnk's MCP server gives your agent publishing tools — so it can act on your social accounts without anyone writing glue code.
Connect once, and from then on you just ask: “draft a launch post for our two IG accounts and schedule it for tomorrow morning.”
Connect in two minutes
Drop the server into your MCP client config, add an API key, and restart. Your agent gets Solnk's publishing tools in the conversation.
Clients with native remote-MCP support (like Cursor) can add the server URL directly with an Authorization: Bearer header. Grab your key at Settings → API Keys.
Server URL
https://mcp.solnk.com/mcpAdd to your MCP client config
{
"mcpServers": {
"solnk": {
"command": "npx",
"args": [
"mcp-remote", "https://mcp.solnk.com/mcp",
"--header", "Authorization: Bearer sk_..."
]
}
}
}Let it draft. You keep the last word.
The valuable part of an AI agent is the drafting — reading a source, shaping copy per platform, scheduling around your times. The risky part is the publish click. Default to drafts, approve in Solnk, and loosen the leash once you trust the output.
Read: how to let an AI agent post safely →MCP or the REST API?
Use MCP
When you work inside an AI client — Claude Desktop, Cursor, or anything MCP-compatible. The agent calls the tools for you.
Use the REST API
When you have built your own agent or a no-code flow (n8n, a cron script). Plain authenticated HTTP calls. See the API.
MCP FAQ
It is a Model Context Protocol server that lets any MCP-compatible AI client — Claude, Cursor, and others — connect to Solnk and publish to 9 social platforms. Your agent gets a set of tools (draft, schedule, publish, list accounts, upload media) without you writing any custom API code.
Claude Desktop, Cursor, and any client that speaks MCP. Clients with native remote-MCP support can add the server URL directly with a Bearer token; everything else connects through the mcp-remote bridge shown below.
Add the Solnk server to your MCP client config, drop in an API key from Settings → API Keys, and restart the client. Your agent then has Solnk publishing tools available in the conversation.
Only if you let it. The safer setup is to have the agent create drafts and approve them in Solnk, then loosen the leash once you trust the output. Direct publishing is available, but draft-first is the recommended default.
Use the MCP server if you work inside an AI client like Claude or Cursor. Use the REST API if you have built your own agent or a no-code automation. Both reach the same 9 platforms.
MCP and API access are part of the paid plan, and there is a free tier so you can connect an agent and see how it behaves before committing.
Give your AI agent a way to post
Start free, connect the MCP server, and let your agent draft to 9 platforms.