Give your AI a safe way to publish.
Connect Codex, Claude Code, Cursor, or another MCP client to one reviewed workflow for drafts, schedules, media, and publishing across nine social platforms.
Let your AI connect Solnk.
Copy one instruction into Codex, Claude Code, Cursor, or another MCP-capable agent. It will choose the correct configuration method, ask for your key, and verify the tools.
Set up Solnk as a remote MCP server in the AI client I am using.
https://mcp.solnk.com/mcp
Tools that feel native to the conversation.
Your agent calls the right Solnk tool while you stay in the client where the work already happens.
solnk_publishCreate a draft, schedule a post, or publish immediately.
solnk_confirm_publishRelease a reviewed draft immediately or schedule it.
solnk_get_publish_statusCheck aggregate and per-destination delivery status.
solnk_list_accountsSee which social accounts are available to the agent.
solnk_create_media_uploadStart a local image or video upload for publishing.
solnk_list_teamsList owned teams and identify the selected default team.
solnk_set_default_teamChoose which owned team is used as the default fallback.
solnk_delete_teamDelete an extra team with explicit confirmation and content migration.
Let it draft. Keep the last word.
Start with draft creation and human approval. Direct publishing stays available when the workflow has earned your trust, while scoped API keys control what each agent can access.
Create a scoped API key ↗Configure it manually when you need control.
Native remote-MCP clients can use the server URL and Bearer key directly. Other clients can connect through the localmcp-remotebridge.
Codex
Add this to ~/.codex/config.toml, then run codex mcp login solnk.
[mcp_servers.solnk]
url = "https://mcp.solnk.com/mcp"
auth = "oauth"
default_tools_approval_mode = "writes"Cursor / Claude Code
This form avoids the known Windows argument-spacing problem.
{
"mcpServers": {
"solnk": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://mcp.solnk.com/mcp",
"--header",
"Authorization:${SOLNK_AUTH_HEADER}"
],
"env": {
"SOLNK_AUTH_HEADER": "Bearer sk_..."
}
}
}
}ChatGPT web
Open Plugins or developer mode, add the public endpoint, and complete OAuth. Access depends on your ChatGPT account and workspace policy.
https://mcp.solnk.com/mcpMCP or the REST API?
Use MCP
Choose MCP when you want Codex, Claude Code, Cursor, or another AI client to call publishing tools inside the conversation.
Use the REST API
Choose the API for your own product, backend service, n8n flow, or scheduled automation. Explore the AI agent API.
MCP FAQ
It is a hosted Model Context Protocol server that gives an MCP-compatible AI agent Solnk publishing tools. The agent can create drafts, schedule posts, publish, list connected accounts, and attach media without custom API wiring.
Codex connects directly over Streamable HTTP with OAuth or a Bearer key. Cursor and Claude Code can connect directly when their version supports remote MCP, or through mcp-remote. ChatGPT web uses plugins or developer-mode connections, and availability depends on the account and workspace policy.
Use https://mcp.solnk.com/mcp and follow the client-specific configuration on this page. Prefer OAuth when the client supports it. Use a scoped Solnk API key only for clients that require manual Bearer authentication.
Only if your workflow and key permissions allow it. Draft-first is the recommended default: let the agent prepare the post, review it in Solnk, and enable direct publishing only after you trust the workflow.
Use MCP when an AI client should call publishing tools for you. Use the REST API when you are building your own product, backend integration, or automation. Both reach the same publishing layer.
MCP and API access are included with paid plans. You can start with a free account, connect your social accounts, and prepare the workflow before upgrading.
Give your agent the connection. Keep control of the publish.
Create an account, connect your social profiles, and let your AI prepare the first reviewed draft.