Last Updated:
No. A properly built MCP connector for social publishing, Planoly's included, does not post, delete, or connect an account without you confirming it. That's the direct answer. What follows is where the approval gate actually sits, what a staged write looks like in practice, and what you should expect to see before anything goes live. If you're weighing this for the first time, Planoly's MCP hub covers the full connector spec alongside this.
It sits between the tool call and the write. When Claude calls a tool like "create post" or "schedule post" through Planoly's connector, that call creates a draft or a scheduled item in Planoly, not a live post. The item sits in your queue exactly like something you scheduled by hand, visible and editable before it fires.
Why it matters: the gate isn't a warning dialogue the model can talk its way past. It's a state the post has to pass through, calendar draft to scheduled to published, and only a human action moves it to the last step.
Concretely, three things happen in order:
Why it matters: this is the same distinction that trips people up between chat mode and an agent with tool access generally. The chat window can describe a post; only a confirmed action in the connected app publishes one.
It will not connect or disconnect a social account, publish a post without a prior draft or schedule state existing first, or delete content. Those actions require you, directly, in Planoly or through an explicit confirmation step Claude surfaces before calling the tool. If a customer's account has ever silently published something wrong, the cause on record has been a setup mismatch, like a caption confirmation step someone clicked through too fast, not an agent acting without a gate at all.
Ask Claude to list the tools available on Planoly's MCP server. A tool list that separates read actions (checking analytics, listing scheduled posts) from write actions (creating, scheduling, publishing) is the artifact worth checking, on Planoly or on any connector you're evaluating. If a server's tool list doesn't make that distinction clearly, that's the real due-diligence flag, not the vendor's own claim either way.
Ready to see the tool list for yourself? Planoly's connector walkthrough walks through exactly what's exposed, or find Planoly directly in the Claude Connector Directory if you're already set up.
Can Claude publish a post the moment I ask it to, with no review step?
No. The post is created as a draft or scheduled item first. Publishing requires your confirmation in Planoly.
What happens if I don't review a scheduled post before it's due?
It publishes at the scheduled time, the same as anything you scheduled manually. The safeguard is reviewing before you schedule, not a second gate at fire time.
Can an MCP connector connect a new social account on its own?
No. Connecting or disconnecting an account is always a direct action you take, never something a tool call can do for you.
Does this approval model slow down bulk scheduling?
Not meaningfully. You can review a week or a month of staged posts in one pass through the calendar rather than approving each one individually as it's created.
Is this the same across every scheduler with an MCP server?
No. Review-first is common but not universal in how it's implemented, and gating varies by vendor. Check a specific connector's tool list rather than assuming.
