Access, auth, and limits
There is no tier-gating to navigate here, which is unusual. Outstand sells one public plan, so MCP access comes with any account at the $19 a month base and costs nothing extra. Posts fired through an agent draw on the same 3,000-post monthly allowance as posts fired through REST, then bill at $0.007 each up to 10,000 and $0.005 above that. The practical consequence is worth saying out loud: an agent in a retry loop spends real money, so the idempotency keys on post creation are a billing safeguard as much as a correctness one.
Auth comes in two shapes. One-click OAuth is the path for ChatGPT, Claude, Cursor and Windsurf, where you add the connector and sign in. For headless or CLI setups you pass a Bearer key instead, and the vendor publishes the exact Claude Code command: claude mcp add -t http -H "Authorization: Bearer ost_your_key" outstand https://mcp.outstand.so/mcp. Probed on 2026-07-20, an unauthenticated call to the endpoint returns 401, so the auth gate is real and the server is live.
Where it works and what to build
Because it is a remote HTTP server rather than a local stdio binary, client support is broad and boring in the good way. ChatGPT, Claude Desktop, Claude web, Claude Code, Cursor and Windsurf are all named by the vendor, with Claude Desktop and Cursor using an mcp-remote wrapper config and everything else connecting directly. Nothing to install per machine, nothing to version-pin.
The workflow it actually earns its place in is the boring operational one, not the demo. Telling an agent to post the same announcement to X and LinkedIn now and schedule it on Threads for 9am tomorrow works, but so does asking it which of last month's posts pulled the most engagement, then drafting follow-ups off the answer, because analytics reads are tools too. For agencies the interesting bit is that connected accounts are unlimited and free, so pointing an agent at forty client profiles does not change the bill.
Which AI clients can use Outstand MCP?
Not every AI assistant supports MCP natively. Per-client picture for Outstand:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Add as a custom connector and sign in with one-click OAuth. |
| Claude Code | Native MCP | Vendor publishes a one-line claude mcp add -t http command with a Bearer key. |
| ChatGPT | Native MCP | Listed as a supported one-click OAuth client. |
| Cursor | Native MCP | Vendor documents an mcp-remote wrapper config with a bearer header. |
| Windsurf | Native MCP | Named on the vendor's supported-client list. |
How to connect Outstand MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.outstand.so/mcp
// Claude Code (one-liner): claude mcp add outstand <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.outstand.so/mcp.
Does Outstand MCP cost extra?
The Outstand MCP server is community-built — free to run, but you still pay for your Outstand subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your Outstand account still needs whatever plan is required to access the data the MCP server queries.
- Trade-off: zero MCP cost, but no guarantee it'll keep working when Outstand changes their UI or API.
Outstand also publishes a REST API
Outstand publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Outstand from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Outstand data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Outstand account
- Multi-account workflows without context-switching the Outstand UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Outstand data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Outstand safe
Limits and gotchas
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying Outstand API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
One of the better social MCP servers you can point an agent at, because it is the product rather than a demo of the product. Real remote endpoint, one-click OAuth, same 11 networks as the API, and idempotency keys underneath so a retrying agent does not double-post. The wobbling tool count is a documentation smell, not a functional one, but it is the sort of thing worth checking against the live tool list before you build around a specific tool name.
Scored by Joonas (TMB).
Outstand MCP & API FAQ
Is the Outstand MCP server official?+
Can I use the Outstand MCP with Cursor or Codex?+
Does Outstand support webhooks?+
Sources
- Outstand official site: https://www.outstand.so
- MCP server page: https://mcp.outstand.so/mcp
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

