Publish, schedule, manage, and analyze social content across nine platforms through MCP.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
This server is confirmed live β we successfully called its tools/list endpoint directly (see the verified badge above). We haven't yet sandbox-tested the stdio install command below specifically, which is a separate, ongoing check.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Solnk MCP.
solnk_list_teamsList teams owned by the connected Solnk user. Call this before solnk_delete_team to identify the protected default team, the API-key team, and a destination team for migrated content.
solnk_set_default_teamMake the connected API-key team the owner's default team. The default team is used as the fallback after leaving a shared team and is preselected as the migration destination when deleting another team.
solnk_delete_teamPermanently delete an extra team after the user explicitly requests it. The connected API key must belong to the deleted team. Accounts, posts, groups, and media move to destination_team_id; memberships, source-team API keys, webhooks, and invitations are removed. The default team cannot be deleted. Success revokes the current API key, so the MCP connection must be reconnected to a key in the destination team.
solnk_list_accountsList the user's connected social accounts (id, platform, username, status, capabilities). Call this first to get account_id values for publishing.
solnk_get_usageGet the user's plan limits and current usage. Check `can_publish` is true before publishing.
solnk_publishPublish content to one or more platforms in a single request. Use publish_mode 'draft' to stage for review (then solnk_confirm_publish), 'scheduled' with scheduled_at, or 'immediate' to send now. Reuse the same idempotency_key when retrying the same logical publish. If omitted and a network/503 error occurs, the error details include the generated key to reuse. NOTE: if the team requires approval and this key is not an owner/admin, the response comes back with status 'awaiting_approval' (approval_status 'pending_approval') and is NOT published until a team owner/admin approves it (solnk_approve_publish).
The solnk-dev/solnk-mcp MCP server provides an MCP interface to Solnkβs social publishing API. It lets an MCP client work with connected social accounts and publish one piece of content to one or more supported platforms: X, Instagram, TikTok, YouTube, Facebook, LinkedIn, Pinterest, Threads, and Bluesky.
Publishing can happen immediately, at a future time, or as a draft for later confirmation. Teams can also require owner or administrator approval before content enters the publishing queue. The server exposes operations for listing publishes, checking status, editing drafts or pending scheduled posts, rescheduling, cancelling, unscheduling, retrying failed targets, and reviewing post analytics.
The hosted endpoint is https://mcp.solnk.com/mcp. A client connects over MCP and sends a Solnk API key as a bearer token. The implementation is a stateless proxy: credentials are supplied with requests and are not stored by the Worker. Solnk handles authentication, permissions, team scope, and usage limits.
Clients should list connected accounts before publishing to obtain account IDs, and check usage before attempting a publish. Media can be supplied from a public URL, or uploaded from a local file through a presigned URL followed by confirmation. A local upload supports images and videos up to 500 MB, with the documented PNG, JPEG, WebP, GIF, MP4, and MOV formats.
The solnk-dev/solnk-mcp MCP server also supports MCP discovery without an API key. Calling initialize or tools/list reveals the tool surface, but an API key is needed for publishing operations.
For normal use, connect an MCP client to the hosted endpoint and provide a Solnk API key created in Solnkβs API-key settings. Clients with native Streamable HTTP support can connect directly and set the authorization header. Other clients can use an MCP-compatible remote HTTP bridge in their client configuration.
For self-hosting, the repository provides a Cloudflare Worker. Install dependencies with pnpm install, run local development with pnpm dev, and deploy with pnpm deploy. SOLNK_API_BASE in wrangler.toml controls the upstream Solnk API and defaults to https://api.solnk.com/api/v1. No deployment-time secret is required because the API key arrives from the client.
A publish may remain in awaiting_approval when team approval is enabled and the API-key holder is not an owner or administrator. Deleting a team moves supported content to a destination team, removes related memberships and credentials, and revokes the current API key, requiring reconnection with a destination-team key. Draft cancellation is unavailable once a publish is queued, processing, or published. The repository is MIT-licensed.
Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/solnk-dev-solnk-mcp)<a href="https://allmcps.com/mcp/solnk-dev-solnk-mcp"><img src="https://allmcps.com/api/badge/solnk-dev-solnk-mcp?style=directory" alt="Solnk MCP on AllMCPs" /></a>