# Connect an AI Agent to Your Social Channels in Six Steps

> Connect an AI agent to your social channels through one MCP endpoint and a scoped token. Six steps, from minting the token to a scheduled week.

Canonical page: https://www.socialfaktory.com/blog/connect-an-ai-agent-to-your-social-channels
Published: 2026-09-15
Language: en

To connect an AI agent to your social channels, give it an execution layer rather than another prompt. That layer is one MCP endpoint, a token that carries only the permissions you chose, and the channels you connected once in a browser. After that the agent can price a job, generate the video, write the posts and put them on the calendar without you opening the app.

Six steps get you there, and none of them takes longer than a coffee.

1. Mint a personal access token in your settings and copy the secret while it is on screen.
2. Choose its scopes. Read is always on, generate lets it spend credits, publish lets it post.
3. Pin the token to one brand and set a monthly credit cap.
4. Add the endpoint to your agent client as a Streamable HTTP MCP server.
5. Ask the agent to list your brands and channels, which costs nothing and proves the wiring.
6. Brief it for the week, read the quote, and let it schedule what you approve.

## What does an agent need before it can post?

Three things, and only one of them is technical. It needs a brand that already knows your voice, your cast and your products. It needs at least one social account connected, which is a browser sign-in and therefore stays in the app. And it needs a token.

Nothing else is required. There is no SDK to install and no key exchange to arrange. The [agent hub](/agents) lists every client with a tested recipe.

## How do you mint a token?

Open your settings, create a token, and decide three things about it. The scopes decide what it may do. The brand pin decides which brand's channels, generations and posts it may see, though the credit wallet and uploads stay shared across the account. The monthly credit cap decides how much it may ever spend.

The secret appears once. Store it the way you store any other credential, in a password manager or an environment variable, never in a file you commit.

## How do you point a client at the endpoint?

Every client takes the same URL and the same header. Claude Code registers it from the command line.

```bash
claude mcp add -s user --transport http socialfaktory https://www.socialfaktory.com/mcp --header "Authorization: Bearer sfp_..."
```

Codex reads the token from the environment, which keeps the secret out of the config file.

```bash
export SOCIALFAKTORY_TOKEN=sfp_...
codex mcp add socialfaktory --url https://www.socialfaktory.com/mcp --bearer-token-env-var SOCIALFAKTORY_TOKEN
```

OpenClaw takes the whole server entry as JSON, with the transport named and the token in a header.

```bash
openclaw mcp set socialfaktory '{"url":"https://www.socialfaktory.com/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer sfp_..."}}'
```

Claude Desktop reaches the endpoint through mcp-remote, a small local bridge declared in its config file. claude.ai and Cowork can use it only when an organization administrator adds it with the token as a request header, which shares that token across the organization. The per-client guides go further, one for [Claude](/agents/claude), one for [Codex](/agents/codex) and one for [OpenClaw](/agents/openclaw).

## What does the agent call?

Twenty tools in five groups. Reading tools list your brands, channels, formats and wallet, and they are free. Generating tools price a job and then run it. Result tools read back what came out. Upload tools bring a file of your own into the library. Publishing tools compose posts, send them and delete them.

Every tool names the scope it needs, so a token without that scope is refused before the tool runs. Every call that spends or publishes carries an idempotency key, and a replay inside twenty-four hours returns the first result instead of doing the work twice. The [MCP reference](/docs/mcp) lists all twenty by name, with the scope each needs and whether it spends credits.

## What will an agent not do?

It will not clone a video from a link, and it will not make still images or carousels. Those stay in the app for now. It will not connect a social channel, because that is an OAuth sign-in in a browser. It will not change your plan, and it cannot spend past the cap you set.

That list matters more than the feature list. An agent you cannot bound is an agent you cannot leave running.

## What does a first run cost?

Nothing, until you say otherwise. Listing brands, channels and formats is free, reading your wallet is free, and pricing a job with the quote tool is free. The first call that spends is the one that makes a video or writes a post. Nothing forces a quote before a video, so ask for one. A text write has no quote: it reserves a few credits up front and settles what it used.

That asymmetry is deliberate. An agent that can survey your whole account for free is an agent you can let explore before you trust it with a credit. Spend your first session asking it what it can see, and read the answers carefully: they tell you whether your brand is set up the way you think it is.

If a channel you expected is missing from that list, its connection may have lapsed. Reconnect it in the app, then come back to the session.

## What does a first week look like?

Give it a theme and a channel mix on Monday. Ask for a quote before each video runs, read it, and approve the parts you want. The agent can then generate the videos and write the posts around each one. Composing them as drafts, scheduling them and sending them immediately all need the publish scope, so decide which you want before you grant it.

If you would rather stay in the product, the [AI assistant](/features/ai-assistant) does the same job inside the app, with the same prices on screen before anything spends. The agent route is for people who already live in a terminal. [Start a brand](/register) and mint your first token from the same settings page.

**In one sentence:** Connect an AI agent to your social channels by minting a scoped token, pointing your client at one MCP endpoint, and capping what it may spend each month.

## Questions

### Do I need to write any code to connect an agent?

No. Every supported client takes the endpoint through one command, one config entry or one settings screen.

### Can a read-only token publish by mistake?

No. Publishing tools are refused outright unless the token carries the publish scope.

### How do I stop an agent from overspending?

Set a monthly credit cap on the token. It starts no paid call once the month's spend reaches the cap.

### Which channels can an agent publish to?

X, Instagram, TikTok, YouTube, LinkedIn, Facebook and Pinterest, once you have connected them in the app.

### Can I give each brand its own token?

Yes. A pinned token sees only its brand's channels, generations, posts and text, while the credit wallet and uploads stay shared across the account.

### What happens if the agent retries a call?

Calls that spend or publish take an idempotency key. A replay inside twenty-four hours returns the first result.

## More detail

- All articles: https://www.socialfaktory.com/blog.md
- What SocialFaktory does: https://www.socialfaktory.com/features.md
- Pricing: https://www.socialfaktory.com/plans.md