Works with Claude, Cursor, Windsurf, and other MCP-ready assistants.
Four MCP tools for diagnostics, media, and posting across TikTok, Instagram, YouTube, LinkedIn, Facebook, X, Threads, and Pinterest. Scheduling, analytics, deletes, and glue logic stay on 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
Four registered tools grouped by publishing, media, and diagnostics. Profiles, deletes, polls, listing tabs, and other automation-heavy routes ship on /docs/api.
| Group | MCP tools (monospace names) | Notes |
|---|---|---|
| Publishing | status200_create_post, status200_create_post_site_v2 | Edge `api-posts` routes plus queued-friendly site `/api/v2/posts`. |
| Media | status200_upload_media_from_url | Queue remote assets into reusable file IDs. |
| Diagnostics | status200_server_info | Confirm bases + masked key hint before deeper calls. |
Automations via n8n, Zapier, and Make cover the broader REST cookbook above: profiles, deletes, polls, and tab-specific routes live in Full API docs.
The Model Context Protocol lets assistants open a small, typed bridge to your tooling. Status 200 uploads exposes four MCP tools for diagnostics, media ingestion, and post creation; the rest of our product stays on honest REST curves 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 →Each teammate sends their own rl_* dashboard key over HTTPS during MCP initialize.
MCP reference →The bridge exposes publishing + media primitives; everything else maps to documented REST curves you can automate with n8n, Zapier, or Make from the platform workbench tabs.
Platform workbench →Hosted gateway for assistants, curls for pipelines; social accounts and rl_* billing stay unified no matter where you automate.