`connect_account`

Start connecting one of the user's own social accounts to their SocialClaw workspace. For most providers this returns an authorizeUrl; give it to the user so they sign in with the provider themselves (SocialClaw never sees their password). Telegram and Discord have no sign-in page: Telegram takes the bot token and chat id of a bot the user created and made admin of their channel, and Discord takes a webhook URL the user created for their channel. Only pass values the user gave you for this purpose.

Calling it

Invoke this tool with a JSON-RPC 2.0 tools/call request against the hosted MCP endpoint at POST https://getsocialclaw.com/mcp. Send your workspace API key as Authorization: Bearer sc_live_your_key. In an MCP client (Claude, Cursor, Claude Code) the client makes this call for you — just ask it to use connect_account.

Arguments

Parameter	Type		Description
`provider`	`string`	required	Provider to connect.
`botToken`	`string`	optional	Telegram only: token of the user's own bot, from @BotFather.
`chatId`	`string`	optional	Telegram chat target, e.g. @yourchannel (telegram only).
`webhookUrl`	`string`	optional	Discord only: webhook URL the user created in their channel settings.

Example request

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "connect_account",
    "arguments": {
      "provider": "linkedin"
    }
  }
}

Response

The server replies with a JSON-RPC result whose content array carries the tool output as a JSON-encoded text block. isError is true when the call failed.

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{ /* JSON-encoded tool result */ }"
      }
    ],
    "isError": false
  }
}