RepeatPost MCP Server

Schedule and publish social media posts, write captions and create branded graphics with RepeatPost, from Claude or any MCP client.

Documentation · MCP server page · Website · Directories · Support

Overview

RepeatPost MCP is a remote, hosted Model Context Protocol server. Add one URL to your AI assistant, sign in to RepeatPost in your browser, and choose what the assistant may do. It then works with the channels connected to your RepeatPost workspace and stays within your workspace role.

There is nothing to install or run. This repository holds the server's public metadata and documentation, not its source code. The server itself runs at https://api.repeatpost.com/mcp.

Connection details

Key features

• Publish to 15 platforms. Create drafts, schedule, publish, edit and reschedule posts on any connected channel. Send one post to several channels at once as a post group, with a status for each channel and a retry for the failed ones.
• Captions in your brand voice. The assistant writes ready-to-publish captions in the brand voice that applies. Each caption costs 1 AI credit.
• Branded graphics without an image model. The assistant designs a layout as SVG and RepeatPost renders it to a PNG, using your brand colours and logo. It can also add your logo to a photo.
• Media library. Search, browse, upload, organise, rename, favourite and delete files and folders.
• Workspaces and brand voices. List and switch workspaces, see which brand voice applies, and set the default one.
• You choose the permissions. Five OAuth scopes, each with its own checkbox on the consent screen. The workspace role is always the ceiling, and channel approvals still apply.
• Standard MCP sign-in. OAuth 2.1 with dynamic client registration and PKCE. Credentials never pass through the AI client or the model.
• Annotated tools. Every tool carries MCP tool annotations, so clients can ask before running destructive ones.

What it doesn't do

• AI images and videos. Create them in the RepeatPost app, then ask your assistant to schedule them from the media library.
• Connecting channels. Connect social channels in the RepeatPost app.
• Accounts and billing. Create an account and change plans in the RepeatPost app.

Supported social media platforms

An assistant can publish to any channel connected in RepeatPost, on 15 platforms:

MCP tools

The server exposes 35 tools in seven groups. tools.json holds the full tools/list output: names, titles, descriptions, input schemas and MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). The Scope column refers to the OAuth scopes.

Channels

Posts

Media library

Branded graphics

Brand voice

AI captions

Workspaces and credits

These tools are marked destructiveHint: true, so clients can ask the user before running them: updatePost, deletePost, deletePostGroup, publishPostGroup, mediaRename, mediaDelete and setDefaultBrandVoice.

Graphic sizes and fonts

No AI image model is involved. The assistant designs the layout as SVG, and RepeatPost renders it to a PNG in the media library.

Text can be set in Inter, Montserrat, Poppins, Playfair Display or Roboto, and the design can use the colours and logo from the workspace's brand voice. brandImage puts the brand logo on a photo from the media library and saves a new copy, so the original never changes.

AI credits

Only captions cost AI credits. Everything else is free.

Installation and setup

There is nothing to install. You add the server URL to your AI client and sign in.

Before you connect

• You need a RepeatPost account.
• Connect your social channels in the RepeatPost app first. An assistant can only use channels that are already connected.

Connect in four steps

1. Add https://api.repeatpost.com/mcp as a remote MCP server in your client. See Client configuration.
2. Sign in to RepeatPost on the page your client opens in the browser.
3. On the consent screen, untick anything you don't want to allow, then approve. See Permissions (OAuth scopes).
4. Ask your assistant to do something, for example one of the example workflows.

Authentication and OAuth

The server uses the standard MCP authorization flow. Credentials never pass through the AI client or the model: the user signs in on RepeatPost's own page in their browser, and the client receives OAuth tokens.

1. An unauthenticated request to /mcp returns 401 with a WWW-Authenticate header that points to the protected resource metadata.
2. The client reads the metadata, registers itself (RFC 7591 dynamic client registration) and opens the authorization page in the browser.
3. The user signs in, reviews the consent screen and approves.
4. The client exchanges the authorization code for tokens (PKCE S256) and calls /mcp with Authorization: Bearer <access_token>.

The scopes a token can carry are listed under Permissions (OAuth scopes).

Client configuration

Claude (web and desktop)

1. In Claude, open Settings, then Connectors, and select Add custom connector.
2. Paste https://api.repeatpost.com/mcp and select Connect.
3. Sign in to RepeatPost on the page that opens.
4. On the consent screen, untick anything you don't want to allow, then approve.

Claude Code

claude mcp add --transport http repeatpost https://api.repeatpost.com/mcp

Then run /mcp in Claude Code, select repeatpost and authenticate in your browser.

Cursor

Add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "repeatpost": {
      "url": "https://api.repeatpost.com/mcp"
    }
  }
}

VS Code

Add this to .vscode/mcp.json:

{
  "servers": {
    "repeatpost": {
      "type": "http",
      "url": "https://api.repeatpost.com/mcp"
    }
  }
}

Clients that only support stdio

Use mcp-remote as a bridge:

{
  "mcpServers": {
    "repeatpost": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.repeatpost.com/mcp"]
    }
  }
}

Any other MCP client

Any client that supports remote MCP servers with OAuth sign-in can connect. Add a remote server with the URL https://api.repeatpost.com/mcp and sign in when asked.

Example workflows

• "Schedule a post about our weekend sale to Instagram and LinkedIn for Friday at 9am."
• "Make a square post announcing our 20% weekend sale in our brand style and save it as a draft."
• "Add our logo to the summer product photo in my media library."
• "What's scheduled for next week, and did any posts fail?"
• "Write three LinkedIn captions about our new feature in our brand voice."

Tool permissions and security

Permissions (OAuth scopes)

The consent screen lists five permissions, each with its own checkbox. A token carries only the scopes the user approved.

Two rules apply whatever the user approves:

• The workspace role is the ceiling. An assistant can never do more than the user's role allows. A Viewer can only read.
• Approvals still apply. If posts on a channel need approval, posts scheduled there by an assistant go to approval first.

Security and privacy

• Sign-in happens on RepeatPost's own page. The assistant never sees the user's password.
• Each token carries only the permissions the user approved, and never more than the user's workspace role.
• By default, deleting a post removes it from RepeatPost only. Deleting it on the platform as well needs an explicit request from a workspace Owner.
• To disconnect, remove the RepeatPost connector in your assistant's settings, or email support@repeatpost.com to have its access revoked.

Read AI assistants and connectors in the RepeatPost Privacy Policy, and the Terms of Service.

To report a security issue, follow SECURITY.md or email support@repeatpost.com.

Troubleshooting

Directory listings

RepeatPost is listed in these MCP directories:

Support

• Documentation: help.repeatpost.com/integrations/mcp-server
• MCP server page: www.repeatpost.com/mcp
• Website: www.repeatpost.com
• Email: support@repeatpost.com
• Bugs and tool requests: GitHub issues
• Security: SECURITY.md

See SUPPORT.md for what to include when you ask for help.

Repository contents

License

The contents of this repository are released under the MIT License. The hosted RepeatPost service is governed by the RepeatPost Terms of Service. The RepeatPost name and logo are trademarks of RepeatPost and are not licensed for use outside of referring to RepeatPost.