FeedBoss Documentation
Connected Assistants API (MCP)
The FeedBoss Model Context Protocol (MCP) endpoint, its OAuth auth model, and the tools a connected assistant can call.
FeedBoss exposes a Model Context Protocol (MCP) endpoint so assistants like Claude, ChatGPT, and Cursor can act in your workspace. This is the programmatic side of Connected Assistants.
FeedBoss is now listed in the ChatGPT plugin directory, so ChatGPT users can add it without pasting a link (search “FeedBoss” or open https://chatgpt.com/plugins?q=feedboss).
A different auth surface
This endpoint does not use the fb_live_ Service API Key described in Authentication. An assistant connects through an OAuth consent flow, and the user approves access from the assistant itself.
POST /api/v1/mcp
Access is gated by plan (see Connected Assistants) and is enabled per environment.
Tools
A connected assistant can call these tools:
| Tool | What it does |
|---|---|
generate_post | Draft a LinkedIn post |
import_post | Save a post to the workspace |
check_post_quality | Run the Slop Check on a post |
schedule_post | Schedule a post |
reschedule_post | Change a scheduled post’s time |
cancel_scheduled_post | Cancel a scheduled post |
list_recent_posts | List drafts, scheduled, and recently published posts |
list_popular_posts | List popular posts |
get_posts_timeline | Posts timeline (last 90 days plus scheduled) |
get_analytics_overview | Read the analytics overview |
get_posting_consistency | Read posting-consistency status |
get_voice_profile | Read the workspace voice Profile |
list_content_styles | List saved content styles |
search_knowledge_base | Search the Knowledge Base |
check_credit_balance | Read the credit balance |
ask_feedboss_data | Answer a question about the workspace’s own data |
NOTE
A post never publishes to LinkedIn without the user’s confirmation, and any assistant can be revoked from Settings, Connected Assistants.