Back

MCP Server

Give your coding agent a way to post

Add one connection with your API key, and Claude Code, Cursor, or any MCP-compatible client can list accounts, read your brand kit, generate images, and publish, without you writing a REST client by hand.

Get the Agent SkillNot a coding agent? See the API →

MCP-compatible coding agents

Claude CodeCursorVS CodeCodexAmpGemini CLIOpenCodeWarpWindsurfZedOpenClawHermes
Xroad Studio MCP Server

9 social platforms

InstagramTikTokYouTubeFacebookXLinkedInPinterestThreadsBluesky

What MCP actually is

MCP (Model Context Protocol) is an open standard, originally released by Anthropic, that lets AI models call external tools directly instead of you copy-pasting instructions back and forth. Anthropic describes it as a USB-C port for AI applications: one connector, many devices.

For Xroad Studio, that means your coding agent gets a menu of real actions, list your accounts, read your brand kit, generate an image, publish a post, pull analytics, instead of a wall of API documentation it has to interpret and hope it got right.

Think of the Xroad MCP server as a convenience layer, not a new technology to learn. MCP is the connector, we are the implementation that turns it into list an account, read a brand kit, publish a post, with nothing to configure per platform.

Why this matters, not just for developers

Without MCP, per project

  • →Write and maintain a client for our REST API in your own codebase
  • →Re-explain your account IDs and brand kit to the agent every session
  • →Look up the right endpoint and payload shape for every action
  • →Do this again for every new agent or project you start

With the Xroad MCP server

  • →Connect once, in your agent's settings, with a single API key
  • →The agent discovers create_post, get_brand_kit, and the other 11 tools on its own
  • →No endpoint shapes to look up, the tool call is the documentation
  • →Same connection works in every project going forward

All 13 tools

The exact same tools Xroad Studio uses internally, exposed directly to your agent. Same errors, quotas, and plan rules as the REST API.

Accounts

list_accounts

List connected social accounts and their IDs

get_connect_url

Generate an OAuth URL for connecting a new social account

Publishing

create_post

Publish now or schedule a post to connected accounts

list_posts

List posts with status and date filters, paginated

get_post

Get one post and its current status

update_post

Edit a post that is still scheduled

cancel_post

Cancel a scheduled or processing post

Media & images

upload_media

Re-host an expiring URL (max 20 MB) onto the permanent Xroad CDN

generate_image

Generate one AI image and wait for the finished URL

get_image_status

Check an image job that is still running

Brand kit

list_brand_kits

Read sanitized brand voice, colors, audience, offer, banned words

get_brand_kit

Get one brand kit by ID

Analytics

get_analytics

Normalized performance metrics per account (Creator and Business plans)

Setup

Generate an API key in Settings → API Keys, then add the server to your client.

Claude Code

claude mcp add --transport http xroad-studio https://xroadstudio.com/api/mcp \
  --header "Authorization: Bearer $XROAD_API_KEY"

Cursor

Add to .cursor/mcp.json

{
  "mcpServers": {
    "xroad-studio": {
      "url": "https://xroadstudio.com/api/mcp",
      "headers": { "Authorization": "Bearer xrd_live_<your-key>" }
    }
  }
}

Claude.ai / Claude Desktop

Settings → Connectors → Add custom connector (no custom header support, so the key goes in the URL)

https://xroadstudio.com/api/mcp?key=xrd_live_<your-key>

n8n

MCP Client Tool node, Header Auth

Endpoint: https://xroadstudio.com/api/mcp
Auth header: Authorization: Bearer xrd_live_<your-key>

VS Code, Codex, Amp, Gemini CLI, OpenCode, Warp, Windsurf, Zed, and any other MCP-compatible client connect the same way, point the client at https://xroadstudio.com/api/mcp with an Authorization: Bearer header, following that client's own MCP config format.

Not using a coding agent? ChatGPT Custom GPTs work better through the REST API and OpenAPI schema than MCP.

Frequently asked questions

No. Generate an API key in Settings, then connect with a Bearer token in the Authorization header. Clients that cannot set custom headers can pass the key in the URL instead.

Your brand. One platform. Always on

Create, edit, and post from a single studio.

Start for free

MCP access from Starter plan. Cancel anytime.