Choose a local API-key server or a curated remote connector

The remote connector at the URL below uses OAuth, so you sign in to PostQuickAI instead of copying an API key. It is not an official directory listing or a compatibility certification for any AI client.

Client menus, availability, and directory status can change. This page does not claim a live-tested integration, official listing, or confirmed compatibility with Claude, ChatGPT, Muse, or any other client. Existing connections affected by the OAuth security update must reconnect; disconnect and add the connector again if prompted to re-authorize.

The connector signs you in with OAuth — your PostQuickAI password is not shared with the client. See the MCP connector privacy notice.

The full remote connector includes model discovery, image editing, music, saved media, website research, campaign scheduling and cancellation, story edits, analytics and account health. Audio settings are rendered during video publishing. New permissions require your consent.

In ChatGPT, select PostQuickAI from the @ menu before requesting media generation. Ask for a draft first, review the result, then approve the connected destination and posting time. PQAI-generated media uses your PostQuickAI allowance and video credits.

Need help connecting or using the tools? Contact Ark Tech LLC at konark@arktechllc.net. Include the tool name and error message; do not send passwords or access tokens.

Install locally (CLI agents)

The local @postquickai/mcp stdio server uses a POSTQUICKAI_API_KEY. It is separate from the remote OAuth connector and exposes the broader generated API toolset. The configuration snippets below are format examples, not live-client compatibility certifications.

claude mcp add postquickai \
  -e POSTQUICKAI_API_KEY=pq_live_your_key \
  -- npx -y @postquickai/mcp

# Verify
claude mcp list

{
  "mcpServers": {
    "postquickai": {
      "command": "npx",
      "args": ["-y", "@postquickai/mcp"],
      "env": {
        "POSTQUICKAI_API_KEY": "pq_live_..."
      }
    }
  }
}

# ~/.codex/config.toml
[mcp_servers.postquickai]
command = "npx"
args = ["-y", "@postquickai/mcp"]
env = { POSTQUICKAI_API_KEY = "pq_live_..." }

npx -y @postquickai/mcp

Local API-key server: broad generated tools

These examples describe the local API-key server, not the remote connector. The local server generates tools from public v1 REST endpoints; clients load its current tool list when they start or restart.

Remote connector example prompts

The remote connector currently supports reads; post drafts; browser upload links for your images and videos; edits to unpublished posts; AI writing, image, and video generation; video drafts from public URLs; story drafts from public URLs or existing posts/videos; post, video, and story scheduling; and video publish or retry. It does not expose text/story immediate publishing, one-step post generation, deletion, account disconnection, or API-key administration.

Pair with Skills

MCP gives raw tools. Skills give expert workflows — opinionated, multi-step recipes that chain MCP tools with best-practice defaults. Install both.

FAQ