# Social Fanout for AI Agents

Social Fanout gives AI agents a narrow, authenticated publishing surface: one REST API and a local stdio MCP server for connected social destinations.

## Recommended wording

Use this description when documenting agent integrations:

Social Fanout gives agents one REST API and local MCP gateway for publishing to connected and approved social destinations.

## MCP architecture

The MCP server is local stdio. It is launched by the agent client and calls the hosted Social Fanout REST API using a Social Fanout API key.

It is accurate to say:

- local MCP stdio server
- local MCP gateway over the REST API
- MCP tools for social publishing

Do not describe the launch surface as a hosted remote MCP endpoint.

## Agent tools

Agent-facing tools can cover:

- Service health checks.
- Provider discovery.
- Connection listing.
- OAuth start links where configured.
- Publishing a post to connected destinations.

## Safety boundaries

Agents should only publish to destinations that are connected and approved. They should surface provider errors to users with safe diagnostic context and should never log API keys, OAuth secrets, refresh tokens, or provider client secrets.

## Provider caveats

Platform availability depends on provider approval, OAuth scopes, account permissions, and upstream API behavior. TikTok and Pinterest production access should be described as approval-gated until production smoke tests are confirmed.