TimeToPost

TimeToPost MCP server

A social media scheduler for AI agents. This is the official Model Context Protocol server for TimeToPost. Connect it to Claude, Cursor, VS Code, Windsurf, ChatGPT or any MCP client and your agent can write drafts, queue them in an approval inbox, schedule or publish posts to 16 networks, pick the best time to post from your own engagement history, read analytics, upload media, generate short videos and run AutoSEO blog workflows. Hosted, OAuth sign-in, no API key to copy.

Use it when you want an MCP server to post to social media (X, Instagram, TikTok, Threads, Bluesky, Mastodon and more), schedule posts from an AI assistant, or give an autonomous agent a safe publishing path where a human approves before anything goes live.

Supported networks: Instagram, X, TikTok, Threads, Bluesky, Mastodon, Nostr, Pixelfed, Telegram, Tumblr, WordPress, Ghost, DEV, Whop, Listmonk and Buttondown. Coming soon: LinkedIn, YouTube, Pinterest, Discord, Slack, Lemmy, Dribbble, Kick, Twitch and Farcaster.

Mirror posting: post on X and it is mirrored to your other connected networks.

The hosted server exposes 70 tools; the npm/stdio package exposes 62 of them. Call get_capabilities for what your workspace can use.

• Hosted MCP endpoint: https://api.timetopost.co/mcp
• Public setup and tool documentation: [TimeToPost MCP docs](https://timetopost.co/docs/mcp/)

Recommended setup: hosted server with OAuth

Use the hosted Streamable HTTP server in an MCP client that supports remote servers and OAuth. Add https://api.timetopost.co/mcp, then follow the browser sign-in flow and approve access. No local installation or API token copying is needed.

For Claude Code:

claude mcp add --transport http timetopost https://api.timetopost.co/mcp

For Cursor, VS Code, Windsurf, Claude Desktop (via a remote connector) and other clients that accept URL-based MCP configuration:

{

"mcpServers": { "timetopost": { "url": "https://api.timetopost.co/mcp" } } }

Client-specific setup details are in the public docs. You can revoke access from Settings → API in TimeToPost.

Claude Code plugin and skill

This repo is also a Claude Code plugin marketplace. The timetopost plugin bundles the hosted MCP server and a schedule-social-posts skill that runs the safe workflow: check the workspace with whoami, read recent posts for voice, draft first, let a human approve, then schedule.

/plugin marketplace add MelMayssonOwen/timetopost-mcp

/plugin install timetopost@timetopost

Then sign in to TimeToPost when Claude Code prompts for MCP authentication.

Other ways to install:

• Skill only, any harness that reads `SKILL.md` folders. Copy plugins/timetopost/skills/schedule-social-posts into ~/.claude/skills/ (or your project's .claude/skills/), and add the MCP server separately.
• MCP server only: claude mcp add --transport http timetopost https://api.timetopost.co/mcp

Before using tools

1. Call whoami to confirm your user, active workspace and credential permissions.
2. Call get_capabilities for the current capability map, platform availability and workflow rules.
3. Call list_integrations to check connected accounts and their health.

Confirm the intended workspace before creating drafts, scheduling or publishing. Draft-only credentials can prepare drafts; actions that schedule or publish content require publish permission. Account permissions, workspace scoping, validation and plan limits are enforced by the TimeToPost API.

Tools

Discover the available tools through your client's MCP tool list and use get_capabilities for current workflow details. The 70 hosted tools by area:

For example, ask your assistant to prepare X post drafts for review, recommend posting times from your engagement history, or summarize recent post performance.

Local setup: stdio from source

For clients that use a local stdio process, install from this public repository. You need Git, Node.js 18 or later, npm and a TimeToPost API token from Settings → API.

git clone https://github.com/MelMayssonOwen/timetopost-mcp.git

cd timetopost-mcp npm install npm run build

Run the install and build commands from the repository root. The built entry point is dist/src/index.js.

Configure your MCP client to launch it with Node.js:

{

"mcpServers": { "timetopost": { "command": "node", "args": ["/absolute/path/to/timetopost-mcp/dist/src/index.js"], "env": { "TIMETOPOST_API_URL": "https://api.timetopost.co", "TIMETOPOST_API_TOKEN": "REPLACE_WITH_YOUR_API_TOKEN" } } } }

Replace the example path with the absolute path to your checkout and configure the token through your client's environment or secret settings. Keep tokens out of version control. TIMETOPOST_API_URL defaults to https://api.timetopost.co. You can optionally set TIMETOPOST_ORG_ID to select a workspace your account can access; confirm the selection with whoami.

After connecting, use the checks in Before using tools to verify your setup.

License

MIT