How to Use Buffer to Plan Next Week From Last Month's Posts

The short answer: set a posting schedule on each channel, tag every post with its content pillar, connect Buffer's MCP server to Claude, ask it which of last month's sent posts and pillars earned the most engagement, have it save next week's posts as drafts rather than scheduling them, read and approve each draft into the queue in Buffer, and ask the same question a month later to see whether the plan moved anything.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

Most weekly planning starts from a blank document and last week's habits. A better starting point is last month's results, and Buffer already holds them. Its MCP server lets an assistant read those results and write drafts straight into your account, which turns a Monday hour into a ten-minute review, provided a person still reads every draft. For plans and prices, see the Buffer glossary entry.

What you need:

• A plan with enough history. Free insights cover 30 days, enough for a monthly loop; Essentials keeps unlimited history and costs $6 per channel a month on monthly billing (pricing file, checked on 24 October 2026). Approval workflows need Team.
• Three to five content pillars. Product, customer story, how-to, behind the scenes. They become tags, and tags are what make the results comparable.
• Claude on the web, desktop or Claude Code. Buffer documents all three.

Set the slots on every channel

Each channel has its own timezone and posting schedule, a set of weekly time slots that each hold one post, per Buffer's posting schedule article. Queued posts fill the next open slot, and a channel with no slots has no Add to Queue option at all. Set the channel's timezone to the audience's city, not yours. Only the account owner and users with Full Access can change the schedule.

Tag the pillars

Create one tag per pillar and put every post under one. The free plan allows 3 tags and Essentials 250, per the pricing file. Untagged posts still publish, but they drop out of the comparison that drives next week's plan.

Connect the assistant

In Claude, open Customize, then Connectors, search for Buffer, select it, click Connect and approve access; no API key is needed, per Buffer's Claude guide. In Claude Code, add the server with claude mcp add --transport http buffer https://mcp.buffer.com/mcp, then run /mcp and sign in.

Ask what worked last month

Ask in plain words: list the posts sent in the last 30 days on LinkedIn and Instagram with their metrics, group them by tag, and tell me which pillar earned the most engagement per post and which single posts stood out. Behind that, the assistant calls list_posts with the sent status and metrics switched on, per the MCP server reference. Metrics make the response much larger, and lists come 20 posts to a page, up to 100, so a busy account takes a few calls. Ask for the numbers in a table, so you can check two or three against Buffer's own analytics before believing the summary.

Have it draft, not schedule

Now the planning request: write five posts for next week, two in the strongest pillar, one each in the next two, and one rewrite of the top single post, and save each as a draft on the right channel with its tag. The reference documents create_post with a saveToDraft option for exactly this, and notes that most MCP clients ask you to approve write tools before they run. Approve a call only when it says draft. A channel's minimum requirements still apply: Instagram needs an image or video and a post type, Pinterest a board.

Read and approve every draft

The human check happens in Buffer, not in the chat. Open the channel's Drafts tab, read each post as the audience will, and edit it. The account owner and users with Full Access can then choose Add to Queue, which takes the next open slot, or Schedule Post when the draft already carries a date, per the approval article. On Team, a colleague with Needs Approval access clicks Request Approval instead, and the post waits in the Approvals tab. Turn on Collaboration emails under Settings, Notifications, and approvers hear about drafts created through the API as well.

Ask the same question a month later

Run the first prompt again on the new month and compare engagement per post by pillar against the month before. Keep one pillar exactly as it was, same format and frequency, so you have something unchanged to compare the rest with. These are the networks' own engagement counts, which is fine for choosing between pillars and weak for anything about revenue.

Buffer's homepage sells the loop as ask, plan, post, and the post step is the one in Buffer's interest, because a full queue is a reason to stay subscribed. Yours is whether the posts moved anything, so put the month-later check in the calendar before the first draft goes out.

What Buffer's documentation warns about

• No slots, no queue. Without posting times, every post needs a set date and time.
• The time you see is not always the time it posts. The calendar may show your browser's timezone while the post follows the channel's; check the channel's own queue.
• Editing can move a post. Sending a mode in edit_post reschedules it even when the mode is unchanged; leaving it out keeps the slot.
• Owners cannot request approval on their own drafts. The approval article points to a workaround for agencies.
• The free plan holds 10 scheduled posts per channel. A week of drafts fits; a month may not.

FAQ

Can the assistant publish without asking?

It can: create_post also offers share-now and custom-time modes. That is why the request says draft, and why you approve each write call, per the MCP server reference.

Does this work on the free plan?

Yes. The pricing file lists the Claude and ChatGPT integrations and API access on Free, with 3,000 requests a month, and the 30 days of history is enough for a monthly loop.

Why did a post go out at an odd hour?

Most often the channel's timezone differs from yours. Buffer publishes on the channel's timezone, so set it to where the audience is.