PostNext MCP MCP server

The PostNext MCP server enables AI assistants to manage social media operations across seven platforms including X, Instagram, LinkedIn, TikTok, YouTube, Threads, and Bluesky. It allows users to schedule, draft, and audit posts using natural language commands while maintaining security through OAuth authentication. The server supports features like content planning, draft creation, queue auditing, and channel management without auto-publishing, ensuring user control over final content release.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by PostNext

MCP endpoint (Streamable HTTP)

https://mcp.postnext.io/api

Vendor documentation

What you can do with it

Plan a week of social media posts across multiple platforms
Draft threads or posts from URLs using brand voice
Audit scheduled queues for duplicates or posting gaps
Connect and manage social media channel accounts

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http postnext-mcp https://mcp.postnext.io/api

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add postnext-mcp --url https://mcp.postnext.io/api

Cursor

Merge this server into .cursor/mcp.json in your project, then enable postnext-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "postnext-mcp": {
      "url": "https://mcp.postnext.io/api"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "postnext-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.postnext.io/api",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start postnext-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "postnext-mcp": {
      "type": "http",
      "url": "https://mcp.postnext.io/api"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http postnext-mcp https://mcp.postnext.io/api

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "postnext-mcp": {
      "url": "https://mcp.postnext.io/api"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "postnext-mcp": {
      "serverUrl": "https://mcp.postnext.io/api"
    }
  }
}

See all 347

Do you run PostNext MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing