$59 once, yours for life

Get it

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.

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:

ToolWhat it does
generate_postDraft a LinkedIn post
import_postSave a post to the workspace
check_post_qualityRun the Slop Check on a post
schedule_postSchedule a post
reschedule_postChange a scheduled post’s time
cancel_scheduled_postCancel a scheduled post
list_recent_postsList drafts, scheduled, and recently published posts
list_popular_postsList popular posts
get_posts_timelinePosts timeline (last 90 days plus scheduled)
get_analytics_overviewRead the analytics overview
get_posting_consistencyRead posting-consistency status
get_voice_profileRead the workspace voice Profile
list_content_stylesList saved content styles
search_knowledge_baseSearch the Knowledge Base
check_credit_balanceRead the credit balance
ask_feedboss_dataAnswer 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.