Skip to main content

​
Add the remote server

In an MCP client that supports remote Streamable HTTP and OAuth, add:
Complete the browser authorization flow: sign in as a project admin, select the project, review the requested permissions, and connect. No local npm package or CLI login is required. The exact settings screen varies by client. This is a generic URL-based configuration; adapt the enclosing configuration to your client:
For clients without OAuth support, configure a customer API key as the HTTP Authorization: Bearer pst_… header using the client’s credential settings. Do not put keys in the URL or tool arguments.

​
Try a read-only request

List my Postinger accounts, then show the publishing capabilities for the account I choose.
Next, try drafting with a public image URL. Hosted uploads accept HTTPS URLs, not paths on your computer. For local files, use postinger upload FILE and give the resulting media ID to the assistant.

​
Manage access

OAuth connections appear in Project settings → Connected apps. They last at most 90 days and can be disconnected at any time. Disconnecting stops further access; it does not cancel previously scheduled posts. Default requested permissions exclude post deletion. A client must explicitly request posts-delete, and you must approve it. API-key connections use the key’s own permissions and expiry.

​
Two different MCP services

The Postinger server operates on your accounts, posts, media, and analytics. A documentation search MCP supplied by your documentation host searches the docs; connect the Postinger URL above to perform product actions.