TimeToPost

npx add-mcp 'https://api.timetopost.co/mcp'

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 get_capabilities and list_integrations 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/mcp

For 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

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.

Tool examples

Discover the available tools through your client's MCP tool list and use get_capabilities for current workflow details.

Workflow	Example tools
Account and capabilities	whoami, get_capabilities, list_integrations
Posts and publishing	list_posts, get_post, schedule_post, publish_post, cancel_post, publish_thread
Drafts and approvals	create_drafts, list_drafts, approve_draft, reject_draft, list_approvals
Analytics and timing	get_engagement_summary, get_optimal_times, get_post_metrics, scheduler_status
AutoSEO	autoseo_connect_site, autoseo_integration_kit, autoseo_verify_site, autoseo_list_sites, autoseo_configure, autoseo_generate_post

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