New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

postraid-mcp

Package Overview
Dependencies
Maintainers
1
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

postraid-mcp

Postraid MCP connector for Claude Desktop and other stdio clients

Source
npmnpm
Version
1.1.0
Version published
Weekly downloads
49
-90.54%
Maintainers
1
Weekly downloads
 
Created
Source

Postraid MCP

Create and manage social content for your brand.

get_profile reads your account. list_brands, list_posts and get_post browse your own workspace content. create_post_draft saves an editable carousel with placeholder backgrounds. No generation, publishing, scheduling or credit spending.

Remote MCP

Use https://mcp.postraid.com/mcp in a client that supports remote MCP with OAuth. Sign in to Postraid and explicitly approve the connection.

Claude Desktop and other stdio clients

Requires Node.js 22 or newer. Add this configuration:

{
  "mcpServers": {
    "postraid": {
      "command": "npx",
      "args": [
        "-y",
        "postraid-mcp"
      ]
    }
  }
}

Or install the .mcpb file from Releases in your desktop client's Extensions settings. The connector opens your browser for sign-in. If the consent page asks you to sign in, use its new-tab link, then return and refresh the consent page.

Privacy and permissions

Existing profile-only connections must reconnect and approve the new permissions to use content tools. The consent screen lists the requested permissions. Your product password and provider credentials are not requested by this package. The pinned mcp-remote bridge handles OAuth, PKCE and local token storage. It connects only to the fixed endpoint above; command-line endpoint overrides are not supported. OAuth tokens are stored locally by mcp-remote and should be treated as credentials.

Revoke a connection at Postraid MCP connections.

Development and publishing

Run npm ci and npm test. GitHub Actions publishes a new package version using the organization’s NPM_TOKEN secret, then builds and releases the desktop bundle. Keep package.json, manifest.json, server/config.json and server.json versions aligned.

Marketplace approval is separate from npm publication. See the product’s submission notes for endpoint tests and review prerequisites.

Website · Issues

Keywords

mcp

FAQs

Package last updated on 21 Sep 2026

Related posts