What it is
MCP (Model Context Protocol) is the standard way AI assistants use outside tools. Postbing runs a remote MCP server, so there is nothing to install. You give your assistant one address and one API key:
https://www.postbing.com/mcpAfter that you can say things like "write a post about our spring sale and publish it to my store" or "what is scheduled on my blog this week?" and the assistant does it through Postbing.
Get an API key
- Sign in to Postbing and open Account settings, API access.
- Click Create API key and copy it. It starts with
pb_and is shown once. - Keep it private, like a password. Anyone with the key can publish to your sites. You can revoke it on the same page at any time.
API keys are included with the Agency plan. See plans.
Connect your client
In every example, replace pb_your_key with your own key.
Claude Code
claude mcp add --transport http postbing https://www.postbing.com/mcp --header "Authorization: Bearer pb_your_key"Cursor
Add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"postbing": {
"url": "https://www.postbing.com/mcp",
"headers": { "Authorization": "Bearer pb_your_key" }
}
}
}Claude Desktop
Claude Desktop's config file starts local programs, so it reaches a remote server through the small mcp-remote bridge (needs Node.js). Open Settings, Developer, Edit Config and add:
{
"mcpServers": {
"postbing": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://www.postbing.com/mcp",
"--header", "Authorization:${POSTBING_AUTH}"
],
"env": { "POSTBING_AUTH": "Bearer pb_your_key" }
}
}
}ChatGPT and other clients
Any client that supports remote MCP servers over Streamable HTTP and lets you set a request header works. Give it the address above and this header:
Authorization: Bearer pb_your_keyTo check the connection yourself:
curl -s https://www.postbing.com/mcp \
-H "Authorization: Bearer pb_your_key" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Tools
Your assistant picks the right tool by itself. This is what it can do:
| Tool | What it does |
|---|---|
list_sites | List the Postbing sites this API key can use, each with its connected publishing platform (WordPress, Shopify, Webflow, Ghost, Notion, webhook or the hosted Postbing blog), the connection status and the publish mode. Start here to get a site_id. |
list_articles | List a site's articles, newest change first: id, title, status, scheduled date and live URL. Skipped (archived) articles are left out unless you ask for that status. |
get_article | Read one article: title, slug, SEO title and description, tags, status, scheduled date, live URL and the full body. |
create_article | Save an article you wrote as a draft on a site. Nothing goes live and no article credit is used. Follow with publish_article to send it to the site's connected platform. |
generate_article | Ask Postbing to research and write an article for a keyword, in the site's voice and settings. Uses one article credit from the site owner's plan. Writing takes a few minutes: poll get_article until the status is draft. |
update_article | Change an article's title, body, SEO fields, slug, keyword or tags. Only the fields you send change, and the previous version is kept in the article's history. If the article is already live, the live post is updated on the site too. |
publish_article | Send an article to the site's connected platform. mode 'publish' (default) makes it live now and returns the live URL; on an article that is already live it pushes the latest text. mode 'schedule' publishes it on the given date. Publishing twice never creates a duplicate post. |
unpublish_article | Take a live article off the site (removed or moved to drafts there, depending on the platform). In Postbing it becomes a draft again and keeps its text. |
list_integrations | List the publishing platforms Postbing can connect a site to. |
test_connection | Check that Postbing can still publish to a site: signs in and, where the platform allows it, creates and deletes a private test draft. Returns each step and what to fix. Needs admin access to the site. |
A typical run: list_sites, then create_article with the text the assistant wrote, then publish_article. The answer includes the live URL.
Limits and safety
- Your sites only. A key reaches the sites on its own account, plus team sites with the role you were given there. Viewers can read, editors can write and publish, admins can also test the connection.
- Article credits.
generate_articleuses one article credit from the site owner's plan, the same as writing in the app. Saving and publishing your own text withcreate_articleuses none. - No duplicate posts. Publishing the same article again updates the existing post.
- History. Every edit keeps the previous version in the article's history in Postbing.
- Rate limit. 120 requests a minute. Publishing now can take up to a minute or two while your site answers.
- Technical details. Streamable HTTP, JSON responses, no sessions. Protocol versions 2025-03-26, 2025-06-18 and 2025-11-25.
Building your own integration instead? See the REST API and webhooks.