Skip to content
Connect an agent

Workflows

connect_platforms

Start connecting several platforms. Starts a connect for each platform named and returns one authorizationUrl per platform, skipping any this Flung cannot connect. Give the person every link, then poll get_connect_session for each sessionId. For an account already connected, use reconnect_accounts_needing_attention instead.

TL;DR

QuestionAnswer
What does it do?Starts a connect for each platform named and returns one authorizationUrl per platform, skipping any this Flung cannot connect. Give the person every link, then poll get_connect_session for each sessionId. For an account already connected, use reconnect_accounts_needing_attention instead.
Does it change anything?Changes something.
Which tools does it call?list_platforms, connect_account
What if a step is refused?The workflow stops there and answers with that step's refusal, named, with its reason and next step.
Which server?https://mcp.flung.dev/mcp-oauth (sign in) or https://mcp.flung.dev/mcp (API key).

Steps

StepToolWhat it does
1list_platformsList platforms and their limits
2connect_accountConnect a new account

Arguments

ArgumentTypeRequiredDescription
platforms("x" | "instagram" | "facebook" | "threads" | "linkedin" | "tiktok" | "youtube" | "pinterest" | "bluesky" | "mastodon" | "discord" | "farcaster")[]yesThe platforms to connect.
redirectUrlstringnoWhere to send the person after each one. at most 2048 characters.

Example call

json
{  "name": "connect_platforms",  "arguments": {    "platforms": [      "linkedin",      "x",      "bluesky"    ]  }}

Things a person might say

  • "Connect our LinkedIn, X and Bluesky."
  • "Set up all our social accounts."

Annotations

HintValue
readOnlyHintfalse
destructiveHintfalse
idempotentHintfalse
openWorldHinttrue

See also

DocWhy
MCP toolsEvery workflow and tool
Connect an AI agentInstall the server in your client