AI assistants

Connect an AI assistant to review a schedule or prepare a publication without leaving the conversation. OpenPost uses Model Context Protocol (MCP) to let the assistant access only the work your account permits. Hosted clients connect to:

https://app.openpo.st/mcp

Choose mcp:read to review accounts and scheduled posts. Choose mcp:full only when the assistant needs to create, edit, schedule, or publish. OpenPost checks your workspace access on each request.

Choose a setup

Choose its guide below. Each guide shows where to enter the server URL, how to sign in, and a first read request. Start with "List my OpenPost workspaces" so you know which workspace the assistant can see.

ChatGPTClaude webClaude DesktopClaude CodeCursorCodexGrokDevinPerplexityGemini CLIGitHub CopilotVS CodeAntigravityOpenCodeOpenClawHermes Agent

For a client not listed here, use the endpoint and authentication rules in Tools and permissions.

Remote clients can use browser sign-in. OpenPost asks you to choose mcp:read or mcp:full and, optionally, bind access to one workspace. If your client cannot use OAuth, create a developer token in Settings → Personal → Developer and pass it in a bearer header. Do not put a token in a chat message or a committed config file.

Self-hosted connections

For a public HTTPS instance, replace https://app.openpo.st with your own origin and keep the /mcp path. Use that URL in the client guide above.

Cloud clients cannot reach a private LAN address or localhost. If the server is private but reachable from your computer, a desktop client can use OpenPost's local bridge. Install the CLI and bridge together:

curl -fsSL https://raw.githubusercontent.com/getopenpost/openpost/main/scripts/install-cli.sh | sh -s -- --with-mcp

Sign in using a named profile:

openpost --profile local auth login https://your-openpost-host.example

Configure your desktop MCP client to launch the bridge with the same profile:

{
  "mcpServers": {
    "openpost": {
      "command": "openpost-mcp",
      "args": ["--profile", "local"]
    }
  }
}

The client launches openpost-mcp; you do not need to keep a separate terminal running. If it cannot find the command, use the full path printed by command -v openpost-mcp.

Check what the assistant can do

Ask, "List my OpenPost workspaces," then name the workspace you want to use. Next ask, "Review this week's schedule without changing anything." If that succeeds and you granted mcp:full, try an unpublished draft before asking the assistant to schedule or publish. Inspect the result in Publications. If a request fails, use the troubleshooting steps in your client guide.