Typefully migrated to API v2 in December 2025 and stopped issuing v1 API keys. This server uses the v1 endpoints (https://api.typefully.com/v1) and X-API-KEY: Bearer auth header, which means any new API key from Typefully Settings → API will return 403.
What changed (v1 → v2):
|
v1 (EOL June 2026) |
v2 (current) |
| Base URL |
api.typefully.com/v1/ |
api.typefully.com/v2/ |
| Auth |
X-API-KEY: Bearer <key> |
Authorization: Bearer <key> |
| Scope |
Twitter only |
Multi-platform (X, LinkedIn, Threads, Bluesky, Mastodon) |
| Content format |
Flat text |
Platform-nested (platforms.x.posts[]) |
| Scheduling |
schedule-date |
publish_at ("now", "next-free-slot", or ISO 8601) |
| New concept |
N/A |
social_set_id required for all operations |
I built a v2-compatible server here: https://github.com/jrejaud/typefully-mcp-server
Happy to collaborate if you'd prefer to update this repo instead.
Typefully migrated to API v2 in December 2025 and stopped issuing v1 API keys. This server uses the v1 endpoints (
https://api.typefully.com/v1) andX-API-KEY: Bearerauth header, which means any new API key from Typefully Settings → API will return 403.What changed (v1 → v2):
api.typefully.com/v1/api.typefully.com/v2/X-API-KEY: Bearer <key>Authorization: Bearer <key>platforms.x.posts[])schedule-datepublish_at("now","next-free-slot", or ISO 8601)social_set_idrequired for all operationsI built a v2-compatible server here: https://github.com/jrejaud/typefully-mcp-server
Happy to collaborate if you'd prefer to update this repo instead.