What your assistant can do with PostBoost
Once connected, you can manage social media from the chat you already work in. Ask your assistant to list your connected accounts, draft a LinkedIn post about a launch, check whether a caption fits X and Instagram, find the best time to post this week, schedule the post or add it to your queue, and later report how it performed. The assistant works through the same workspace, accounts and posting rules as the PostBoost dashboard, so everything it creates shows up there for review.
Connector or advanced server
PostBoost runs two MCP servers. The connector is built for conversations: a curated set of workflow tools with titles and safety annotations, OAuth sign-in in the client, and a dashboard access token as a fallback for headless use. The advanced server mirrors the REST API, one tool per operation, and accepts only a token. Start with the connector unless you need an operation it does not have.
Keep your token out of shared files
The configs on this page never contain a real token. When a setup reads the token from an environment variable such as POSTBOOST_API_TOKEN, keep it that way, so the config can be committed to a repository without leaking access. Tokens are shown once when you create them; if one leaks, delete it under Access Tokens and create a new one.
Check the connection
Ask your assistant to list your PostBoost workspaces or accounts. If it cannot see the tools, open your client's MCP settings and check that the PostBoost server is enabled and signed in. The full guides, with troubleshooting, are in the docs linked below each setup.