Solnk MCP
Publish and schedule content via Solnk to X, Instagram, TikTok, YouTube, LinkedIn and more, with drafts, media upload and post analytics.
Installation
Les étapes d'installation sont dans la documentation ci-dessous. Documentation
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Solnk MCP
A Model Context Protocol server for Solnk — let any MCP client (Claude, Cursor, your own agent) publish and schedule content across 9 social platforms through one tool surface: X, Instagram, TikTok, YouTube, Facebook, LinkedIn, Pinterest, Threads, and Bluesky.
It's a thin, stateless proxy to the Solnk public API: your API key is forwarded per request, and all auth/scope/quota enforcement happens server-side. No credentials are stored in this Worker.
Hosted endpoint
A managed instance runs at:
https://mcp.solnk.com/mcp
Authenticate with a Solnk API key as a bearer token. Create one at **https://solnk.com/settings/api-keys**.
Authorization: Bearer sk_...
Connect a client
Most MCP clients reach a remote HTTP server through mcp-remote. Example config (Claude Desktop / Cursor / any client using the standard mcpServers schema):
{
"mcpServers": {
"solnk": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.solnk.com/mcp",
"--header",
"Authorization:Bearer ${SOLNK_API_KEY}"
],
"env": {
"SOLNK_API_KEY": "sk_your_key_here"
}
}
}
}
Clients with native Streamable HTTP support can connect to https://mcp.solnk.com/mcp directly and set the Authorization: Bearer sk_... header.
Tools
| Tool | What it does |
|---|---|
solnk_list_accounts | List connected social accounts (id, platform, username, status, capabilities). Call first to get account_ids. |
solnk_get_usage | Plan limits and current usage — check can_publish before posting. |
solnk_publish | Publish to one or more platforms in a single request (immediate, scheduled, or draft). |
solnk_confirm_publish | Confirm a draft so it goes out, now or scheduled. |
solnk_cancel_publish | Cancel a draft or not-yet-sent scheduled publish. |
solnk_get_publish_status | Aggregate status of a publish. |
solnk_list_publishes | List recent publishes with filters. |
solnk_get_post_analytics | Rolled-up or per-platform post metrics, including live post URLs. |
solnk_create_media_upload | Presigned upload for a local image/video file (3-step flow). |
solnk_confirm_media_upload | Finalize a presigned upload. |
solnk_create_media_from_url | Ingest an image/video by public URL in one call. |
Full request/response shapes and per-platform options live at developers.solnk.com.
Self-hosting
The server is a single Cloudflare Worker.
pnpm install
# Local dev — point at your own Solnk API base if needed
# (edit SOLNK_API_BASE in wrangler.toml, e.g. http://localhost:3002/api/v1)
pnpm dev
# Deploy to your own Cloudflare account
pnpm deploy
wrangler.toml:
SOLNK_API_BASE— the Solnk public API the tools proxy to (defaults tohttps://api.solnk.com/api/v1).routes— bind your own custom domain.
No secrets are needed at deploy time; the API key is supplied by the client at request time.
Discovery without a key
MCP discovery (initialize / tools/list) is open — clients, inspectors, and directories can introspect the tool surface without an API key. A key is only required to actually invoke a publishing tool. A Dockerfile is included so the Worker can be built and run locally (wrangler dev, no Cloudflare login) for introspection.
License
MIT © Solnk
Questions fréquentes
Qu'est-ce que Solnk MCP ?
Publish and schedule content via Solnk to X, Instagram, TikTok, YouTube, LinkedIn and more, with drafts, media upload and post analytics.
Comment installer Solnk MCP ?
Suivez les étapes d'installation de sa documentation, affichée sur cette page et dans son dépôt.
Solnk MCP est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Solnk MCP ?
Il est publié par solnk-dev. AI.tn le référence sans le maintenir ni le recommander.
Issu des listes communautaires awesome-mcp-servers et du dépôt GitHub du projet. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.