Works with Claude, Cursor, Windsurf, and other MCP-ready assistants.
Sign in from your AI app (paid plans, from Beginner) and it can publish, schedule, check and retry posts on TikTok, Instagram, YouTube, LinkedIn, Facebook, X, Threads, Pinterest, and Skool, and read post numbers where the network reports them (not Skool). An rl_* key works on every plan with five tools for media and posting. For automation, publish through our HTTPS API with n8n, Zapier, Make, Bolt, or your own runners.
~/.cursor/mcp.json
{
"mcpServers": {
"status200-uploads": {
"url": "https://mcp.status200uploads.com/mcp",
"headers": {
"Authorization": "Bearer rl_your_api_key"
}
}
}
}Agents connect over HTTPS.
Cursor reads MCP definitions from ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project. Use the hosted URL, not a filesystem path.
.cursor/mcp.json
{
"mcpServers": {
"status200-uploads": {
"url": "https://mcp.status200uploads.com/mcp",
"headers": {
"Authorization": "Bearer rl_your_api_key"
}
}
}
}Interactive preview
Watch the composer type and send, then tool calls. Each API step shows Working... then Success, Queued, or Failed inline; longer assistant replies appear in the thread. One wrap-up per example. this is how realistic and effortless working with Status 200 Uploads through MCP can look in practice.
Typing in composer below...
Simulated composer; demo types automatically
The tools an AI app gets, grouped by what they do. An app that signed in gets the first five groups; a client that sends an rl_* key gets the last row. The posting and media endpoints behind them are documented on /docs/api.
| Group | MCP tools (monospace names) | Notes |
|---|---|---|
| Accounts | status200_list_accounts, status200_get_usage, status200_get_posting_options | Your profiles and networks, your plan and what is left of it, and what each network really allows (TikTok privacy choices, Pinterest boards, Skool groups). |
| Media | status200_upload_media_from_url, status200_get_media_status | Import a file from a URL, then check it until it is ready to post. |
| Publishing | status200_validate_post, status200_publish_post, status200_retry_post | Check a post without sending it, publish to up to ten places in one call, and send a failed post again. |
| Scheduling | status200_schedule_post, status200_update_scheduled_post, status200_cancel_scheduled_post | Put a post on the calendar, change it, or cancel it before it goes out. |
| History | status200_get_post, status200_list_posts, status200_get_post_performance | What happened to a post, your post history, and the numbers each post earned. |
| With an rl_* key | status200_server_info, status200_create_post, status200_create_post_site_v2, status200_upload_media_from_url, status200_get_media_status | A client that sends an API key instead of signing in gets these five: publish through the older URL or /api/v2/posts, import media, and check the connection. |
Signing in is part of the paid plans (from Beginner); an rl_* key works on every plan. n8n, Zapier, and Make use the REST API, which publishes posts, schedules them (post.scheduledFor), cancels a scheduled post (DELETE) and imports media.
The Model Context Protocol lets assistants open a small, typed bridge to your tooling. An app that signs in to Status 200 uploads gets 14 MCP tools to publish, schedule, check and retry posts and read their numbers (an rl_* key gets five); pipelines use the REST API you automate below.
Paste one JSON snippet, restart MCP in your IDE, and reuse the hosted endpoint; same pattern Cursor, Claude-compatible clients, and Windsurf workflows expect.
Platform workbench →Signing in needs no key: you approve the app on our page and choose read-only or read and publish (paid plans). A client that cannot sign in sends an rl_* dashboard key over HTTPS instead, on every plan.
MCP reference →A signed-in app gets 14 tools: accounts, media, a check before posting, publish, schedule, retry, history and post numbers. An rl_* key gets five tools for media and posting. n8n, Zapier and Make use the REST API, which publishes and schedules posts and imports media.
Platform workbench →Hosted gateway for assistants, curls for pipelines; social accounts and rl_* billing stay unified no matter where you automate.