Skip to content

Frequently asked questions

Short answers to the questions support hears most. Each links to the guide that covers it in full.

Can I cancel a scheduled post?

Yes. Open All Posts, find the post and choose Cancel. A cancelled post never reaches the network and no credits are spent. Posts that already published cannot be recalled from PostMCP; removing one only deletes your local record, the post stays live on the network.

Read the guide
How many people can I invite to a workspace?

Seats depend on the owner’s plan: 1 on Free Forever, 5 on Starter, 10 on Professional and 20 on Business. Pending invitations count towards the limit until they are accepted or cancelled.

Read the guide
How long does an invitation stay valid?

Seven days. After that the link stops working and an admin has to cancel the pending invite from the Team tab and send a new one.

Read the guide
Why did my post fail?

The most common cause is an expired authorisation on the target profile. Open Accounts, reconnect the profile, then use Publish Immediately on the failed post to retry. Profiles that already received the post are skipped, so a retry never double-posts.

Read the guide
What does a post cost?

One credit for every profile it is delivered to, except X, which costs five. A post whose text contains a link carries a one-off surcharge of 50 credits. Drafts and cancelled posts cost nothing.

Read the guide
Which time zone do scheduled times use?

The composer schedules in your browser’s local time zone and says so under the time picker. Through the API and MCP tools, always pass a timezone, otherwise the backend treats the time as UTC.

Read the guide
Does deleting a workspace delete my connected accounts?

No. Deleting a workspace removes its posts, activity log and team access. To revoke a social authorisation, disconnect the channel from Accounts. To have every record removed, submit a data deletion request.

Read the guide
Is my API key or social login ever shown to the AI model?

No. The model only sees tool names, the arguments it chooses and the results. Your API key stays in the client configuration, and social OAuth tokens never leave the PostMCP backend.

Read the guide