FoPost for Cline

Cline, the open source coding agent, connects to remote MCP servers. Add FoPost by URL, click Authenticate, and Cline can plan and schedule posts while it works.

Paste this into Cline

Set up FoPost from fopost.com/agents/cline
  • Hosted MCP server
  • 31 networks
  • No API key
All agents
How it works

Cline drafts. You approve. Then it goes out.

  • REST API
FoPost
YouApproveApproved

On by default

  • X (Twitter)
  • Facebook
  • Instagram
  • LinkedIn
  • TikTok
  • YouTube
  • Threads
  • Bluesky
  • Pinterest
  • Reddit
  • Discord
  • Mastodon
  • Telegram
  • Slack
  • DEV.to
  • Substack
  • Tumblr
  • Hashnode
  • Dribbble
  • Kick
  • Twitch
  • Nostr
  • Lemmy
  • MeWe
  • Whop
  • Listmonk
  • Google Business Profile
  • Medium
  • WhatsApp Business
  • Snapchat
  • Skool

Pick an agent to copy its setup prompt.

Setup

The agent can write its own config. Give it the link.

Paste the line above into Cline. It reads this page, adds the server, and stops so you can sign in to FoPost yourself. Rather do it by hand? This is the whole config.

cline_mcp_settings.json
{
  "mcpServers": {
    "fopost": {
      "type": "streamableHttp",
      "url": "https://api.fopost.com/mcp",
      "disabled": false
    }
  }
}
Instructions for AI agentsPlain markdown version
## For AI agents reading this page

You are reading https://fopost.com/agents/cline. FoPost schedules and publishes social posts on 31 networks, and its hosted MCP server gives Cline tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Cline to it.

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; Cline discovers the sign-in from the server.

### 1. Register the server

In the Cline panel, open MCP Servers, then the Remote Servers tab. Enter the name fopost and the URL https://api.fopost.com/mcp, choose Streamable HTTP, and click Add Server. Or add this entry under Configure MCP Servers; the type is required, or Cline falls back to SSE. No headers and no API key.

cline_mcp_settings.json:

```
{
  "mcpServers": {
    "fopost": {
      "type": "streamableHttp",
      "url": "https://api.fopost.com/mcp",
      "disabled": false
    }
  }
}
```

### 2. Sign in

Click Authenticate on the fopost server. A browser window opens for the user to sign in. In the Cline CLI, run cline mcp and choose Authorize OAuth. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.

### 3. Verify before you continue

The MCP Servers list shows fopost with its tools. If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist.

### 4. Report back

Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first.

### Standing rules

- Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser.
- Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently.
- Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them.

### No browser (headless machines only)

Use this only when the machine has no browser to sign in with. Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and to put it in the config themselves, then run the local package over stdio:

cline_mcp_settings.json:

```
{
  "mcpServers": {
    "fopost": {
      "command": "npx",
      "args": ["-y", "@fopost/mcp"],
      "env": { "FOPOST_API_KEY": "your-api-key" }
    }
  }
}
```

### References

- This block as markdown: https://fopost.com/agents/cline/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docs

A remote server

Add it in the panel. Nothing to install.

Sign in, not a key

Cline opens FoPost in the browser to approve access.

Approval first

Publishing goes through a proposal you accept. Drafts never go out alone.

Setup

Add the server, then authenticate

In the Cline panel, open MCP Servers, then Remote Servers. Enter fopost and https://api.fopost.com/mcp, choose Streamable HTTP and click Add Server. Then click Authenticate and sign in to FoPost.

Start free
cline_mcp_settings.json
{
  "mcpServers": {
    "fopost": {
      "type": "streamableHttp",
      "url": "https://api.fopost.com/mcp"
    }
  }
}

Editor or CLI

Works in the extension and the cline CLI.

No key in the config

You sign in instead of pasting a key.

Check first

The tools show under MCP Servers.

Plan

A week of posts from one prompt

Ask Cline to turn this week’s articles into posts with repurpose_url, shape each with draft_post_variants, and slot them with get_queue_slots. It ends with propose_publish, which you accept.

Plan your week
A month of scheduled posts on the publishing calendar

repurpose_url

An article becomes a run of posts.

draft_post_variants

A version for each network.

get_calendar

What is already booked.

Check

Ask whether it landed

The read tools report what published, which accounts need a reconnect, and what is waiting in the inbox.

Start free
Task
> What went out today?

list_posts shows 3 of 3 published.
list_inbox has 2 new comments.

list_posts

Recent posts and their status.

get_account_health

Which accounts need a reconnect.

list_inbox

Comments, mentions, and messages.

Headless

No browser on the machine?

On a server or in CI there is no browser to sign in with. Create an API key in the dashboard and run the local package over stdio instead. Keep the key out of your repository.

cline_mcp_settings.json
{
  "mcpServers": {
    "fopost": {
      "command": "npx",
      "args": ["-y", "@fopost/mcp"],
      "env": { "FOPOST_API_KEY": "your-api-key" }
    }
  }
}

Cline questions, answered

Do I need an API key?

No. Cline signs you in to FoPost through the browser.

Why does the type matter?

Without "type": "streamableHttp", Cline falls back to the older SSE transport.

Does it work in the Cline CLI?

Yes. Run cline mcp add with the URL, then cline mcp and choose Authorize OAuth.

Will it post without asking?

No. Publishing goes through a proposal you approve before anything is sent.

Does it use my AI credits?

Only the FoPost tools that write with AI do. Listing and scheduling do not.

Run FoPost from Cline

Starting is free and the MCP server is included. Paste the setup line into your agent, sign in, and schedule your first post from it.

Start free