Setup
Client configuration for the Onepostly MCP server, access levels, revoking access, and connection errors.
Add the Onepostly MCP server to your AI client, then approve access once in your browser.
Before You Start
- A Onepostly workspace with at least one connected social account. See Connect an Account.
- An MCP client that supports remote servers over Streamable HTTP with OAuth and MCP protocol version
2025-11-25. For a client that only runs local servers, use the Other tab below.
Connect Your Client
Add https://mcp.onepostly.com to your client with the configuration for your client below.
Start the connection. The client opens a browser window. Sign in to Onepostly if you are not signed in.
Review the consent screen. It names the client, the workspace it connects to, and the access it requests. Click Allow. To connect a different workspace, make it the active workspace in the dashboard and start again.
Ask the assistant to list your connected accounts. A list of accounts confirms the connection works.
Add the server:
claude mcp add --transport http onepostly https://mcp.onepostly.comThen run /mcp inside Claude Code, select onepostly, and authenticate in the browser.
Access Levels
The client asks for one or both scopes, and the consent screen shows what it asked for. A client that asks for no scope gets both.
| Scope | Consent screen | Tools |
|---|---|---|
mcp:read | Read your workspace | connections_list, publish_options, posts_list, posts_get, analytics_get |
mcp:write | Publish, schedule, and delete | All tools, including posts_create and posts_delete |
API keys from Authentication do not work on the MCP server.
Manage and Revoke Access
Open Settings → MCP Connections in the dashboard to see every connected client and its access (Read only or Read & write). Click Revoke to end a client's access immediately. The client must be approved again before it can call any tool.
A client also has to be approved again when:
- It has not connected for 30 days.
- The person who approved it leaves the workspace.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
401 with missing or invalid access token | The client was never approved, its access was revoked, it has not connected for 30 days, or the approving user left the workspace. | Authenticate again: run /mcp in Claude Code, codex mcp login onepostly in Codex, or remove the server from your client and add it again. |
403 with Insufficient scope: mcp:write is required for <tool> | The client was approved with read-only access and called posts_create or posts_delete. | Reconnect the client and approve write access. If it asks for read access again, remove the server and add it again. |
400 with Unsupported protocol version | The client speaks an MCP protocol version other than 2025-11-25. | Update the client to a version that supports 2025-11-25. |
402 with PAYMENT_METHOD_REQUIRED or PAYMENT_PAST_DUE | The workspace has no payment method, or a charge could not be collected. Every request is refused until this is resolved. | Add or update the payment method in Settings → Billing. |
429 with RATE_LIMITED | The workspace reached its API rate limit. | Wait the number of seconds in the Retry-After header. See Handle 429 Responses. |
| The server shows no tools, or config changes have no effect | The client did not reload its MCP configuration. | Restart the client completely. |
Errors returned by a tool itself (for example ACCOUNT_NOT_FOUND) are listed in Tools.