Agent API · MCP server
Let your AI assistant run your social media.
›
Quick start
Three steps to your first call
- 1Create a keyOrganization → API Keys. Pick one workspace, the accounts and the permissions. The key is shown once.
- 2Call the API or add the MCP serverUse the REST API from code, or add the MCP URL to an AI assistant that supports remote MCP servers.
- 3Watch it in the activity logEvery call is audited, rate-limited and checked against the key’s permissions.
{
"mcpServers": {
"luminobot": {
"url": "https://app.luminobot.com/api/v1/mcp/",
"headers": { "Authorization": "Bearer <your API key>" }
}
}
}Every field and response is documented in the interactive reference at /api/v1/docs.
MCP server
42 tools, grouped
Same keys and limits as the REST API.
Publishing 13
- list_accounts
- create_draft
- schedule_post
- schedule_draft
- get_post
- cancel_post
- delete_post
- suggest_post_times
- list_hashtag_groups
- list_post_reminders
- complete_post_reminder
- assign_post
- list_my_posts
Media 3
- search_media
- get_media
- upload_media
Analytics 3
- get_account_analytics
- get_post_analytics
- get_insights
Inbox 9
- list_conversations
- get_conversation
- list_saved_replies
- reply_to_message
- private_reply_to_comment
- update_message
- get_csat
- list_inbox_teams
- route_to_team
Contacts 5
- search_contacts
- get_contact
- set_contact_consent
- list_segments
- export_contact_data
AI 6
- suggest_reply
- summarise_conversation
- translate_message
- write_captions
- list_ai_actions
- decide_ai_action
Ads 3
- list_ad_accounts
- get_ad_insights
- list_ad_leads
REST API
/api/v1/ routers
- A key belongs to one workspace and an explicit list of accounts
- Keys hold a subset of the issuer’s permissions, re-checked on every call
- Keys can expire, are shown once and stored hashed
- Every call is written to the activity log
- Rate limits per key, per workspace and per account per day
- Idempotency-Key on sends, so retries never double-post
Not available through the API or MCP yet: workflows, broadcasts and drips, reports and billing.
| /me | The key’s scope |
|---|---|
| /accounts | Accounts the key can use, with limits and first-comment support |
| /posts | Create a draft or scheduled post with per-network options; read, update, schedule, cancel, delete; who’s on a post and its ready-by date; “assigned to me” |
| /media | Upload (multipart), list, read processing status |
| /analytics | Account summary (7–90 days), post metrics and AI insights |
| /inbox | Conversations, threads, filled saved replies, reply, private reply, status / assignee / priority, CSAT, teams |
| /contacts | List, read, set consent, privacy export, erase |
| /segments | Saved segments with live sizes |
| /ai | Suggest reply, rewrite, summary, translate, captions, brand voice |
| /ai/actions | AI Employee actions awaiting approval — approve or reject |
| /publishing | Best times, hashtag groups, “Remind me” posts |
| /ads | Ad accounts, insights, leads, ad referrals (read-only) |
| /mcp | The MCP transport |
Any client that supports remote MCP servers over streamable HTTP with a bearer token header.
Only what you allow: one workspace, an explicit list of accounts and a subset of your own permissions, re-checked on every call.
Yes — per key, per workspace and per account per day, matching each network’s own posting limits (for example Instagram 25 and TikTok 15 posts per 24 hours).
No. Messaging-window refusals and expired connections return a 409 with an actionable message.
Made for agencies, support teams, creators, small businesses, online stores.
Run your social media from one calm workspace.
Start on the Free plan, connect your channels and invite your team when you’re ready.
Free plan · No credit card · Billed per workspace