What is MCP?
The Model Context Protocol is an open standard that lets an AI assistant call tools on another service. Hey Tasky runs an MCP server, so any assistant that supports custom MCP servers can work with your social calendar.
Your assistant already writes the posts. Hey Tasky gives it a real calendar: connect it once and it can draft, schedule, and check posts on every account in your workspace, from one chat.
These assistants don't accept custom tool servers right now. We'll add a guide when that changes.
The Model Context Protocol is an open standard that lets an AI assistant call tools on another service. Hey Tasky runs an MCP server, so any assistant that supports custom MCP servers can work with your social calendar.
No. Most assistants take a server URL in their settings and open a Hey Tasky sign-in window. Developer tools use one command or a few lines of config, which each guide shows.
Only if you ask it to schedule. A draft request saves the post in Hey Tasky for you to review. A schedule request publishes automatically at the time you set, so check the text, account, and time first.
Any account you have connected in Hey Tasky, such as X, LinkedIn, Bluesky, and Mastodon. The agent asks Hey Tasky for your connected accounts before posting, so it can only use accounts you added.
No. You connect social accounts inside Hey Tasky. The agent gets a Hey Tasky sign-in or API key scoped to your workspace, which you can revoke at any time.
Yes. Each assistant signs in separately, so you can use ChatGPT on your phone and Claude at your desk against the same calendar.