SOCIAL MEDIA API · MCP
Publish from your code — or your AI agent
One REST API for your automations and an MCP server for agents like Claude. Draft, schedule and publish to 15+ channels from one place.
POST https://api.onlypult.com/v1/posts
Authorization: Bearer op_…
{ "profile_ids": ["1234", "5678"],
"content": "Launch day is here.",
"media_urls": ["https://cdn…/asset.png"],
// is_draft: true - nothing goes live
"is_draft": true }$ claude mcp add onlypult https://mcp.onlypult.com/mcp
"Turn this article into posts for Telegram and LinkedIn, attach the image, save as drafts."
→ account_get → profiles_list → posts_createYour bill doesn't scale with your customers' reach. Pay for a plan, not per connected account.
No separate developer tier. API and MCP work on the free trial — no card required.
The agent gets hands, not the publish button. Pass is_draft: true and nothing goes live until you say so.
Works with your stack
Your clients connect via OAuth — no shared passwords, and no Meta app for you to build.
Two paths. One product.
Same data — accounts, media, posts, schedule. The only choice is who drives publishing.
REST with a Bearer key. Drops into your product, backend, or an n8n / Make / Zapier flow.
The same capability for Claude and other agents. They call Onlypult by the meaning of the task. No code.
Publishing isn't enough. It has to be reliable.
The agent knows the account timezone and plan limits before it schedules a post — not after a failed one.
To 15+ channels as one post group. Draft, schedule, or publish.
Pass is_draft: true and set granular MCP tool permissions. Hands yes; an unsupervised publish button, no.
The agent lists what failed overnight and fixes it in one call.
We ran it. Here's the sequence.
An image generated in an AI generator went to three profiles across two platforms in one call. The file never touched a disk. Nothing was published.
AI-generated
Launch day is here.
3 drafts · media re-hosted on Onlypult CDN · nothing published
Image is an AI-generated asset — not a real photo.
The image goes in by URL. No Claude Code.
When the agent runs in the cloud, the MCP server can't see your disk — so people leave the chat for Claude Code just to move one image. Onlypult takes up to 10 public URLs in media_urls, and generators return exactly that. The asset goes generator → link → Onlypult, never touching your disk.
Turn on agentic publishing gradually, and under control.
Pass is_draft: true and the post is saved, not scheduled or published — nothing goes live until you explicitly ask for it.
Reads and drafts on "Always allow", publish and delete on "Needs approval" — set per tool in Claude, Cursor or ChatGPT.
Claude.ai and ChatGPT connect via OAuth 2.1 — your client signs in once, you never see or store a password.
The whole post lifecycle — not just "create".
15+ channels from one integration
One integration layer for every channel your client publishes to.
Start in five minutes
Two rookie mistakes — skipping tool permissions (the agent asks before every call) and not checking account_get for plan and timezone before scheduling. Both take a minute to fix.
The honest test: does it close the loop — safely?
Not "can the agent publish", but "can it do it safely, to the right place". Accurate as of the publish date.
API and MCP on every plan. No access fee.
No developer-tier surcharge, no per-connected-profile fee, no trial cut short when you create a key. Programmatic access is included everywhere — from the trial to the top plans.
Your bill doesn't grow with each connected profile.
Included in the plan you already have.
7 days free, no card — API and MCP included.
Questions, answered
What's the difference between the API and MCP?
The API is REST you call from your own code or an automation flow. MCP is the same capability exposed to AI agents like Claude, which call it by the meaning of the task — no code. Same data layer underneath; you pick who drives publishing.
Can I post to Instagram & LinkedIn programmatically?
Yes. Both are among the 15+ channels reachable from a single call — as a draft, on a schedule, or published — through the API or an agent via MCP.
Do I need Claude Code to attach an image?
No. Onlypult accepts up to 10 public URLs in media_urls and re-hosts the file itself, so a cloud agent never needs disk access. Generator → link → Onlypult. Want to attach a file straight from disk instead? Run the local MCP package (npx -y @onlypult/mcp@latest) — it adds a media_upload_file tool that uploads local paths directly, in Cursor, Claude Desktop or any stdio-capable client.
Will the agent publish without my confirmation?
Only if you let it. Reads and drafts can be "Always allow" while publish and delete stay on "Needs approval" — set per tool in your MCP client (Claude, Cursor, ChatGPT).
What happens if a post fails?
The agent lists it with posts_list_failed and can re-send it with posts_retry_all_failed in one call. Repair is part of the loop, not a manual chore.
Which plans include API and MCP?
Every plan, including the free trial — with no separate developer tier and no per-profile fee.
How do I connect in Claude and ChatGPT?
Add a custom connector pointing at the MCP server URL, then authorize. It works the same way in both.
What are the rate limits?
Rate limits are published in the API reference. We don't quote a number here that could drift out of date — see the docs for the current per-endpoint limits.
How is the API versioned?
The API is versioned (v1) with backward compatibility within a major version, so your integration keeps working as we ship.
Onlypult has been around — will you shut the API down?
Onlypult has been on the market for years with a public roadmap. The API and MCP are part of the product, not a side experiment.
Connect publishing to your code or to Claude
On every plan · 7-day free trial · no card required