PublishQ

com.publishqPublished by publishq.comOfficial publisherv1.0.0Updated Nov 4, 2026

Schedule and publish posts, organize media into folders, and keep each brand in its own workspace.

VerifiedStreamable HTTPWeb executableBusiness & CommerceMedia & Design

Overview

AI-generated overview

PublishQ lets an assistant schedule and publish social posts, organize media into folders, and keep each brand in its own workspace.

What you can do
  • Schedule and publish posts from the assistant.
  • Organize media into folders.
  • Keep each brand separated in its own workspace.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to draft, queue and publish posts on a schedule, and to keep media and brands organized without switching to the PublishQ app for each step.
Requirements
A PublishQ account with OAuth sign-in. Either a PublishQ API key supplied as the PUBLISHQ_API_KEY environment variable, or a prior sign-in with the PublishQ CLI login command, which removes the need for the key. Available as a remote endpoint or as the npm package @publishq/mcp over stdio.
Before you install
The API key is a live credential and should be treated as a secret. The server publishes content publicly and changes workspace and media data, so review scheduled posts before they go out. Publishing sends content to PublishQ and the connected social platforms.

Installation

In SourceWeft

  1. Open PublishQ in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.publishq%2Fpublishq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.