Setup

Connect the Outstand MCP server to your AI client. There are two ways to authenticate:

1. One-click OAuth (recommended) - add Outstand as a custom connector and sign in with a single click. No API key to copy, no config file to edit. Works with ChatGPT, Claude, Cursor, and any client that supports remote MCP connectors.
2. API key - pass an Outstand API key as a Bearer token. Best for CLI clients and headless setups where a connector UI is not available.

Both methods talk to the same server URL:

https://mcp.outstand.so/mcp

Prerequisites

Before you start, you need:

1. An Outstand account - sign up free.
2. At least one connected social account - connect accounts through the Outstand dashboard or API.
3. For the API key method only: an API key from your dashboard. API keys start with ost_.

One-click OAuth (custom connector)

Add Outstand as a custom connector in your client and authorize it in the browser. The flow is the same everywhere:

1. Add a new custom connector / MCP server and paste the URL https://mcp.outstand.so/mcp.
2. Your client opens Outstand in a browser. Sign in (or create an account).
3. Choose which organization the connector should access, then approve.
4. You are redirected back to your client with the connection live. The Outstand tools are ready to use.

No API key, no mcp-remote bridge, and no config file to edit. The steps below show where to add the connector in each client.

ChatGPT

1. Make sure connectors/developer mode is enabled for your account (Settings → Connectors).
2. Go to Settings → Connectors → Create (or Add custom connector).
3. Set the MCP server URL to https://mcp.outstand.so/mcp and save.
4. Click Connect on the Outstand connector and complete the sign-in and organization selection in the browser.
5. Enable the connector in a chat to give ChatGPT access to the Outstand tools.

Claude (Desktop & Web)

1. Open Settings → Connectors.
2. Click Add custom connector.
3. Give it a name (for example, Outstand) and set the URL to https://mcp.outstand.so/mcp.
4. Click Connect and complete the OAuth sign-in and organization selection.
5. The Outstand tools now appear in the tools menu of any chat.

Cursor

1. Open Settings → MCP → Add new MCP server (or edit .cursor/mcp.json).
2. Add the Outstand server using its URL:

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

3. Cursor detects that the server requires authorization and prompts you to sign in. Complete the OAuth flow in the browser and pick your organization.

Grok Bot

1. Open Settings → Plugins in Grok Bot and add a custom connector.
2. Set the Server URL to https://mcp.outstand.so/mcp and leave the headers blank - do not add an Authorization header.
3. Grok Bot detects that the server requires authorization and opens the sign-in flow itself. Complete it and pick your organization.
4. The connector is available account-wide across your Bots.

Any client with connector support

Any MCP client that supports remote servers with OAuth can connect the same way:

• Server URL: https://mcp.outstand.so/mcp
• Transport: Streamable HTTP (MCP revision 2026-07-28; clients on the 2025 revisions are still supported)
• Authentication: OAuth 2.0 (the server advertises its authorization server via RFC 9728 protected-resource metadata, so compatible clients discover the sign-in flow automatically)

When the client first connects it receives a 401 with a pointer to Outstand's authorization server, opens the browser for you to sign in and pick an organization, and stores the resulting access token. Everything after that is automatic.

API key (Bearer token)

If your client does not support custom connectors - or you prefer a headless setup - authenticate with an Outstand API key passed as a Bearer token.

Claude Code

The fastest way to connect with a key. Run this single command:

claude mcp add -t http \
  -H "Authorization: Bearer ost_your_key" \
  outstand https://mcp.outstand.so/mcp

Replace ost_your_key with your actual API key. That's it - Outstand tools are now available in your Claude Code sessions.

Verify the connection

claude mcp list

You should see outstand listed with the MCP server URL.

Claude Desktop (with an API key)

If you would rather pass a key than use the connector UI, Claude Desktop can reach the server through the mcp-remote bridge.

Step 1: Install mcp-remote

The MCP server uses streamable HTTP transport, which the bridge exposes to Claude Desktop:

npm install -g mcp-remote

Step 2: Edit your configuration

Open your Claude Desktop configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the Outstand server to the mcpServers section:

{
  "mcpServers": {
    "outstand": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.outstand.so/mcp",
        "--header",
        "Authorization: Bearer ost_your_key"
      ]
    }
  }
}

Step 3: Restart Claude Desktop

Quit and reopen Claude Desktop. You should see the Outstand tools available in your tool list.

Cursor / Windsurf (with an API key)

Create .cursor/mcp.json (Cursor) or .windsurf/mcp.json (Windsurf) in your project root:

{
  "mcpServers": {
    "outstand": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.outstand.so/mcp",
        "--header",
        "Authorization: Bearer ost_your_key"
      ]
    }
  }
}

Restart the editor (or reload the window) to pick up the new server.

Zapier

Zapier's MCP Client app connects a Zap to any remote MCP server.

1. Go to Apps → + Add connection, search for MCP Client, and click Add connection.
2. Set Server URL to https://mcp.outstand.so/mcp.
3. Set Transport to Streamable HTTP.
4. Leave OAuth set to no. If you answer yes, Zapier ignores the Bearer Token field.
5. Paste your key into Bearer Token. The field takes the key itself (ost_your_key), not a full Bearer ... header value.
6. Save the connection. The Outstand tools are then available as actions in your Zaps.

The key is stored in that Zapier connection, on Zapier's infrastructure. Create a key named zapier for it so you can revoke it from Settings → API Keys without disturbing your other integrations.

Make

Make's MCP Client app has two modules: Call a tool, which runs a named Outstand tool, and Execute an action with AI, which lets a model pick the tool.

1. Add an MCP Client module to your scenario and create a new connection.
2. Under MCP Server, choose + new mcp server and set the URL to https://mcp.outstand.so/mcp.
3. Paste your key into API key / access token.
4. Save. Make loads the Outstand tool list over the connection, and you pick the tool you want from it.

The key is stored in that Make connection, on Make's infrastructure. Create a key named make for it so you can revoke it from Settings → API Keys without disturbing your other integrations.

n8n

Use the MCP Client Tool node to give an AI Agent the Outstand tools, or the MCP Client node in a plain workflow.

1. Set Server Transport to HTTP Streamable, not the deprecated SSE option.
2. Set Endpoint to https://mcp.outstand.so/mcp.
3. Set Authentication to Bearer Auth, then create a Bearer Auth credential with your key as the Token. n8n sends it as Authorization: Bearer ost_your_key.
4. Save. The node fetches the Outstand tool list from the server.

If the node has no Server Transport field, it predates n8n's HTTP Streamable support (added July 2025) and speaks SSE only. That is a different transport, not a different field name: Outstand serves Streamable HTTP at /mcp and no SSE endpoint, so an SSE-only node cannot connect at all. Update n8n rather than looking for another URL to paste. Newer nodes have the selector but may still default to SSE, so set it explicitly either way.

The key is stored as an n8n credential - on n8n Cloud that means n8n's infrastructure, on a self-hosted instance your own. Create a key named n8n for it so you can revoke it from Settings → API Keys without disturbing your other integrations.

Any MCP Client (HTTP)

Any MCP-compatible client that supports streamable HTTP transport can connect directly with a key:

• Server URL: https://mcp.outstand.so/mcp
• Transport: Streamable HTTP (MCP revision 2026-07-28; clients on the 2025 revisions are still supported)
• Authentication: Authorization: Bearer ost_your_key header

Testing with MCP Inspector

You can test the connection using the official MCP Inspector tool:

npx @modelcontextprotocol/inspector@latest

Enter the server URL (https://mcp.outstand.so/mcp). The Inspector supports both OAuth (it will walk you through the browser sign-in) and a manual Authorization: Bearer ost_your_key header, so you can browse the available tools and test them interactively with either method.

Troubleshooting

The browser sign-in doesn't complete or won't redirect back

• Make sure pop-ups are allowed for your AI client so the OAuth window can open.
• If you have multiple organizations, confirm you selected the correct one on the authorization screen - the connector only has access to the organization you approved.
• To switch organizations or re-grant access, remove and re-add the connector, then complete the sign-in again.

"Authentication failed" or 401 error (API key)

• Verify your API key starts with ost_ and is correctly copied.
• Check that the Authorization header format is Bearer ost_your_key (note the space after "Bearer").
• Generate a new API key from your dashboard if the current one isn't working.

"No organization authorized for this client"

• This means the OAuth connection was made but no organization was granted. Reconnect the connector and complete the authorization flow again, making sure to pick an organization before approving.

Tools not appearing

• For the connector method, confirm the connector shows as connected in your client's settings and is enabled for the current chat.
• For the API key method, make sure mcp-remote is installed (npm install -g mcp-remote), restart your AI client, and check the configuration file path is correct for your OS.

"No social accounts found"

• Connect at least one social account through the Outstand dashboard before using the MCP tools.
• Configure your social network credentials first (see Configurations).

Connection timeout

• Verify you can reach https://mcp.outstand.so/mcp from your network.
• If you're behind a corporate proxy, configure your proxy settings in your AI client.