PublishQPublishQ

MCP Server

Run the PublishQ MCP server so any MCP client can list your connected accounts, upload media, and schedule posts across your social platforms.

Add PublishQ to your MCP client, and the assistant you already talk to can draft, schedule and publish to the accounts you have connected, and tell you what is queued. Any Model Context Protocol client works; the only thing that changes between them is which file the configuration goes in.

Hosted server

Add https://publishq.com/mcp as a remote MCP server. On first use your client opens PublishQ in your browser: sign in, choose what it may do, and click Approve. Nothing to install and no key to copy.

On claude.ai, Claude Desktop or Claude mobile, open Settings > Connectors, choose Add custom connector and paste https://publishq.com/mcp. The connector is available in Cowork too.

Turn on developer mode in Settings, then create an app with the URL https://publishq.com/mcp and OAuth as its authentication.

claude mcp add --transport http publishq https://publishq.com/mcp

Then open /mcp in a session and choose Authenticate.

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

{
  "mcpServers": {
    "publishq": { "url": "https://publishq.com/mcp" }
  }
}

Local server

The local server runs on your machine over stdio, with npx. Sign in once with the CLI and it uses that login:

npx @publishq/cli@latest login

Then register it with your client. None of these needs a key or an env block.

Add this to claude_desktop_config.json, then restart the app:

{
  "mcpServers": {
    "publishq": {
      "command": "npx",
      "args": ["-y", "@publishq/mcp@latest"]
    }
  }
}
claude mcp add publishq -- npx -y @publishq/mcp@latest

Add --scope project to write it into a .mcp.json the rest of the team shares. It holds no secret, so each person uses their own login.

codex mcp add publishq -- npx -y @publishq/mcp@latest

Codex stores it as TOML in ~/.codex/config.toml, under [mcp_servers.publishq].

Add this to ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{
  "mcpServers": {
    "publishq": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@publishq/mcp@latest"]
    }
  }
}
openclaw mcp add publishq \
  --command npx \
  --arg -y \
  --arg @publishq/mcp@latest

openclaw mcp doctor publishq --probe

Any other MCP client works the same way: run npx -y @publishq/mcp@latest after signing in.

In CI, use an API key

A job has no browser to approve a login, so set PUBLISHQ_API_KEY to a key from API Keys in its environment instead.

Configuration

VariableRequiredDescription
PUBLISHQ_API_KEYNoAn API key (pq_live_...), for CI. Not needed after pq login.
PUBLISHQ_API_URLNoOverride the API base URL. Defaults to https://publishq.com/api/v1.

Tools

ToolWhat it does
publishq_list_postsList posts, paginated
publishq_get_postGet one post by ID
publishq_create_postCreate a draft, scheduled, or immediate post
publishq_update_postChange content, media, or schedule
publishq_delete_postDelete a post
publishq_remove_post_accountRemove one account's delivery from a post
publishq_list_accountsList connected social accounts
publishq_get_tiktok_creator_infoRead TikTok privacy options before posting
publishq_list_mediaList media in the library
publishq_get_mediaGet one media item
publishq_upload_mediaUpload a local file of up to 4 GB
publishq_create_media_uploadGet a signed URL to upload a file from your own disk, up to 4 GB, and the media ID it becomes.
publishq_delete_mediaDelete a media file that no draft or scheduled post uses
publishq_list_media_foldersList media folders with their file counts
publishq_move_mediaMove media files to a folder or to the top level
publishq_rename_media_folderRename a media folder
publishq_preview_media_folder_deletionCount what deleting a folder would remove
publishq_delete_media_folderDelete a folder and its files, after the preview
publishq_list_workspacesList workspaces
publishq_get_workspaceGet one workspace
publishq_create_workspaceCreate a workspace

Send what you want

The server forwards the agent's arguments as they are, including fields it does not recognise, so any error you see is the API's own.

Keeping an agent inside bounds

  • Filter the tools. Most clients can hide individual tools. Exposing publishq_list_accounts and publishq_create_post and nothing else gives you an agent that can write posts and cannot delete them.
  • Ask for drafts and schedules. Publishing is a field on the create call, not a separate tool: a post with no scheduledAt and no publishNow is a draft that waits for you, and a scheduled post can be edited or cancelled until it fires. That, plus your client's approval prompt, is what keeps an unattended run off your accounts.
  • Scope the key. Scopes turn a whole resource on or off. posts:write covers creating, updating, deleting and publishing, so a key without it cannot draft either — useful for an agent that only needs to read.

On this page