Get Posting API and MCP developer resources

There are two supported ways to automate Get Posting. Connect an AI assistant through MCP, or call API v1 from a server you control. Both use the same workspace, validation rules, and publishing services as the dashboard.

Choose the access path that matches the job

MCP for AI assistants

You want ChatGPT, Claude, or another compatible assistant to work inside one Get Posting workspace.

Endpoint: https://getposting.com/mcp
Authentication: OAuth sign-in and workspace consent. No API key.
Protocol: MCP 2026-07-28 over stateless Streamable HTTP. The same URL still serves 2025-era clients.

Read the 2026-07-28 specification See the MCP server and setup guide

REST API v1 for your server

You are building your own server-side workflow, script, or integration against a Get Posting workspace.

Endpoint: https://getposting.com/api/v1
Authentication: Workspace API key created by an owner or admin in Settings → API.

Read the OpenAPI specification

What both interfaces protect

Access stays inside the authenticated Get Posting workspace.
Social accounts must be connected in Get Posting before either interface can use them.
Draft creation is separate from publishing, and every publish is validated again server-side.
Public responses use Get Posting IDs and concepts instead of provider credentials or internal IDs.

Current access limits

MCP grants one approved workspace to one connected client. Membership, consent, billing access, and role permissions are checked again on every request.

REST API keys are workspace-wide server credentials without per-key scopes. They must not be placed in browser code, mobile apps, repositories, logs, or URLs.

Neither interface connects social accounts or bypasses a platform rule. Use the dashboard for account connection, billing, team membership, and anything the published MCP tools or API contract do not expose.