What is MCP?
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and services. FeedMansion provides a built-in MCP server so your AI assistant can help you manage content — drafting posts, organizing queues, and more — all from within your AI chat.
No installation or self-hosting required. FeedMansion's MCP server runs remotely at https://feedmansion.com/mcp.
Prerequisites
Before connecting an AI assistant, you need an Agent Token:
- Go to Settings → API Tokens in FeedMansion
- Choose the Agent token type
- Optionally restrict the token to specific presences
- Click Create Token and copy the token (it starts with
fm_pat_)
Agent tokens include a supervision gate: your AI assistant can create and organize content, but nothing gets published without your explicit approval in the FeedMansion UI.
Claude
Claude.ai (Web / Desktop)
- Open Claude → Settings → Integrations (or Connectors)
- Click Add MCP Server (or Add Custom Connector)
- Enter the server URL:
https://feedmansion.com/mcp - For authentication, add a custom header:
- Header name:
Authorization - Header value:
Bearer fm_pat_YOUR_TOKEN_HERE
- Header name:
- Save — Claude will discover the available FeedMansion tools automatically
Claude Code / Claude Desktop (JSON config)
Add to your MCP configuration file:
{
"mcpServers": {
"feedmansion": {
"type": "streamable-http",
"url": "https://feedmansion.com/mcp",
"headers": {
"Authorization": "Bearer fm_pat_YOUR_TOKEN_HERE"
}
}
}
}
ChatGPT
- Open ChatGPT → Settings → MCP
- Click Add MCP Server
- Enter the server URL:
https://feedmansion.com/mcp - Set the authentication header:
Authorization: Bearer fm_pat_YOUR_TOKEN_HERE - Save — ChatGPT will discover the available tools
Perplexity
- Open Perplexity → Settings → MCP
- Click Add Server
- Enter the URL:
https://feedmansion.com/mcp - Add your token as a Bearer authorization header
- Save and test the connection
Manus AI
- Open Manus AI → Settings → MCP Servers
- Add a new server with URL:
https://feedmansion.com/mcp - Configure authentication with your Agent Token as a Bearer token
- Save — Manus will detect the available FeedMansion tools
Cursor / Other MCP Clients
Any MCP client that supports Streamable HTTP transport can connect using this JSON config:
{
"mcpServers": {
"feedmansion": {
"type": "streamable-http",
"url": "https://feedmansion.com/mcp",
"headers": {
"Authorization": "Bearer fm_pat_YOUR_TOKEN_HERE"
}
}
}
}
Replace fm_pat_YOUR_TOKEN_HERE with your actual Agent Token.
What Can AI Assistants Do?
Once connected, your AI assistant has access to these tools:
- list_presences — See all your presences (brands/projects)
- get_presence — Get details about a specific presence, including connected social accounts
- list_content — Browse content drafts, optionally filtered by status
- get_content — Read a specific piece of content
- create_content — Create a new draft
- generate_content_from_url — Generate a draft from a URL using AI
- approve_content — Submit a draft for human review (with target social accounts)
- enqueue_content — Request to add content to a publishing queue
Safety: The Supervision Gate
Agent tokens enforce a supervision gate — your AI assistant can prepare content, but critical actions require your approval:
- Creating drafts: Allowed — drafts are saved with status "draft"
- Approving content: The AI submits content for your review — it moves to "pending review" status, not directly to publishing
- Enqueuing content: The AI saves an enqueue intent — you confirm it in the FeedMansion UI
- Publishing: Not available to AI assistants — only humans can publish
This means your AI assistant is a powerful content co-pilot, but you always have the final say before anything goes live.