# Social Fanout hosted connector

Canonical HTML: https://socialfanout.com/connectors

Social Fanout's hosted connector uses Streamable HTTP MCP at:

```txt
https://socialfanout.com/mcp
```

Directory availability is separate from endpoint availability. OpenAI and
Anthropic review and control their own listings, so this page does not mean
that Social Fanout is already published or discoverable in either directory.

## What the connector can do

After you sign in to Social Fanout and authorize one existing API key, a
compatible MCP client can:

- list available providers and the social accounts connected to that key;
- inspect account-specific publishing capabilities;
- dry-run one post without contacting the social provider or consuming publish
  quota;
- publish now or schedule one post to one selected account per tool call;
- list jobs and inspect per-account status and provider receipts;
- cancel a future scheduled job before a worker claims it; and
- start a first-party flow for connecting another social account.

Provider availability depends on Social Fanout configuration, provider
approval, account permissions, media rules, and upstream API status. A Social
Fanout acceptance or queued job is not proof that the native post is visible.
Inspect the returned account result, job status, and native destination before
reporting verified delivery or retrying an unclear result.

## Connect with OAuth

1. Add `https://socialfanout.com/mcp` as a custom connector in a compatible
   client, or choose Social Fanout after a directory listing becomes available.
2. Follow the Social Fanout sign-in prompt. Do not paste a Social Fanout API key
   or social-platform token into chat.
3. Select exactly one active Social Fanout key that you own and approve the
   named OAuth client. That client is limited to the accounts and entitlement
   attached to the selected key.
4. Review the authorized application in **Dashboard → Authorized assistants**.
   You can revoke it there to block future connector calls.

The hosted connector uses per-user OAuth. It does not expose the selected API
key or stored social-platform credentials to the MCP client.

## Publish safely

1. List connections and capabilities before preparing a publish call.
   Use the selected connection ID as `accountId`. If you also supply
   `connectionId`, it must equal `accountId`.
2. Call `fanout_publish_post` with `dryRun: true` for the exact content,
   destination, media, provider-specific options, and schedule.
3. A successful dry run returns a short-lived `confirmationToken` and
   `confirmationExpiresAt`. Review the dry-run result with the user.
4. For the approved live request, reuse that `confirmationToken` unchanged and
   send the exact same publish fields with `dryRun: false`.

The token is bound to the signed-in user, OAuth client, selected Social Fanout
key, and exact publish request. It cannot be reused after expiry. If any
content, destination, media, option, or schedule changes—or the token
expires—run a new dry run and obtain a fresh token before publishing.

Publishing and canceling are consequential write actions. For multiple
destinations, invoke the MCP publishing tool once for each explicitly approved
account and report each receipt separately.

## Data sent, stored, and controlled

The connector sends Social Fanout the signed-in account context and only the
fields required for the requested operation. A publish may include post text,
media URLs, a selected account identifier, provider-specific options, and a
schedule. Live publishing sends those fields onward to the selected social
provider. Social-platform credentials remain stored on Social Fanout's servers
and are not returned to the MCP client.

Hosted connection and history results omit internal key identifiers,
ownership fingerprints, arbitrary brand metadata, and dashboard-only replay
metadata. Public connection and job IDs, post content, schedules, status, and
provider receipts remain available for the requested workflow.

Social Fanout records content-free connector events when an application is
authorized or revoked and when a hosted tool is called. These events can
include the event name, tool name, success or error outcome, dry-run state,
trusted directory/source classification when an exact OAuth client identity is
configured, an opaque internal key identifier and key fingerprint, a one-way
hash of the OAuth client ID, an opaque grant identifier, and timestamps. They
do not include post text, media URLs, destination or social-account
identifiers, email addresses, access tokens, raw API keys, or the raw OAuth
client ID.

We use this telemetry for security, audit, support, reliability, capacity
planning, and to distinguish attributable Claude and OpenAI connector use. We
do not use it for behavioral advertising or to train models. Connector grants
remain until revoked, the selected key becomes unavailable, or the account is
deleted. Connector events remain until account deletion or operational
cleanup; Social Fanout does not currently claim a fixed automatic purge
interval. Revoking an application blocks future calls but does not immediately
erase its historical content-free events. See the [Privacy Policy](/privacy)
for deletion and other controls.

## Other supported integration paths

The hosted connector does not replace existing alternatives:

- The local stdio MCP package runs on your machine and calls Social Fanout with
  a customer-owned API key.
- The private GPT Action imports the hosted OpenAPI schema into a custom GPT
  where GPT Actions are available and uses a customer-owned Bearer key.
- The REST API supports direct server-to-server integrations, including a
  multi-target request shape that is separate from the one-account-per-call MCP
  contract.

Use the [Quickstart](/quickstart) for those API-key paths. They are distinct
from the hosted OAuth connector and have different credential boundaries.

## Support and policies

- [Privacy Policy](/privacy)
- [Terms of Service](/terms)
- [Service Status](/status)
- [Security](/security)
- [Support and FAQ](/faq)

Questions: [hello@socialfanout.com](mailto:hello@socialfanout.com)