MCP

UniPost exposes a hosted Model Context Protocol server so agents can list accounts, validate content, publish posts, and inspect analytics through one tool layer instead of seven separate platform APIs.

What MCP is for

Use MCP when your product or workflow already runs AI agents. Instead of teaching a model the exact request shapes, limits, and quirks of every social network, you give it one consistent interface for accounts, posts, validation, and analytics.

Transport and endpoint

Available tools

Important: the current MCP surface is strongest for account lookup, text publishing, analytics, and media that is already reachable by URL or already uploaded into UniPost. Large local video files are not the ideal path today.

Recommended flow

The best MCP workflow is not “generate text, then publish immediately.” The safer pattern is generate, validate, preview if needed, then publish.

YouTube video workflow

For YouTube specifically, the most reliable flow today is: upload the video into UniPost’s media library first, then create the post with a media_id. That matches the dashboard flow and avoids trying to push a large local file through an MCP client or base64 payload.

If you are posting from an agent, UniPost should ideally hide these steps behind one higher-level video publish flow. UniPost now exposes unipost_create_youtube_video_post for that wrapper, but for very large local files the most reliable path is still a hosted video_url or a reusable media_id.

Client configuration

Here is the part that was missing: each client expects this config in a different place. Copy the matching snippet into the file below, then restart the client.

Important: ~/Library/Application Support/Claude/claude_desktop_config.json is the Claude Desktop config file. Claude Code uses the claude mcp add command or Claude Code settings files such as ~/.claude/settings.json and .claude/settings.json.

{
  "mcpServers": {
    "unipost": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.unipost.dev/mcp",
        "--header",
        "Authorization:Bearer YOUR_API_KEY",
        "--transport",
        "http-only"
      ]
    }
  }
}

Test the server directly

If you want to confirm auth and transport outside an MCP client, initialize the server directly with cURL.

curl -X POST https://mcp.unipost.dev/mcp \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "capabilities": {},
      "clientInfo": { "name": "test", "version": "0.1.0" }
    }
  }'

When to use MCP vs SDK vs raw API