Claude Desktop: Plan a Week of Posts by Chatting

Every MCP tutorial I have written so far assumed a terminal. This one does not. If you run PostSider and you are the kind of founder who chats with Claude instead of writing code, this is the setup for you: one config block, added through Claude Desktop’s own settings screen, and from then on you plan a week of posts the same way you would ask a person to do it, in a conversation.

Who this is for: founders who chat, not code

Claude Code and Codex tutorials assume you are comfortable in a terminal. Claude Desktop is different. It is the consumer app, the one people use for writing, research, and now, with MCP, real actions in outside tools. If the phrase npx -y @postsider/mcp made your eyes glaze over in an earlier post, this is the version written for you.

The mechanics underneath are identical. Claude Desktop supports MCP servers the same way Claude Code and Codex do. The only thing that changes for a non-developer is where you find the config screen, and the fact that you never touch a command line again after the one-time setup.

The one JSON block to add

Open Claude Desktop, go to Settings, then Developer, and click Edit Config. That opens claude_desktop_config.json directly, a file that on macOS lives at ~/Library/Application Support/Claude/claude_desktop_config.json and on Windows at %APPDATA%\Claude\claude_desktop_config.json [VERIFY: confirm the current Claude Desktop config path and Developer-settings menu wording before publishing, this UI moves between releases]. You do not need to find that path yourself; the Edit Config button does it for you.

Paste this block into the mcpServers object, with your own PostSider API key from Settings, then Developers, then Public API in the PostSider dashboard:

{
  "mcpServers": {
    "postsider": {
      "command": "npx",
      "args": ["-y", "@postsider/mcp"],
      "env": {
        "POSTSIDER_API_KEY": "your-api-key"
      }
    }
  }
}

Save the file, quit Claude Desktop completely, and reopen it. That restart matters: Claude Desktop reads the config file at launch, so a save without a restart leaves the old tool list in place. Once it reopens, PostSider’s tools are available in any conversation, no terminal, no further setup, ever again.

A real planning conversation

Here is the kind of exchange this setup makes possible, written to show the shape of the conversation rather than transcribed from one exact session [VERIFY: potwierdź, że to zapis prawdziwej rozmowy zanim opublikujesz, w przeciwnym razie zostaw jako jawnie oznaczony przykład ilustracyjny].

You: What channels do I have connected in PostSider?

Claude: You have three channels connected: LinkedIn (company page), X, and Instagram.

You: Plan me a week of posts for LinkedIn and X. I want to talk about the new export feature we shipped, one client story, and a general tip. Find open slots and draft each one, do not publish anything.

Claude: I found three open slots this week: Tuesday 9am and Thursday 2pm on LinkedIn, Wednesday 11am on X. Here is what I drafted for each, all saved as drafts in your queue:

1. LinkedIn, Tuesday 9am: announcement post about the export feature, framed around the time it saves a five-person team.
2. X, Wednesday 11am: a shorter version of the same announcement, trimmed for the character limit.
3. LinkedIn, Thursday 2pm: a client story post, using the outline you gave me last week about the agency that cut reporting time in half.

All three are sitting as drafts. Nothing publishes until you review them in the app.

That exchange is the whole workflow. No tool call syntax, no code, just a request in plain language and a result you can go check in the dashboard. Under the hood, Claude called the list-channels tool, the find-next-free-slot tool three times, and the create-post tool three times with a draft status. You never see any of that. You see the plan.

Drafts land in the calendar, not on the internet

The same design choice that runs through every PostSider MCP tutorial applies here without exception: the create-post tool defaults to draft. Claude Desktop can plan, write, and slot a week of content, and every single piece of it waits in your calendar until you open PostSider and look at it yourself.

This matters more for a chat-first workflow than a code-first one, not less. A developer reviewing an agent’s output is used to reading logs and diffs. A founder chatting with Claude is used to trusting the response on screen. Building the review step into the product, not into your own diligence, is the part I would not skip regardless of which client you connect.

Open the calendar after a planning session like the one above, read every draft top to bottom, and either approve, edit, or delete each one. That five minutes is the entire cost of using chat for the drafting instead of your own keyboard.

What chat cannot do well

Text planning is where this setup shines. Media is where it runs out of road. Claude can attach an image to a post if you already have a URL for it, since the upload-media tool accepts a link, but it cannot browse your camera roll, crop a photo to an Instagram-safe aspect ratio, or judge whether a shot looks good next to last week’s grid. That is still a dashboard job, and I would not try to talk my way around it.

The practical split I use: plan the week’s copy, cadence, and slotting in chat, since that is a language problem Claude is genuinely good at. Handle photo selection, cropping, and anything visual in the PostSider app itself, since that is a looking problem, not a talking problem.

Get it running

Copy the JSON block above into claude_desktop_config.json through Claude Desktop’s Developer settings, drop in your PostSider API key, restart the app, and ask it what channels you have connected. If that comes back with a real answer, you are set up to plan a week of posts the same way you would brief an assistant, in a conversation, with every draft waiting for your review before it goes anywhere.

Grab an API key at app.postsider.com/register if you have not connected your accounts yet. If you want the mechanics of how the tool discovery and the drafts-first default actually work under the hood, the Claude Code walkthrough and the general MCP tutorial cover that ground for the developer audience this post deliberately skipped.