> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postlybee.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect MCP clients

> Configure Claude Code, Cursor, and other Streamable HTTP clients.

Use the modern MCP endpoint whenever the client supports Streamable HTTP. Prefer OAuth discovery when the client offers it; otherwise configure a workspace API key as a Bearer token.

## Claude Code

```bash theme={null}
claude mcp add --transport http postlybee \
  "https://api.postlybee.com/mcp" \
  --header "Authorization: Bearer YOUR_API_KEY"
```

After adding the server, ask Claude to list the available PostlyBee accounts before scheduling content.

## Generic configuration

Clients that accept JSON server configuration typically use a structure similar to:

```json theme={null}
{
  "mcpServers": {
    "postlybee": {
      "url": "https://api.postlybee.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

Configuration keys vary by client. Select **Streamable HTTP** or **HTTP** transport, not the deprecated SSE transport.

## OAuth discovery

Clients supporting OAuth can start with only the MCP URL. PostlyBee advertises protected-resource and authorization-server metadata under `/.well-known`, supports dynamic client registration, and requires PKCE S256 for authorization-code exchange.

During authorization, sign in to PostlyBee, choose the intended workspace, review the requested scopes, and approve the connection.

## Verify the connection

Ask the client to perform a read-only action first:

> List all PostlyBee social accounts available in this workspace.

Then test a publishing workflow without immediately sending content:

> Validate the requirements for my selected account and prepare a draft post. Ask for confirmation before scheduling it.

## Troubleshooting

| Symptom             | Check                                                             |
| ------------------- | ----------------------------------------------------------------- |
| `401 invalid_token` | Confirm the Bearer header or reconnect through OAuth.             |
| No write tools      | Reconnect with the `mcp:write` scope.                             |
| Client expects SSE  | Use the legacy URL only if Streamable HTTP is unsupported.        |
| Wrong workspace     | Remove the connection and authorize the intended workspace again. |