HumanPost MCP server

HumanPost MCP and agent plugins

Official integration package for HumanPost: manage social accounts, prepare video and image drafts, queue approved content, and inspect human posting status and analytics from an AI assistant.

HumanPost operates a hosted MCP service. This repository contains client configuration and a publishing skill; it does not contain the hosted server implementation. A HumanPost account and company access are required. OAuth-capable clients use HumanPost sign-in; company-scoped API keys remain available for manual configurations. Service usage and some actions may incur charges under your HumanPost plan.

Connect

• Transport: Streamable HTTP
• Endpoint: https://humanpost.com/mcp
• Authentication: OAuth 2.1 authorization code with S256 PKCE and dynamic client registration. Company-scoped API keys are also supported.
• Setup and tools · API reference · Complete agent documentation

Create a key under Dashboard → Settings → API & MCP. Start with accounts:read and add only the scopes your workflow needs. Each key belongs to one company. Store it in your client's secret configuration; never commit it or paste it into a conversation. OAuth users select one company and minimum permissions in the consent screen. Writes are off by default. Access tokens expire after 15 minutes; refresh tokens rotate and expire after seven days. Revoke a connection under Settings → API Keys. No credential is included in this package.

Cursor

The Cursor plugin uses the canonical OAuth endpoint. Install it and use Cursor’s Connect action to sign in to HumanPost. For manual setup:

{
  "mcpServers": {
    "humanpost": { "url": "https://humanpost.com/mcp" }
  }
}

If you use a company API key instead, configure an Authorization header in your private Cursor settings with Bearer ${env:HUMANPOSTAPIKEY}.

Cline

Merge config-cline.json into Cline's MCP settings. Replace YOURHUMANPOSTAPIKEY in your local settings with your scoped key. Keep that settings file private. The transport value is streamableHttp; keep autoApprove empty and review tool calls. Cline CLI uses ~/.cline/data/settings/clinemcpsettings.json by default and supports CLINEMCPSETTINGSPATH for an isolated configuration.

Claude Code

Add this repository as a marketplace, then install the plugin:

/plugin marketplace add HumanPost-co/humanpost-mcp
/plugin install humanpost@humanpost

Set HUMANPOSTAPIKEY in the process environment before launching Claude Code. Alternatively, use the .mcp.json entry in your project. The compatibility .mcp.json uses an environment-supplied API key. For native OAuth instead, run claude mcp add --transport http humanpost https://humanpost.com/mcp and use Claude Code’s MCP authentication flow. Claude web directory approval is separate from installing this plugin.

Grok Build

Grok Build supports Claude-compatible plugins. Add the repository using its plugin marketplace command:

grok plugin marketplace add HumanPost-co/humanpost-mcp

Install humanpost from the Marketplace tab and supply HUMANPOSTAPIKEY in the client environment. The package includes both .grok-plugin/plugin.json and .claude-plugin/plugin.json. Review the configured MCP before enabling it. Official marketplace inclusion is separate from adding this publisher's marketplace.

Grok Bot

Grok Bot has a separate app-directory submission form, which also covers Cursor. The Grok Build CLI instructions above apply to Build; they do not install the Bot app plugin. This repository includes the Cursor marketplace manifest and the canonical OAuth MCP entry for app-directory review.

Shortened. The full README is on GitHub.