planpost-mcp 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -2,6 +2,27 @@
 
 All notable changes to `planpost-mcp`. Versions follow [semver](https://semver.org).
 
+## 0.4.1 — 2026-11-14
+
+### Changed
+- Agents that sign in with OAuth see 34 tools: the scheduling, delivery,
+  analytics, revenue and approval tools. The video, carousel, brand kit,
+  content source and repurposing tools are left out for them, because those
+  features are parked in the PlanPost app; an API key still gets all 49.
+- `create_post` no longer points agents at the carousel tools; several
+  attached images publish as a carousel where the network supports one.
+- Descriptions in the README, `server.json`, the plugin manifests, GEMINI.md
+  and the skill describe the product as it is now: an agentic scheduler, with
+  approval as a choice the user makes (off by default).
+- `generate_image` is among the tools left out for OAuth sign-ins: it calls a
+  generative image model, which the Claude directory does not allow in a
+  listed server.
+- `.claude-plugin/marketplace.json` has a marketplace description.
+
+### Removed
+- The `send-to-plan-post` skill. It described one account's own groups, not
+  the product. `skills/planpost` is the skill to install.
+
 ## 0.4.0 — 2026-11-09
 
 ### Added

package/README.md

@@ -1,6 +1,6 @@
 # planpost-mcp
 
-MCP (Model Context Protocol) server for [PlanPost](https://planpo.st), the agentic social scheduler with revenue attribution. It lets Claude, ChatGPT, Cursor, Gemini CLI and other AI agents schedule social media posts, create videos and carousels, manage content sources, and read analytics and revenue data by talking to your PlanPost account.
+MCP (Model Context Protocol) server for [PlanPost](https://planpo.st), the agentic social scheduler your AI agent can run. It lets Claude, ChatGPT, Cursor, Gemini CLI and other AI agents draft, schedule and publish posts to Instagram, Facebook, LinkedIn, X, Threads, TikTok and YouTube, see what failed and why, and read analytics and revenue from your PlanPost account.
 
 ## Quick start
 
@@ -9,8 +9,9 @@ MCP (Model Context Protocol) server for [PlanPost](https://planpo.st), the agent
 Add `https://mcp.planpo.st/mcp` to your agent as a remote MCP server (a
 "connector" in Claude and ChatGPT) and leave the authentication fields empty.
 The first time the agent uses it, a browser opens on planpo.st: log in, review
-what the agent may do, and choose whether its posts wait for your approval.
-No key to create or paste.
+what the agent may do, and choose whether its posts wait for your approval
+(they go out at the time the agent sets unless you turn that on). No key to
+create or paste.
 
 ```bash
 claude mcp add --transport http planpost https://mcp.planpo.st/mcp
@@ -20,8 +21,8 @@ claude mcp add --transport http planpost https://mcp.planpo.st/mcp
 { "mcpServers": { "planpost": { "url": "https://mcp.planpo.st/mcp" } } }
 ```
 
-Connected agents are listed under **Settings → API Keys → Connected apps**,
-where you can remove one at any time. They use the same permissions and the
+Connected agents are listed on the **Agent** page under **Connected apps**,
+where you can turn approval on or off for each one, or remove it, at any time. They use the same permissions and the
 same monthly call allowance as API keys.
 
 The repository also ships ready-made bundles: a Claude Code plugin
@@ -39,16 +40,17 @@ OAuth support, for CI, or when you want a key limited to a few permissions.
 
 ### 1. Get an API key
 
-In the PlanPost dashboard go to **Settings → API Keys → Create Key** and select the permissions you need (see the table below). The key (`pk_live_…`) is shown **once** — copy it.
+In the PlanPost dashboard open the **Agent** page and choose **Create key** and select the permissions you need (see the table below). The key (`pk_live_…`) is shown **once** — copy it.
 
-> API/MCP access is included in every paid plan — Creator: 1,000 calls/month, Pro: 10,000 calls/month. Keys are scoped: a key with only `posts:read` cannot publish.
+> API/MCP access is included on every plan: Free 200 calls a month, Creator 1,000, Pro 10,000. Keys are scoped: a key with only `posts:read` cannot publish.
 
 ### 2. Add the server to your agent
 
 Two ways to connect. **Hosted** is the default: point your client at
 `https://mcp.planpo.st/mcp`, nothing to install, your key travels as a header.
 **Local** runs the same server on your machine with `npx`, so the key never
-leaves it. Both expose the same 49 tools.
+leaves it. Both expose the same 49 tools to an API key; an agent that signs in
+with OAuth gets 34 of them (see the note under Tools).
 
 Replace `pk_live_xxx` with your key throughout.
 
@@ -190,9 +192,9 @@ endpoint, and never forwards them upstream.
 
 > "Schedule this post to my Polish Pages group for tomorrow 9:00: …"
 >
-> "Make a quote video from this testimonial and publish it as a reel."
+> "Here is my new blog post. Write one version per network and spread them across next week."
 >
-> "Pull the latest posts from my WordPress blog and draft a LinkedIn carousel from the newest one."
+> "What failed to publish this week, and what do I need to fix?"
 >
 > "How much revenue did my posts drive last 30 days?"
 
@@ -200,12 +202,12 @@ endpoint, and never forwards them upstream.
 
 | Variable | Required | Description |
 |---|---|---|
-| `PLANPOST_API_KEY` | stdio only | API key from Settings → API Keys (`pk_live_…`). Not needed with `--http`, where each request brings its own credentials. |
+| `PLANPOST_API_KEY` | stdio only | API key from the Agent page in PlanPost (`pk_live_…`). Not needed with `--http`, where each request brings its own credentials. |
 | `PLANPOST_API_URL` | — | API base URL (default `https://api.planpo.st`) |
 
 ## Tools
 
-49 tools, grouped below. The permission column is the scope a tool needs, whether it comes from an API key or from OAuth sign-in; a credential without the scope gets a clear error rather than a silent failure. Every tool carries MCP annotations (a title plus read-only, destructive and open-world hints) so clients know which calls to confirm.
+49 tools, grouped below. An agent that signs in with OAuth (the hosted server with no key, which is how Claude, ChatGPT and Cursor connect) is offered 34: the AI image tool and the video, carousel, brand kit, content source and repurposing tools are left out, because those features are parked in the PlanPost app. An API key gets all 49. The permission column is the scope a tool needs, whether it comes from an API key or from OAuth sign-in; a credential without the scope gets a clear error rather than a silent failure. Every tool carries MCP annotations (a title plus read-only, destructive and open-world hints) so clients know which calls to confirm.
 
 ### Posts & publishing
 
@@ -243,6 +245,8 @@ endpoint, and never forwards them upstream.
 
 Connecting a new social account requires OAuth in a browser: `get_connection_link` hands the user the link, and the agent can target the account once it is connected.
 
+X needs a paid plan. On the free plan `get_connection_link` answers with an upgrade message for `twitter`, `list_connections` marks an X account that is already connected as not on the current plan, and a post that targets X is saved as a draft with the `x_requires_paid_plan` error.
+
 ### Approvals
 
 | Tool | Required permission | Description |

package/dist/index.js

@@ -83,17 +83,58 @@ function formatLinks(links) {
 // ─── MCP Server ───
 // Tool registration is a function so HTTP mode can build a fresh server per
 // request (stateless transport); stdio builds one at startup.
-function buildServer() {
+function buildServer(omit = NO_TOOLS) {
     const server = new McpServer(SERVER_INFO);
-    registerTools(server);
+    registerTools(server, omit);
     return server;
 }
+const NO_TOOLS = new Set();
+/**
+ * Tools left out for agents that signed in with OAuth, which is how every
+ * directory-listed client (Claude, ChatGPT, Cursor) connects.
+ *
+ * - generate_image calls a generative image model. The Claude directory's
+ *   compliance step requires the statement "My MCP server does not use AI
+ *   models to generate images, video, or audio", and a tool that is merely
+ *   discouraged would make that statement false.
+ * - Video and carousel templates, brand kits, content sources and repurposing
+ *   belong to features parked in the app since 2026-11-11 (PARKED_NAV in
+ *   apps/web/lib/config/nav.tsx). A signed-in agent is offered what the
+ *   product sells: scheduling, delivery, results and approvals.
+ *
+ * API-key connections, which the user sets up by hand, keep the full set.
+ * To bring a parked feature back, remove its tools here and its nav entry.
+ */
+const OMITTED_FOR_SIGNED_IN_AGENTS = new Set([
+    "generate_image",
+    // Video templates
+    "create_video",
+    "get_video_status",
+    "list_video_templates",
+    // Carousel templates and brand kits
+    "generate_carousel",
+    "render_carousel",
+    "get_carousel_render",
+    "list_carousel_styles",
+    "list_brand_kits",
+    // Content sources and repurposing
+    "add_content_source",
+    "delete_content_source",
+    "fetch_source_content",
+    "list_content_sources",
+    "list_imported_content",
+    "repurpose_content",
+]);
 // ─── Tools ───
-function registerTools(target) {
+function registerTools(target, omit = NO_TOOLS) {
     // Every tool below is registered through this shim so its annotations
     // (title, read-only / destructive hints) come from annotations.ts.
     const server = {
-        tool: ((name, description, schema, handler) => target.tool(name, description, schema, annotationsFor(name), handler)),
+        tool: ((name, description, schema, handler) => {
+            if (omit.has(name))
+                return undefined;
+            return target.tool(name, description, schema, annotationsFor(name), handler);
+        }),
     };
     server.tool("list_posts", "List your scheduled and published social media posts. Filter by status, platform, campaign, label, post type, or free text.", {
         // `needs_approval` is a first-class status, not an internal one: a post
@@ -142,7 +183,7 @@ function registerTools(target) {
         connectionIds: z.array(z.string()).describe("Array of social connection IDs to post to. Use list_connections or list_account_groups to find IDs."),
         platformContent: z.record(z.string(), z.string()).optional().describe("Per-platform content overrides, e.g. { twitter: 'shorter version', linkedin: 'longer version' }"),
         platformSettings: z.record(z.string(), z.any()).optional().describe("Per-platform settings, e.g. { instagram: { isReel: true }, youtube: { title: '...', visibility: 'public' } }. TikTok: a scheduled or published post MUST carry { tiktok: { privacyLevel } } with one of PUBLIC_TO_EVERYONE, MUTUAL_FOLLOW_FRIENDS, FOLLOWER_OF_CREATOR, SELF_ONLY (TikTok makes the user choose who can view each video; without it the API returns 400). Optional tiktok flags: disableComment, disableDuet, disableStitch (default true = off), brandedContent, yourBrand."),
-        postType: z.enum(["post", "reel", "short", "story", "thread"]).optional().describe("Explicit post type (clearer than platformSettings flags, and takes precedence over them). 'reel' needs Instagram/Facebook; 'short' needs YouTube/Instagram/TikTok/Facebook; 'story' needs Instagram/Facebook; 'thread' is X/Twitter-only and requires threadSegments. Defaults to 'post', or is inferred from platformSettings flags (e.g. { instagram: { isReel: true } } → reel). NOTE: a carousel is NOT a postType — attach media with type 'carousel' or use generate_carousel/render_carousel."),
+        postType: z.enum(["post", "reel", "short", "story", "thread"]).optional().describe("Explicit post type (clearer than platformSettings flags, and takes precedence over them). 'reel' needs Instagram/Facebook; 'short' needs YouTube/Instagram/TikTok/Facebook; 'story' needs Instagram (Facebook Stories are not supported); 'thread' is X/Twitter-only and requires threadSegments. Defaults to 'post', or is inferred from platformSettings flags (e.g. { instagram: { isReel: true } } → reel). NOTE: a carousel is NOT a postType — attach several images (or media with type 'carousel') and it publishes as a carousel where the network supports one."),
         threadSegments: z.array(z.string()).optional().describe("Ordered tweet segments for a thread (only used when postType='thread', X/Twitter-only). 2–25 segments, each 1–280 characters."),
         label: z.string().optional().describe("Internal working name shown in the PlanPost dashboard list, e.g. 'Garmin CIRQA - IG Carousel'. Never published to any platform — it just makes a campaign's drafts tellable apart. Highly recommended when creating several posts at once."),
         campaign: z.string().optional().describe("Campaign tag, e.g. 'garmin-cirqa-2026' (slugified automatically). Sets utm.campaign and derives a utm.content token from the format (e.g. 'ig-carousel', 'fb-static'). Group/filter/bulk-delete by this with list_campaigns, list_posts({campaign}) and delete_posts({campaign})."),
@@ -486,9 +527,15 @@ function registerTools(target) {
                 return "  ⚠️ last publish failed, will retry";
             return `  ⛔ cannot publish${h.reason ? ` [${h.reason}]` : ""}${h.lastError ? `: ${String(h.lastError).slice(0, 120)}` : ""}`;
         };
-        const summary = connections.map((c) => `${c.provider} — ${c.metadata?.accountName || c.providerUsername} (ID: ${c.id})${healthTag(c)}`).join("\n");
+        // `planBlocked` means the platform is not on the account's current plan
+        // (X needs a paid plan). The account is connected and healthy, but a post
+        // that targets it fails preflight with `x_requires_paid_plan`, so flag it
+        // here before the agent picks it.
+        const planTag = (c) => c.planBlocked ? `  ⛔ not on the current plan, needs ${c.requiredPlan === "pro" ? "Pro" : "Creator or Pro"}` : "";
+        const summary = connections.map((c) => `${c.provider} — ${c.metadata?.accountName || c.providerUsername} (ID: ${c.id})${planTag(c) || healthTag(c)}`).join("\n");
         const dead = connections.filter((c) => c.health?.status === "dead").length;
-        const headline = `${connections.length} connected accounts${dead ? `, ${dead} cannot publish until fixed` : ""}:`;
+        const planBlocked = connections.filter((c) => c.planBlocked).length;
+        const headline = `${connections.length} connected accounts${dead ? `, ${dead} cannot publish until fixed` : ""}${planBlocked ? `, ${planBlocked} not on the current plan` : ""}:`;
         return { content: [{ type: "text", text: `${headline}\n\n${summary}\n\nFull data:\n${JSON.stringify(connections, null, 2)}` }] };
     });
     server.tool("list_account_groups", "List account groups the user has set up in PlanPost (e.g. 'Polish Pages', 'English Pages'). Each group bundles social connections so you can target multiple accounts in one create_post call. Returns id, name, connectionCount, isDefault, and the underlying connections.", {}, async () => {
@@ -1069,7 +1116,7 @@ async function startHttp(port, host) {
                 }
             }
             const body = await readBody(req);
-            const server = buildServer();
+            const server = buildServer(credential.kind === "grant" ? OMITTED_FOR_SIGNED_IN_AGENTS : NO_TOOLS);
             const transport = new StreamableHTTPServerTransport({
                 sessionIdGenerator: undefined, // stateless
             });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "planpost-mcp",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "//mcpName": "Ownership marker for the official MCP Registry: must equal `name` in server.json, or `mcp-publisher publish` fails validation. Namespace is the GitHub account that owns this repo, verified with `mcp-publisher login github`.",
   "mcpName": "io.github.lukBB/planpost",
   "description": "PlanPost MCP server, the agentic social scheduler with revenue attribution: schedule and publish posts to Instagram, TikTok, LinkedIn, X, Facebook, Threads and YouTube from Claude, Cursor, Codex or any MCP client, render video and carousels, and read revenue per post.",

package/skills/planpost/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: planpost
-description: Draft, schedule and publish social media posts through PlanPost, the agentic social scheduler with revenue attribution, and report what they earned. Use when the user wants to post, schedule, queue, repurpose or bulk-plan content for Instagram, TikTok, LinkedIn, X (Twitter), Facebook, Threads or YouTube, render a carousel or video for a post, check a post's status or a failed publish, or ask which posts drove clicks, signups or revenue. Requires the PlanPost MCP server (https://mcp.planpo.st/mcp).
+description: Draft, schedule and publish social media posts through PlanPost, the agentic social scheduler your AI agent can run, then check what went out and what worked. Use when the user wants to post, schedule, queue or bulk-plan content for Instagram, TikTok, LinkedIn, X (Twitter), Facebook, Threads or YouTube, check a post's status or a failed publish, or ask which posts drove clicks, signups or revenue. Requires the PlanPost MCP server (https://mcp.planpo.st/mcp).
 license: MIT
 metadata:
   homepage: https://planpo.st/mcp
@@ -8,8 +8,9 @@ metadata:
 
 # PlanPost
 
-PlanPost schedules and publishes to seven social networks and attributes
-revenue back to individual posts. This skill is the operating manual for its
+PlanPost schedules and publishes to seven social networks, reports what
+failed and why, and reads back analytics and revenue (revenue per post on the
+Pro plan). This skill is the operating manual for its
 MCP tools. Tool names below are the ones the server exposes; your client may
 prefix them (for example `mcp__planpost__create_post`).
 
@@ -18,7 +19,7 @@ prefix them (for example `mcp__planpost__create_post`).
 If no PlanPost tools are available, the server is not connected. Tell the user
 to add `https://mcp.planpo.st/mcp` as a remote MCP server (connector) in their
 agent and sign in when the browser opens. Details per client:
-https://planpo.st/docs/agents. Do not ask the user to paste an API key into
+https://planpo.st/docs. Do not ask the user to paste an API key into
 the chat.
 
 ## The rules that prevent bad posts
@@ -33,9 +34,10 @@ the chat.
 3. **Say the time back.** Pass `scheduledFor` as ISO 8601 plus the user's
    `timezone`, and repeat the local time in your answer. If they gave no time
    and want one, `suggest_schedule` or `get_best_times` picks it.
-4. **Approval is not a failure.** A post that comes back `needs_approval` is
-   waiting for the account owner in PlanPost. Report that and stop; do not
-   retry or re-create it. `get_approval_status` tells you when it clears.
+4. **Approval is not a failure.** If the user turned on approval for this
+   connection, a post comes back `needs_approval`: it is waiting for them in
+   PlanPost under Posts, In review. Report that and stop; do not retry or
+   re-create it. `get_approval_status` tells you when it clears.
 5. **Read warnings.** Responses carry `warnings[]` (what will be truncated or
    dropped at publish time) and sometimes `preflight.errors[]` (the post was
    saved as a draft because it would fail). Fix what they name, then
@@ -70,20 +72,13 @@ Reuse before uploading: `list_media` shows what is already in the library.
 For a new file, `upload_media` returns a presigned URL; upload to it, then
 pass the returned asset in `media`.
 
-**Carousel**
-
-`generate_carousel` (slide text) → `list_carousel_styles` or
-`list_brand_kits` → `render_carousel` → poll `get_carousel_render` until
-`completed` → `create_post` with the returned `assets` as `media`.
-
-**Video**
-
-`list_video_templates` → `create_video` → poll `get_video_status` →
-`create_post` with `postType: "reel"` or `"short"`.
+Several images attached to one post publish as a carousel where the network
+supports one. For a Reel or Short, attach the video and set `postType: "reel"`
+or `"short"`.
 
 **Turn an article into posts**
 
-`list_content_sources` → `fetch_source_content` → `list_imported_content` →
+Read the article (open the URL the user gives you, or ask them to paste it) →
 write per-network variants (use `get_brand_voice_prompt` when a brand voice
 exists) → `create_post` as drafts.
 
@@ -103,12 +98,10 @@ money, not the ones with the most likes.
 ## Limits to respect
 
 - Calls count against the user's monthly API allowance; prefer one
-  `bulk_create_posts` over many `create_post` calls, and do not poll render
-  status faster than every few seconds.
+  `bulk_create_posts` over many `create_post` calls, and do not poll a status
+  faster than every few seconds.
 - A tool that answers with a missing-permission error means the user did not
   grant that scope. Say which capability is missing; do not look for a
   workaround.
-- Image, video and carousel generation spend the user's AI credits or render
-  quota. Confirm before generating more than a couple.
 - Connecting a new social account needs a human in a browser:
   `get_connection_link` returns the link to send them.

package/skills/send-to-plan-post/SKILL.md

@@ -1,152 +0,0 @@
----
-name: send-to-plan-post
-description: Compose and route social posts through the user's PlanPost app. Resolves named account groups ("Polish Pages", "English Pages", "SaaS", "Personal", etc.) into PlanPost connection IDs and creates draft, scheduled, or immediately-published posts. MANDATORY TRIGGERS - "send to plan post", "/send-to-plan-post", "post to PlanPost", "publish via PlanPost", "save as draft on PlanPost", "post to my <group> pages", "post this to my <group> group", "draft on PlanPost", "schedule on PlanPost", "post to Polish Pages", "post to English Pages". Also trigger when the user pastes social copy and references any known group name. Requires the planpost-mcp server registered with PLANPOST_API_KEY.
----
-
-# send-to-plan-post
-
-## What this skill does
-
-Routes user-provided content to the right set of social accounts in PlanPost, using account groups as the primary targeting concept (with a fallback to individual handle targeting). Supports draft, scheduled, and immediate-publish modes. Handles image/video attachments via PlanPost's presigned S3 upload flow.
-
-## Required MCP tools (`planpost-mcp`)
-
-The user must have the `planpost-mcp` server installed and authenticated with `PLANPOST_API_KEY`. This skill calls:
-
-- `list_account_groups` — resolve a group name into its connections
-- `get_account_group` — fetch one group (by id, name, or default flag)
-- `list_connections` — fallback when targeting individual accounts
-- `upload_media` — presigned-URL upload for attached files
-- `create_post` — draft or scheduled creation
-- `publish_post` — immediate publish of a created post
-- (read-only) `list_posts`, `get_post` — for "show me what I just sent"
-
-The API key needs these permissions: `groups:read`, `connections:read`, `posts:read`, `posts:write`, `media:write`.
-
-If the MCP server is missing or the API key is unset, stop and tell the user how to install/configure it (see `packages/mcp-server/README.md`). Do not fall back to web scraping or computer-use clicking through the dashboard.
-
-## Flow
-
-### Step 1 — Parse the request
-
-From the user's message extract:
-
-- **Content** — the post body. Preserve the user's language exactly (Polish stays Polish, English stays English). Do not "improve" copy unless asked.
-- **Target** — one of: a group name ("Polish Pages"), a list of handles ("@triathlon_info_pl on IG"), or "default".
-- **Mode** — `draft` | `schedule` | `publish-now`. **Default to `draft` when ambiguous.** Only schedule or publish if the user explicitly asks for it.
-- **Schedule time** — if mode is `schedule`, an ISO datetime or natural phrase ("tomorrow 9am"). Resolve to ISO 8601 in the user's timezone before sending.
-- **Media** — any files attached in the chat or URLs the user pasted.
-- **Platform overrides** — per-platform variants (`platformContent`) or settings (`platformSettings`, e.g. `{ instagram: { isReel: true } }`) only if the user gave them explicitly.
-
-### Step 2 — Resolve targets
-
-- **Group by name** → call `list_account_groups`, do a case-insensitive exact-name match first; if no hit, try substring; if multiple match, ask the user to pick from the matches.
-- **Default group** → call `get_account_group` with `{ default: true }`.
-- **Specific handles** → call `list_connections`, filter by `provider` + `providerUsername` (lowercase compare, strip leading `@`).
-- **No target resolved** → stop, list every group the user has, ask which one.
-
-Capture the resolved `connectionIds[]` and the human-readable list (`provider @handle`) for the confirmation step.
-
-### Step 3 — Handle media
-
-For each attached file:
-
-1. Call `upload_media` with `{ filename, contentType, size }` to get a presigned PUT URL.
-2. PUT the file bytes.
-3. Capture the returned `{ id, type, url, key, filename, mimeType, size }` and append to a `media[]` array.
-
-For pasted URLs: fetch the bytes (respect link-safety rules — verify unfamiliar URLs with the user before fetching), then upload via the same flow. If a URL fails to fetch, ask the user to attach the file directly instead.
-
-### Step 4 — Compose and confirm
-
-Before any write that publishes publicly, show a confirmation block:
-
-```
-About to <draft | schedule | publish-now>:
-
-Group:     Polish Pages (4 accounts)
-  - facebook   @triathloninfopl
-  - instagram  @triathlon_info_pl
-  - threads    @triathlon_info_pl
-  - twitter    @triathlon_info_pl
-When:      <Now | 2026-05-19 09:00 Europe/Warsaw | Draft only>
-Content:   <body, truncated to ~200 chars with [...] if longer>
-Media:     <N items, names>
-Mode:      <publish-now | schedule | draft>
-
-Reply "go" to execute, or describe edits.
-```
-
-Rules:
-
-- **Draft**: a confirmation summary is shown but the skill may proceed without an explicit "go" if the user's instruction was already unambiguous. (Drafts are reversible.)
-- **Schedule**: require explicit "go".
-- **Publish-now**: require explicit "go". If 5+ accounts are targeted, require a second `"yes publish to all <N>"` confirmation.
-
-### Step 5 — Execute
-
-- Call `create_post` with `{ content, connectionIds, media, scheduledFor?, platformContent?, platformSettings?, timezone? }`.
-- If mode is `publish-now`: take the returned post id and call `publish_post`.
-- If mode is `schedule`: setting `scheduledFor` on `create_post` is enough; do not call `publish_post`.
-- If mode is `draft`: do not set `scheduledFor` and do not call `publish_post`.
-
-### Step 6 — Report back
-
-Format the result tightly:
-
-```
-Created post <id> as <status>.
-
-Targets:
-  - facebook   @triathloninfopl    queued
-  - instagram  @triathlon_info_pl  queued
-  - threads    @triathlon_info_pl  failed (token expired — re-auth at planpo.st)
-
-Dashboard: https://planpo.st/posts/<id>
-```
-
-Surface per-platform results (`platformResults[]`) from the API response. **Do not swallow partial failures.**
-
-## Examples
-
-### Draft to a group
-
-> "draft a post on PlanPost to my English Pages — 'New SoloOperatorStack post on building Claude skills over PlanPost. Link in bio.'"
-
-→ Resolve "English Pages" via `list_account_groups`. Show confirmation. Call `create_post` with no `scheduledFor`. Report id.
-
-### Publish-now to specific handles
-
-> "post to @triathlon_info_pl on Instagram and Facebook only: 'Trening interwałowy 6x800 — kto dziś biegnie?'"
-
-→ Skip group resolution. Filter `list_connections` to those two. Confirm (4+ rule does not apply). `create_post` → `publish_post`.
-
-### Schedule with image
-
-> User drops `cover.jpg`: "schedule this for tomorrow 9am to Polish Pages: 'Lista startów na weekend ...'"
-
-→ `upload_media` for the image. Resolve Polish Pages via `get_account_group`. Resolve "tomorrow 9am" to ISO in `Europe/Warsaw`. Confirm. `create_post` with `scheduledFor`.
-
-### Discovery
-
-> "what groups do I have on PlanPost?"
-
-→ `list_account_groups`. Format as table: name, account count, default flag, color.
-
-## Safety rules
-
-- Never publish without explicit "go" / "publish" / "yes" from the user.
-- Never invent a group name — if the user names a group that doesn't exist, list what does exist and ask.
-- Never silently drop a failed-per-account result — always surface it in the final report.
-- Preserve the user's language and tone in the post body. Do not paraphrase.
-- For pasted URLs, follow link-safety rules: confirm unfamiliar URLs with the user before fetching their contents.
-
-## Failure modes and how to handle them
-
-- **API key missing** → "Set `PLANPOST_API_KEY` in your MCP config. See `packages/mcp-server/README.md`."
-- **`groups:read` permission missing** → "Your API key doesn't have the `groups:read` permission. Regenerate it at planpo.st/settings/api-keys with that scope checked, or pass connection IDs directly via `list_connections`."
-- **Group not found** → "I don't see a group called 'X'. You have: <list>. Want me to use one of these?"
-- **Ambiguous group name (HTTP 300)** → list the candidates returned by the API, ask the user to pick by id.
-- **Connection inactive (token expired)** → call this out before composing; suggest re-auth in the dashboard.
-- **Upload fails** → retry once, then ask the user to attach again or paste a different URL.
-- **Backend 5xx on `create_post`** → do not retry automatically. Confirm with the user first to avoid duplicate posts.