Adding Outstand to Claude used to start with a URL. You opened connector settings, chose Add custom connector, pasted https://mcp.outstand.so/mcp, and signed in. It worked, and it asked you to trust a link.
As of today you can find it in Claude's connector directory instead: claude.ai/directory/outstand. Same server, same 28 tools, no URL to paste.
What changed, and what did not
The server itself did not change. It has been live at https://mcp.outstand.so/mcp since March 2026, and anyone who added it by hand is already on the listed one — nothing to re-add, nothing to migrate.
What changed is where it lives. A directory listing means Claude finds the connector where you already look for connectors, and it means the listing went through Anthropic's review rather than arriving as a link from a stranger. Pasting a URL into a client that is about to act on your social accounts is a reasonable thing to hesitate over. That step is gone.
The 28 tools
One connection gives Claude the full publishing surface. Grouped by the job they do:
- Posting and scheduling (7) — create a post, update it, list and fetch posts, delete one from Outstand or from the network itself, and repost.
- Accounts (6) — list connected accounts, fetch one, disconnect one, start an OAuth flow for a new one, connect Bluesky, and list Pinterest boards.
- Media (5) — request an upload URL, confirm the upload, then list, fetch or delete what you have uploaded.
- Credentials (5) — create, list, fetch, update and delete the OAuth applications behind your own networks, for anyone running bring-your-own-keys.
- Analytics (3) — per-post metrics, per-account metrics, and your own usage against quota.
- Replies (2) — reply to a comment, and read the replies on a post.
The full list, tool by tool, is on the Claude connector page. It is also machine-readable: the server publishes an MCP server card at /.well-known/mcp/server-card.json with all 28 names in it, so an agent can read the surface before it calls anything.
One sign-in, and no key to copy
In Claude on web, desktop and mobile there is no API key in the flow at all. You click through a browser sign-in, pick which Outstand organization and which accounts Claude may act on, and that is the setup.
Underneath, that is OAuth 2.1 the way the MCP spec describes it. Call the server without a token and it tells you where to authenticate:
1curl -i -X POST https://mcp.outstand.so/mcp \
2 -H 'Content-Type: application/json' \
3 -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'
4
5HTTP/2 401
6www-authenticate: Bearer resource_metadata="https://mcp.outstand.so/.well-known/oauth-protected-resource/mcp"Follow that pointer and you get the protected-resource metadata:
1{
2 "resource": "https://mcp.outstand.so/mcp",
3 "authorization_servers": [
4 "https://www.outstand.so/app"
5 ],
6 "bearer_methods_supported": [
7 "header"
8 ],
9 "scopes_supported": [
10 "openid",
11 "profile",
12 "email",
13 "offline_access"
14 ],
15 "resource_name": "Outstand",
16 "resource_documentation": "https://www.outstand.so/docs/mcp"
17}The authorization server exposes a registration endpoint, so Claude registers itself and exchanges the code for a scoped token. Nothing is ever shown to you to copy, because nothing needs to be. Revoke the token in Outstand and Claude loses access without touching your API keys or your social logins.
Claude Code is the exception, and for a dull reason: it is headless, so there is no browser to finish a sign-in in. There it takes an Outstand API key as a bearer token in one command:
1claude mcp add -t http \
2 -H "Authorization: Bearer ost_your_key" \
3 outstand https://mcp.outstand.so/mcpThe Claude Code page covers that setup on its own.
Twelve platforms, and the four that need your own credentials
The connector covers X (Twitter), LinkedIn, Instagram, TikTok, Facebook, Threads, Bluesky, YouTube, Pinterest, Google Business Profile, Vimeo and Reddit. One request shape publishes to all of them, and analytics come back in one schema regardless of which network produced them.
Eight of those connect on Managed Keys, which are included on every plan: LinkedIn, Instagram, Facebook, Threads, Bluesky, YouTube, Pinterest and TikTok. You connect the account and Outstand supplies the platform OAuth application.
Four need credentials you own — X (Twitter), Google Business Profile, Vimeo and Reddit. That is each platform's rule about who may hold an app, not a tier we invented, and it is the one part of setup that takes longer than a minute. Worth knowing before you promise Claude a cross-post to X.
Honest limits
Outstand publishes; it does not listen. Claude cannot use this connector to browse timelines, track a competitor or scrape anyone else's posts, and the analytics it reads back cover posts published through Outstand — not your whole account history. If you wanted a listening tool, this is not one, and no amount of asking Claude nicely will change that.
Every claim above is dated and restated on the facts page, which is the version to quote if something you read elsewhere disagrees.
Start here
Open the directory listing and connect it, then ask Claude to publish something. The connector page has the full capability list and the three setup routes; the MCP docs have the tool reference. If you want the longer version of why one connector beats a stack of single-platform MCP servers, we wrote that up in which social media MCP servers actually publish, and there are walkthroughs for posting to LinkedIn and for uploading video to YouTube from a chat.
Claude could already write the post. Now it can send it, and you no longer have to find it to try.