FoPost for GitHub Copilot

GitHub Copilot connects to remote MCP servers in the CLI and in your IDE. Add FoPost by URL, sign in once, and Copilot can write the launch posts for the code it just shipped.

Paste this into GitHub Copilot

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

GitHub Copilot 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 GitHub Copilot. 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.

Terminal
copilot mcp add --transport http fopost https://api.fopost.com/mcp
Instructions for AI agentsPlain markdown version
## For AI agents reading this page

You are reading https://fopost.com/agents/github-copilot. FoPost schedules and publishes social posts on 31 networks, and its hosted MCP server gives GitHub Copilot tools for posts, the calendar, the inbox and analytics. Follow these steps to connect GitHub Copilot 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; GitHub Copilot discovers the sign-in from the server.

### 1. Register the server

Run this command for Copilot CLI. It adds the server to ~/.copilot/mcp-config.json. No headers and no API key. In JetBrains or Visual Studio, open Copilot Chat in Agent mode, choose the tools icon, then Add MCP Tools, and add the same URL to mcp.json.

Terminal:

```
copilot mcp add --transport http fopost https://api.fopost.com/mcp
```

### 2. Sign in

Run /mcp auth in a Copilot CLI session and pick the server. A browser window opens for the user to sign in. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.

### 3. Verify before you continue

/mcp show fopost lists the server as connected 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:

~/.copilot/mcp-config.json:

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

### References

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

One command

copilot mcp add writes the entry for you.

Sign in, not a key

Copilot 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 sign in

In Copilot CLI, run the command, then /mcp auth in a session and sign in to FoPost. In JetBrains or Visual Studio, open Copilot Chat in Agent mode, choose the tools icon, and add https://api.fopost.com/mcp to mcp.json.

Start free
Terminal
copilot mcp add --transport http fopost https://api.fopost.com/mcp

CLI or IDE

The same server in the terminal and the editor.

No key in the config

You sign in instead of pasting a key.

Check first

/mcp show fopost lists the tools.

Ship

Turn a merged PR into posts

Ask Copilot to summarize what changed, shape a post for each network with draft_post_variants, and book them with get_queue_slots. It ends with propose_publish, which you accept.

Plan your week
One post shaped for several networks in the composer

draft_post_variants

A version for each network.

get_queue_slots

The next open times in your queue.

propose_publish

You approve before anything goes out.

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
Session
> What went out today?

list_posts shows 2 of 2 published.
list_inbox has 5 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.

~/.copilot/mcp-config.json
{
  "mcpServers": {
    "fopost": {
      "type": "local",
      "command": "npx",
      "args": ["-y", "@fopost/mcp"],
      "env": { "FOPOST_API_KEY": "your-api-key" },
      "tools": ["*"]
    }
  }
}

GitHub Copilot questions, answered

Do I need an API key?

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

Does it work in the cloud agent on github.com?

The cloud agent does not sign in to remote servers yet. Use an API key header there, stored as a COPILOT_MCP_ secret.

My organization blocks it. Why?

On Business and Enterprise plans, an admin has to allow MCP servers in Copilot.

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 GitHub Copilot

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