The FoPost MCP Server
One hosted MCP server turns your FoPost workspace into tools your AI agent can use. Any client that supports remote MCP connects by URL and signs in through the browser; for a machine with no browser, the npm package runs locally with an API key.
Paste this into your agent
Set up FoPost from fopost.com/agents/mcp-server- Hosted MCP server
- 33 networks
- No API key
The agent can write its own config. Give it the link.
Paste the line above into your agent. 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.
{
"mcpServers": {
"fopost": {
"url": "https://api.fopost.com/mcp"
}
}
}## For AI agents reading this page
You are reading https://fopost.com/agents/mcp-server. FoPost schedules and publishes social posts on 33 networks, and its hosted MCP server gives your MCP client tools for posts, the calendar, the inbox and analytics. Follow these steps to connect your MCP client 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; your MCP client discovers the sign-in from the server.
### 1. Register the server
Add https://api.fopost.com/mcp as a remote MCP server using streamable HTTP, in whatever form your client takes (a command, a JSON or TOML entry, or a connector form). Do not add an API key or an Authorization header.
### 2. Sign in
Connect. The server answers 401 with a WWW-Authenticate header pointing at https://api.fopost.com/.well-known/oauth-protected-resource/mcp; a client that supports MCP OAuth registers itself (dynamic client registration, PKCE) and opens the browser 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
Your client lists fopost as connected and shows 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:
mcpServers:
```
{
"mcpServers": {
"fopost": {
"command": "npx",
"args": ["-y", "@fopost/mcp"],
"env": { "FOPOST_API_KEY": "your-api-key" }
}
}
}
```
### References
- This block as markdown: https://fopost.com/agents/mcp-server/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docsHosted, sign in once
Connect by URL and sign in to FoPost in the browser. No key to copy, nothing to install.
80+ tools
Posts, calendar, queue, inbox, analytics, listening, ads, media, AI and automations.
You approve, it publishes
The agent drafts and proposes. Nothing goes live until you approve it.
Add it to the client you already use
Paste the server URL into your client's connectors or MCP settings and sign in to FoPost. The connection is scoped to the workspaces you choose and can be revoked at any time. On a server or CI machine with no browser, run the npm package with an API key instead.
See per-client setup# Hosted server: add this URL to any MCP client, then sign in
https://api.fopost.com/mcp
# No browser? Run it locally with an API key
FOPOST_API_KEY=your-api-key npx -y @fopost/mcpOne URL
The same address works in Claude, ChatGPT, Cursor, Codex, VS Code and more.
Browser sign-in
Standard OAuth, so no API key ever sits in a config file.
Local option
The open-source npm package runs over stdio with a scoped API key.
Everything the dashboard can do, as tools
The tools cover the whole job: plan a week, draft and preview posts for each network, schedule them into the calendar or queue, answer comments and messages, read analytics and competitors, watch mentions, manage ads, and generate images and video with your brand kit.
Browse the toolscreate_draft_post propose_publish get_calendar
reschedule_post add_to_queue list_inbox
draft_inbox_reply get_analytics_summary
list_radar_mentions get_competitor_activity
list_ads generate_image generate_video
create_recipe create_connect_linkPlan and publish
Drafts, previews per network, calendar, queue, reschedule and retry.
Engage
Read the inbox, draft replies, label and resolve conversations.
Measure
Analytics, campaign reports, competitors, listening and ads insights.
Built for agents that ask first
The agent never publishes on its own. Posting, scheduling and other actions that reach a network are proposed first and wait for your approval. Every connection is limited to the workspaces and scopes you grant.
Start free
Approval first
Anything that reaches a network waits for your OK. Reads change nothing.
Workspace isolation
A connection reaches only the workspaces you chose. Clients never mix.
Revoke any time
Disconnect the client or delete the key and access stops instantly.
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.
{
"mcpServers": {
"fopost": {
"command": "npx",
"args": ["-y", "@fopost/mcp"],
"env": { "FOPOST_API_KEY": "your-api-key" }
}
}
}MCP Server questions, answered
Which clients are supported?
Do I need an API key?
Can the agent publish without me?
What does it cost?
Can it read analytics?
Where is the source?
Your agent, every network
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