Give your AI agent a social media presence

1. Add the MCP server

Paste this into your client's MCP config, or add the same URL as a custom connector. It prompts you to sign in and pick an organization - no key to copy.

{
  "mcpServers": {
    "outstand": {
      "url": "https://mcp.outstand.so/mcp"
    }
  }
}

2. Or call it directly

One POST publishes everywhere. accounts takes an account id, a network name, or a username, and Outstand resolves each one.

curl -X POST https://api.outstand.so/v1/posts/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Shipped: agents can now post for themselves.",
    "accounts": ["x", "linkedin"]
  }'

3. Then just ask

With the server connected, the model picks the tool and fills the arguments itself. This is the whole interaction.

You: "Post 'Shipped: agents can now post for
      themselves.' to X and LinkedIn."

Agent: create_post({
  content: "Shipped: agents can now post for themselves.",
  accounts: ["x", "linkedin"]
})
→ published

App review before you can post once

Meta and TikTok both gate production posting behind an app review with a screencast, a privacy policy, and a use-case write-up. Outstand ships managed OAuth apps for 8 networks - LinkedIn, Instagram, Facebook, Threads, Bluesky, YouTube, Pinterest, TikTok - so your agent connects an account and posts the same day. Bring your own credentials any time you want your brand on the consent screen.

Token refresh and silent expiry

TikTok access tokens last around 24 hours. Bluesky hands back a session JWT rather than a bearer token. LinkedIn, YouTube, Pinterest, and Google all refresh on different clocks. An agent that stores a token and assumes it keeps working will fail at 3am, quietly, and only tell you when a post never lands. Outstand refreshes and re-resolves credentials on every publish.

Per-network media rules and quirks

Instagram Reels want a cover frame or a thumb offset. TikTok defaults to dropping media in the creator inbox as a draft unless you explicitly ask for a direct post - and direct posts count against a daily cap on distinct publishing creators. Threads takes reply-control settings only at publish time. These are the details that break an agent silently, because the API returns 200 and nothing appears.

Rate limits that surface as failures

Agents burst. They generate ten posts and fire them at once, which is exactly the shape platform rate limiters punish. Outstand queues, throttles, and retries server-side, so your agent does not need retry logic or a 429 handler in its loop.

Every platform schedules differently

Some platforms accept a future timestamp, some do not, some accept one only through a business surface. Outstand normalizes it to a single ISO 8601 scheduledAt field up to 30 days out, and cancels and re-queues the job for you when the agent changes its mind.