Draft creation
create_post saves an unscheduled draft. Review and schedule it later in the app.
Bring your own AI
Social media MCP server
Hey Tasky provides a remote MCP server for compatible AI clients to create drafts, schedule posts, and read the queue in your workspace. Start with create_post when you want to review the text before scheduling. schedule_post authorizes automatic publishing at the chosen time.
Live now. Native account strategy. Agent-first scheduling.
Best for
Who this page is for.
Claude desktop users
Custom internal agent workflows
Technical teams building AI operators
Capabilities
What Hey Tasky is built to handle.
Scheduled publishing
schedule_post accepts content, connected channel IDs, and an ISO 8601 time. The engine publishes automatically at that time.
Workspace-scoped access
OAuth tokens and API keys identify a workspace. Tool calls require the relevant read or write scope.
Queue and results
get_queue reads scheduled or published states. get_post_results returns measured results; new metrics may be null.
Connected channel lookup
list_channels returns your workspace accounts. Use those IDs instead of guessing a platform name.
Practical guide
A draft-first launch workflow
Example: prepare a launch announcement for one connected account, review it, then schedule it. The tool names and arguments below match the Hey Tasky MCP interface.
1. Connect and confirm the workspace
Open Settings, Developers in Hey Tasky and copy the MCP configuration for your client. The default endpoint is https://mcp.heytasky.com/mcp. OAuth handles sign-in for compatible clients; API keys are an alternative for headless tooling.
- Ask the agent to call get_account with {} to confirm the workspace and timezone.
- Call list_channels with {} and choose an ID from the response. Do not invent channel IDs.
2. Save a draft for review
Ask: "Create a launch draft for my selected channel. Do not schedule it." The agent should call create_post with content and the selected channel_ids.
- Example arguments: {"content":"Our new release is available. Here is what changed: ...","channel_ids":["CHANNEL_ID_FROM_LIST"]}
- The result contains a draft ID and status: draft. Open Posts in the app to review and edit it.
3. Schedule the approved text
After reviewing the draft, explicitly ask the agent to schedule the final text. schedule_post creates a scheduled post; it does not approve or update the earlier draft. Keep the original draft out of the schedule to avoid duplicates.
- Example arguments: {"content":"YOUR_REVIEWED_TEXT","channel_ids":["CHANNEL_ID_FROM_LIST"],"scheduled_at":"YOUR_FUTURE_ISO_8601_TIME"}
- Include a timezone offset or use UTC. Confirm the time before running the call, because it authorizes publishing.
4. Check delivery
Call get_queue with {"status":"scheduled"} to confirm the scheduled entry. After its publish time, check the published and failed queues. Use get_post_results for performance when measurements are available.
- An empty get_best_times response means there is not enough measured history yet.
- A successful scheduling response confirms the queue entry, not a successful network publication.
Setup and protocol references
Limits
Check these before scheduling.
Confirm your connected accounts and the workflow you want to use.
A schedule command does not require a separate approval step
Only connected accounts can be targeted; adapters do not guarantee provider approval or account eligibility
This example uses text posts. Media and post-format support vary by network
FAQ
Questions people ask before choosing a scheduler.
Will this replace the Hey Tasky web app?
No. MCP is for agent control. The web app remains the place to review, edit, and manage the calendar.
Does every MCP post wait for human approval?
create_post saves a draft for review. schedule_post creates a scheduled entry that the engine publishes automatically. Use draft creation until you have reviewed the text, account, and time.
Which accounts can the agent use?
The agent can target accounts returned by list_channels in its authenticated workspace. Connection availability depends on provider configuration, permissions, and account eligibility; do not assume every advertised network is enabled.
Related pages