FoPost for Continue

Continue, the open source coding agent, connects to remote MCP servers in Agent mode. Add FoPost with an API key and Continue can plan and schedule posts while you code.

Paste this into Continue

Set up FoPost from fopost.com/agents/continue
  • Hosted MCP server
  • 31 networks
  • API key in a header
All agents
How it works

Continue 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 Continue. It reads this page and sets up the connector, then asks for an API key you create in the dashboard. Rather do it by hand? This is the whole config.

~/.continue/config.yaml
mcpServers:
  - name: fopost
    type: streamable-http
    url: https://api.fopost.com/mcp
    requestOptions:
      headers:
        X-API-Key: ${{ secrets.FOPOST_API_KEY }}
Instructions for AI agentsPlain markdown version
## For AI agents reading this page

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

- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: Continue cannot run the OAuth sign-in for a remote server, so it sends an API key in the X-API-Key header. The user creates the key; you never see it in chat.

### 1. Register the server

Continue signs in to remote servers over SSE only, so with streamable HTTP it sends an API key in the X-API-Key header. Add this entry to ~/.continue/config.yaml, with the key stored as the FOPOST_API_KEY secret. MCP tools run in Agent mode.

~/.continue/config.yaml:

```
mcpServers:
  - name: fopost
    type: streamable-http
    url: https://api.fopost.com/mcp
    requestOptions:
      headers:
        X-API-Key: ${{ secrets.FOPOST_API_KEY }}
```

### 2. Sign in

Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and store it as the FOPOST_API_KEY secret themselves. Never ask them to paste the key into the chat. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.

### 3. Verify before you continue

In Agent mode, asking for the connected FoPost accounts calls list_accounts and returns data. 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.

### References

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

One entry

A url and a header in config.yaml.

Your own key

Create a key in FoPost and revoke it any time.

Approval first

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

Setup

Add the server with a key

Create an API key in FoPost and store it as the FOPOST_API_KEY secret. Add the entry to ~/.continue/config.yaml, then switch to Agent mode.

Start free
~/.continue/config.yaml
mcpServers:
  - name: fopost
    type: streamable-http
    url: https://api.fopost.com/mcp
    requestOptions:
      headers:
        X-API-Key: ${{ secrets.FOPOST_API_KEY }}

Key as a secret

Never in the file itself.

Agent mode

MCP tools run in Agent mode.

Check first

Ask it to list your connected accounts.

Plan

A week of posts from one prompt

Ask Continue 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
Agent
> What went out today?

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

list_posts

Recent posts and their status.

get_account_health

Which accounts need a reconnect.

list_inbox

Comments, mentions, and messages.

Continue questions, answered

Why does Continue need an API key?

Continue signs in to remote servers over SSE only. With streamable HTTP it sends a key in a header.

Where do I keep the key?

As a Continue secret named FOPOST_API_KEY, never in the config file itself.

I see no tools. Why?

MCP tools only run in Agent mode. Switch the mode and ask again.

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 Continue

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