MCP overview
MissLess Social ships an MCP server. Point Claude Code, Cursor, Windsurf or any client that speaks the Model Context Protocol at it, and the assistant can list accounts, upload media, create and schedule posts, read the inbox and reply, on one workspace.
Server URL: https://social.missless.tel/v1/mcp
What it can do
Section titled “What it can do”Everything the API can do for one workspace, through 13 tools:
- See which accounts are connected and how many followers they have.
- Create a connect link when an account is missing or expired.
- Upload media from a URL.
- Create posts, schedule them, publish drafts, list and inspect them, cancel them.
- List conversations, read a thread, and send a reply.
The full list with inputs is on Tools.
Typical prompts once connected: “Schedule this photo for Friday 9:00 on Instagram with the caption below”, “Which DMs from today are still unanswered?”, “Reply to the comment asking about prices with our price list”, “Why did yesterday’s post fail?”.
Every write is a real write
Section titled “Every write is a real write”There is no approval queue, no draft-then-confirm layer between the assistant and the API. When the assistant calls create_post without schedule_at or status: "draft", the post is published. When it calls reply_conversation, the message is sent. The MCP server is a thin mapping onto the same endpoints your backend uses; the assistant is a client with a key, nothing more.
Two consequences:
- The assistant’s client is where approval lives. Claude Code and most editors ask before running a tool. Keep that on. If you build your own agent, add a confirmation step for
create_post,publish_postandreply_conversation. - Everything is attributed. Posts created over MCP have
created_by: "mcp", messages havesent_by: "mcp", and your webhook receives the samepost.publishedandmessage.sentevents as for any other surface. Your product sees what the assistant did.
Use workspace keys
Section titled “Use workspace keys”The server accepts a partner key with an X-MissLess-Workspace header, but the recommended credential is a workspace key: a key minted with POST /v1/workspaces/:id/keys that can only reach that workspace.
- A leaked workspace key exposes one customer, not all of them.
- You can mint one per assistant per customer, label it (“Claude Code, Nova laptop”), see
last_used_at, and revoke it alone. - End users can hold it themselves. A customer who wants to drive their own accounts from their own AI client gets a workspace key, never your partner key.
Partner-key access is there for your own operator tooling, where one person legitimately switches between workspaces.
Rate limits and costs
Section titled “Rate limits and costs”MCP calls are API calls. The 300 requests per minute per key limit applies, and Instagram’s 100 posts per 24 hours applies to whatever the assistant publishes. An assistant that lists posts in a loop will hit rate_limited like any other client.