MCP Server

Outstand runs a remote MCP (Model Context Protocol) server, so AI agents like Claude, Cursor, and Windsurf can list your accounts, publish posts, and upload media directly — no custom integration code required.

Server URL

https://outstand.one/api/mcp

Uses the same API keys as the REST API — generate one from your dashboard under API & Integrations if you don't already have one.

Connecting a client

Clients with native remote MCP support (Cursor, Windsurf, Claude Code)

Add this to your client's MCP config:

{
  "mcpServers": {
    "outstand": {
      "url": "https://outstand.one/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Claude Desktop (stdio-only, via mcp-remote bridge)

Claude Desktop currently launches local commands rather than connecting to remote URLs directly. Bridge it with mcp-remote:

{
  "mcpServers": {
    "outstand": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://outstand.one/api/mcp",
        "--header", "Authorization:Bearer YOUR_API_KEY"
      ]
    }
  }
}

Available Tools

Tool	Description
`list_accounts`	List connected social accounts and their IDs
`create_post`	Publish or schedule a post to one or more accounts
`list_posts`	List previously created posts, optionally filtered by status
`upload_media_from_url`	Re-host an image/video from a public URL for use in a post

These map 1:1 to the REST API — same auth, same quota, same underlying data.

Example prompt

"List my connected Outstand accounts, then post 'New feature just shipped 🚀' to LinkedIn and Threads."

Your agent calls list_accounts to find the account IDs, then create_post to publish — no manual API key handling inside the conversation once the client's configured.