Remote MCP server

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.

Start freeSee the available tools ↓
Remote server ready

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

Create an API key

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_publish

Create a draft, schedule a post, or publish immediately.

solnk_confirm_publish

Release a reviewed draft immediately or schedule it.

solnk_get_publish_status

Check aggregate and per-destination delivery status.

solnk_list_accounts

See which social accounts are available to the agent.

solnk_create_media_upload

Start a local image or video upload for publishing.

The agent prepares a draftPrepared
You review it in SolnkYour decision
Solnk publishes to selected accountsDelivered

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.

Read the API documentation ↗

MCP client config

mcp.solnk.com/mcp
{
  "mcpServers": {
    "solnk": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.solnk.com/mcp",
        "--header",
        "Authorization: Bearer sk_..."
      ]
    }
  }
}

MCP 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 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, Claude Code, Cursor, and other clients that support remote MCP servers can connect. If a client needs a local bridge, the setup instruction asks the agent to choose the appropriate configuration method.

Copy the setup instruction at the top of this page into your AI client. It will use https://mcp.solnk.com/mcp, ask for a Solnk API key when needed, configure the client, and verify the available tools.

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.

Create free accountExplore Developers