The postpeg MCP server

Set it up in your client

Replace pp_live_your_key with your key. Config files hold it in plain text, so keep them out of version control.

1. Claude Code

   Run in a terminal. Add --scope user to use it in every project.

   TerminalCopy Claude Code code

   claude mcp add --transport http postpeg https://mcp.postpeg.com/mcp \
     --header "Authorization: Bearer pp_live_your_key"

2. Claude Desktop

   Settings → Developer → Edit Config, then add this to claude_desktop_config.json and restart Claude Desktop.

   JSONCopy Claude Desktop code

   {
     "mcpServers": {
       "postpeg": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://mcp.postpeg.com/mcp",
           "--header",
           "Authorization:${POSTPEG_AUTH}"
         ],
         "env": {
           "POSTPEG_AUTH": "Bearer pp_live_your_key"
         }
       }
     }
   }

   Claude Desktop’s config file starts local servers, so the mcp-remote bridge (needs Node.js) forwards to the hosted server. The header value sits in env because some systems split arguments on spaces.

3. Cursor

   Add to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project).

   JSONCopy Cursor code

   {
     "mcpServers": {
       "postpeg": {
         "url": "https://mcp.postpeg.com/mcp",
         "headers": {
           "Authorization": "Bearer pp_live_your_key"
         }
       }
     }
   }

4. VS Code

   Add to .vscode/mcp.json in your workspace, or run “MCP: Open User Configuration”.

   JSONCopy VS Code code

   {
     "servers": {
       "postpeg": {
         "type": "http",
         "url": "https://mcp.postpeg.com/mcp",
         "headers": {
           "Authorization": "Bearer pp_live_your_key"
         }
       }
     }
   }

Other clients that support remote MCP servers with custom headers work the same way: the URL above, and the Authorization header. Then try: “List my postpeg accounts, then check this post for X and LinkedIn without publishing it.”