PostFuze

Claude Desktop

Claude Desktop connects to local MCP servers over stdio, so the remote PostFuze server is bridged with mcp-remote — a tiny adapter run on demand via npx that forwards stdio to our Streamable HTTP endpoint. Once configured, all 32 PostFuze toolsappear in Claude’s tool picker and it can publish, schedule and report on your behalf using the same sk_live_… key as the REST API.

Using Claude Code instead?

Claude Code speaks Streamable HTTP natively, so it needs no bridge — register the server with one command. See the setup guide.

Where the config file lives

Claude Desktop reads its MCP servers from claude_desktop_config.json. The fastest way to open it is Settings → Developer → Edit Config, which reveals the file in your OS file manager. Its location:

OSPath
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json

Add the PostFuze server

Add a postfuze entry under mcpServers. The --header flag carries your bearer token to the remote server. Replace sk_live_… with your key:

claude_desktop_config.json
{
  "mcpServers": {
    "postfuze": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.postfuze.com/api/mcp",
        "--header",
        "Authorization: Bearer sk_live_…"
      ]
    }
  }
}

Save the file and fully restart Claude Desktop (quit and reopen — a window reload is not enough). The first launch downloads mcp-remote via npx, so it may take a few seconds.

Prerequisites & header quoting

mcp-remote needs Node.js 18+ on your PATH so npx is available. If your environment strips the space in the header value, some setups accept the colon-delimited form "Authorization:Bearer sk_live_…" instead.

Confirm it loaded

After restart, open a new chat and click the tools (slider) icon in the composer. You should see postfuze listed with its 32 tools. If it’s missing, re-open Settings → Developer — a failed server shows there with its error log.

Example prompts

With the server loaded, just ask. Claude resolves account IDs and chains the right tools automatically:

prompts
"List my connected social accounts, then draft a post for the X one
 introducing our new docs and schedule it for tomorrow at 10am."

"Post a thread to LinkedIn: the first post is our Q2 recap, followed by
 three follow-up points I'll paste below."

"What's my current usage this billing period — how many posts have I
 published and how many are included in my plan?"

The first prompt drives list_social_accounts then create_post with scheduled_at; the second uses create_post with thread_content; the third calls get_account_usage. Claude will surface a confirmation before any publish action that isn’t a draft.

Publishing video & per-platform fields

To post a video, ask Claude to upload it first: it chains upload_media → confirm_media_upload, waits for the asset to reach ready, then attaches it to create_post. Some platforms need an extra field (e.g. a Pinterest board), which Claude can resolve with tools like list_pinterest_boards. See publishing a video with an agent and media processing & limits.

Next steps