Model Context Protocol

Tempost MCP Server

Let your AI assistant run your YouTube posting. Connect Claude, ChatGPT, Cursor or any MCP client to Tempost, then ask it to upload, schedule and publish videos and Shorts, manage your calendar and read channel analytics.

Server URL (Streamable HTTP)

https://app.tempost.io/mcp

Docs and server.json on GitHub

What it does

YouTube: live Facebook Pages: coming soon Instagram: coming soon

Upload a video from a public URL and publish it now or schedule it, with title, description, tags, privacy, made-for-kids setting and translated titles.
Set a custom thumbnail, before or after the upload finishes.
Follow an upload until it is scheduled or published.
See your whole calendar: scheduled, queued, published and failed posts, including videos you uploaded outside Tempost.
Read analytics: views, watch time, subscribers, daily series and top videos.

Facebook Pages and Instagram support is coming soon. Until it is available, use the server for YouTube.

You stay in control. When you connect, you choose what the assistant may do: read, schedule, or delete. Scheduled YouTube videos stay private until their publish time, and every post an agent makes shows up in your Tempost calendar like any other.

Example prompts

"Upload this video to my YouTube channel and schedule it for Friday at 6 pm ET: https://example.com/launch.mp4"

"What is on my posting calendar for the next two weeks? Find the gaps."

"Set this image as the thumbnail of tomorrow's video: https://example.com/thumb.jpg"

"Which of my videos got the most views in the last 30 days, and how did watch time change?"

"Schedule my three new Shorts one per day at 12:00 UTC, starting Monday."

"Did my last upload finish? Give me the YouTube link."

Before you start

You need a Tempost account with an active plan and a connected YouTube channel. Create an account, pick a plan, then connect YouTube from the app.

Connect Claude

Works in Claude on the web, desktop and mobile apps. Sign-in uses OAuth, so you do not need an API key.

In Claude, open Settings, then Connectors, and choose Add custom connector.
Name it Tempost and paste the server URL. Leave the advanced settings empty.
Click Connect, sign in to Tempost, and choose the permissions you want to give (read, schedule, delete).
In a chat, turn on the Tempost connector and ask away.

https://app.tempost.io/mcp

On Team and Enterprise plans, an owner may need to add the connector for the organization first.

Claude Code

Add the server, then run /mcp inside Claude Code and choose Tempost to sign in.

claude mcp add --transport http tempost https://app.tempost.io/mcp

Connect ChatGPT

ChatGPT connects to custom MCP servers in developer mode, on plans where your workspace allows it.

In ChatGPT, open Settings, then Apps and Connectors, then Advanced settings, and turn on Developer mode.
Back in Apps and Connectors, choose Create.
Name it Tempost, paste the server URL, and set authentication to OAuth.
Confirm you trust the connector, then sign in to Tempost and choose the permissions.
In a new chat, select developer mode, enable Tempost, and ask away. ChatGPT asks you to confirm before it runs a tool that makes changes.

https://app.tempost.io/mcp

Connect Cursor and other clients with an API key

Clients that send a fixed header use an API key instead of OAuth.

Sign in at app.tempost.io and open the Agents tab.
Create an API key. It is shown once, so copy it right away. Keys belong to one workspace and can be revoked in Agents at any time.
Add Tempost to your client and send the key as a bearer token.

Cursor

Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in one project, and replace the placeholder with your key.

{
  "mcpServers": {
    "tempost": {
      "url": "https://app.tempost.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TEMPOST_API_KEY"
      }
    }
  }
}

Claude Code with an API key

claude mcp add --transport http tempost https://app.tempost.io/mcp \
  --header "Authorization: Bearer YOUR_TEMPOST_API_KEY"

Keep your key out of shared files and source control. Anyone with the key can act in your workspace within its limits.

Tools

Every tool is marked read-only or destructive, so your client can ask before it changes anything.

Tool	What it does
`list_channels`	Lists the channels connected to your workspace, with their ids and what each one supports. Read-only
`list_posts`	Lists scheduled, queued, published and failed posts, plus recent uploads on your YouTube channel. Filter by time, channel and status. Read-only
`get_post`	Gets one post with its status, times, text, media and link. Use it to follow an upload until it is scheduled or published. Read-only
`create_post`	Uploads a video from a public URL or an uploaded file and publishes it now or schedules it, with title, description, tags, privacy, translations and an optional thumbnail. Writes
`update_post`	Changes the text or time of a post that has not been uploaded yet, sets a custom thumbnail on a YouTube video, and adds translated titles and descriptions. Writes, can change existing posts
`delete_post`	Removes a post from Tempost before it goes out, or a published one from your Tempost calendar. YouTube videos that are already uploaded are not deleted; the tool says so and changes nothing. Destructive
`upload_media`	Downloads an image or video from a public URL into Tempost and returns a media id for `create_post`. Up to 1 GB, kept for 7 days. Writes
`get_analytics`	Channel or video analytics for the last 7, 30 or 90 days: views, watch time, subscribers, daily series and top videos. YouTube data lags 1 to 3 days. Read-only

Limits and pricing

The MCP server is included in every Tempost plan at no extra cost. It uses your plan and its channel limit; creating posts needs an active plan. See pricing.
120 requests per minute and 60 writes per hour per connection.
Up to 6 YouTube uploads per 24 hours, to stay within YouTube's API quota.
Media up to 1 GB from public http or https URLs. Supported files: MP4, MOV, WebM, MKV, JPEG, PNG, GIF, WebP.
Scheduled times must be at least 15 minutes ahead and include a time zone.

Security and privacy

OAuth 2.1 with PKCE, short-lived access tokens and rotating refresh tokens. API keys and tokens are stored only as hashes. You can see and revoke connected apps and keys in the Agents tab. Read how we handle data from AI assistants in our Privacy Policy, and see our Terms of Service.

Help

Stuck connecting a client? Email support@tempost.io or use the contact page.