
TimeToPost
io.github.MelMayssonOwenPublished by GitHub account MelMayssonOwenv0.3.1Updated Nov 2, 2026
Official TimeToPost MCP server for social post drafting, scheduling, publishing and approval queues.
Overview
Official TimeToPost MCP server that lets an assistant draft, schedule, approve and publish social media posts across 16 networks, with analytics and SEO tools.
- What you can do
- Check account, workspace, connected integrations and available capabilities
- List, create, schedule, publish, cancel and thread posts
- Create drafts and digests, then approve or reject them in an approval queue
- Upload media, generate short videos and check their status
- Read engagement summaries, per-post metrics and recommended posting times
- Run AutoSEO article workflows and keyword, SEO and GEO research
- When to use it
- Use it when you want an assistant to prepare and schedule social posts, keep a human approval step before anything goes live, or pull engagement data and posting-time suggestions from your own history.
- Requirements
- Remote Streamable HTTP endpoint with OAuth browser sign-in; no local install or API key needed. A local stdio option requires Git, Node.js 18 or later, npm, and a TimeToPost API token set as TIMETOPOST_API_TOKEN, with optional TIMETOPOST_API_URL and TIMETOPOST_ORG_ID. A TimeToPost account and workspace are required.
Installation
In SourceWeft
- Open TimeToPost in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.MelMayssonOwen%2Ftimetopost-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"timetopost": {
"type": "http",
"url": "https://api.timetopost.co/mcp"
}
}
}README
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
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:
For Cursor, VS Code, Windsurf, Claude Desktop (via a remote connector) and other clients that accept URL-based MCP configuration:
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.
Then sign in to TimeToPost when Claude Code prompts for MCP authentication.
Other ways to install:
- Skill only, any harness that reads
SKILL.mdfolders. Copyplugins/timetopost/skills/schedule-social-postsinto~/.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
- Call
whoamito confirm your user, active workspace and credential permissions. - Call
get_capabilitiesfor the current capability map, platform availability and workflow rules. - Call
list_integrationsto 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.
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:
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
Source: README.md at commit f99c889
Tools
0Version history
1- v0.3.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts