TimeToPost MCP server
online · 100% uptimeOfficial TimeToPost MCP server for social post drafting, scheduling, publishing and approval queues.
0 stars
Reviews
Write oneNobody has reviewed TimeToPost yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
TimeToPost tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 246ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 5 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How TimeToPost compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 97/100
- higher than 98% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 594 ms
- faster than 27% of 30,027 servers
Install TimeToPost in Claude Code, Cursor or VS Code
claude mcp add --transport http timetopost-mcp https://api.timetopost.co/mcp
What the publisher says
From the TimeToPost repository's README, as published. We do not edit it. Read it on GitHub
TimeToPost MCP server
The official Model Context Protocol server for TimeToPost: draft, schedule and publish social posts, manage approval queues, read analytics and run AutoSEO workflows from your AI assistant.
X publishing is live and generally available. Other social providers are capability-gated. Availability depends on your workspace's enabled capabilities and connected accounts; call getcapabilities and listintegrations before planning a provider-specific workflow.
- 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:
claude mcp add --transport http timetopost https://api.timetopost.co/mcpFor 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.
Before using tools
and workflow rules.
- Call whoami to confirm your user, active workspace and credential permissions.
- Call get_capabilities for the current capability map, platform availability
- 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.
Tool examples
Discover the available tools through your client's MCP tool list and use get_capabilities for current workflow details.
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 buildRun 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"
}
}
}
}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
TimeToPost: common questions
- Is TimeToPost MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the TimeToPost safety report
- How do I install TimeToPost?
- It runs remotely at api.timetopost.co. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does TimeToPost need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is TimeToPost maintained?
- The last commit was 25 days ago (2026-10-11). The latest release is v0.3.1.
- Is TimeToPost up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does TimeToPost compare with other MCP servers?
- safety score 97/100 (higher than 98% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 594 ms (faster than 27% of 30,027 servers). Full comparison.