How to Schedule Social Media Posts With Claude

Claude can schedule social media posts through a connected scheduler that exposes publishing tools; it cannot do so merely by writing a caption in chat. With Distinctful, connect through OAuth, select a real connected account, review the saved draft and time zone, then explicitly authorize scheduling. Source: Distinctful's Claude setup.

This guide works through a fictional consultant's LinkedIn post for October 27, 2026. The text and business situation are illustrative, not a customer result or a hands-on publishing test. We publish Distinctful, so this is an owned-product tutorial. If you are choosing a provider first, see the social media MCP comparison.

What do you need before connecting Claude?

You need a Distinctful plan with MCP access, a supported social account connected to that workspace, and access to custom connectors in your Claude environment. Distinctful includes MCP on Grow and higher; check current plans and the connector guide. Your Claude subscription and workspace administration are separate from your scheduler subscription.

Start with one destination. For this example, use the consultant's LinkedIn member profile. Distinctful's LinkedIn integration supports member profiles, not company Pages. A tool listing the word “LinkedIn” is insufficient evidence that it supports the account you intend to use.

Have the actual source material ready: a service description, a lesson you can substantiate, and an approved destination URL if the post needs one. Do not ask Claude to fill missing evidence with a plausible client story. A simple text post makes the first workflow easier to inspect than a media-heavy campaign.

How do you connect Distinctful to Claude with OAuth?

Follow the current Claude setup page:

1. In Claude on web or desktop, open Customize, then Connectors, and choose Add custom connector.
2. Enter https://app.distinctful.com/api/mcp as the server address.
3. Sign in to Distinctful and review the access request on its authorization screen.
4. Approve the intended access, then enable the connector in the Claude conversation.

This is an OAuth sign-in. You do not need to create an API key or paste a social-network password into the conversation. If your Claude interface does not expose the custom-connector option, check your workspace's connector access before trying alternative endpoints or unofficial setup instructions.

Connecting Claude to Distinctful does not connect a missing social account. Complete that connection in Distinctful first, then ask Claude to read the accounts it can use. You can revoke an agent in Distinctful's Integrations settings; the MCP documentation explains the connection and access model.

How do you choose the account and establish a useful brief?

Begin with a read-only request:

Read my content strategy, the next seven days of my calendar, and my connected accounts. Show the exact LinkedIn account name and whether it is available for publishing. Do not create, plan, schedule, or publish anything yet. My time zone is America/New_York.

The relevant tools are get_content_strategy, get_calendar, and get_connected_accounts. The account tool returns the identifiers used for publication and indicates availability; the calendar helps avoid placing a new post on top of an existing commitment. Source: MCP tool reference.

If two accounts could match, select one explicitly. “My LinkedIn” is not a sufficient instruction when a workspace contains several destinations. If the connection is unavailable, repair it in the application before scheduling. Repeating the scheduling request will not resolve the underlying connection.

Next provide the writing brief. For our fictional consultant:

Draft a LinkedIn text post for independent consultants about agreeing on one decision before an onboarding meeting. Use the following idea as an illustrative example, not a client case study: asking the buyer which decision they need to make can reveal which preparation is useful. Avoid invented numbers and testimonials. Show me the complete text here before saving it.

The distinction matters: text in chat is a proposal. It becomes a saved workspace draft only when a write tool succeeds.

What is the difference between a draft, a plan, and a schedule?

Distinctful exposes separate actions for these states:

Action	What it does	Does it start publication?
create_draft	Saves one social draft or thread	No
plan_drafts	Creates two to seven dated drafts	No
plan_post	Gives an existing draft a planned date and platforms	No
schedule_post	Schedules a saved draft on named connected accounts	Yes, for a future time
publish_now	Submits a saved draft for immediate publication	Yes

These are the current documented tools. A planned calendar date is an editorial intention. A successful scheduling action is a publishing instruction. Neither is evidence that a future post is already live.

After reviewing the text, ask Claude to save exactly that version with create_draft and return the draft link and identifier. If you want to review later, ask it to use plan_post and stop there. You can open that draft in Distinctful and schedule it yourself after checking the destination preview.

The weekly_plan prompt can help assemble a week from strategy, offers, existing calendar entries, ideas, and available performance. It is a workflow recipe, not a recurring job or a guarantee that every action requires a separate confirmation. Start with one post until the state changes are clear. Source: documented MCP prompts.

What should an approval-ready preview contain?

Ask for a compact execution summary before giving scheduling approval:

• The complete saved text, including line breaks and the final link.
• The exact destination account name, platform, and account identifier.
• The draft identifier and a link you can open.
• The intended date, local time, named time zone, and equivalent timestamp with an offset.
• A statement that the next action is scheduling, rather than saving a plan or publishing now.

For the illustrative date, Tuesday October 27, 2026 at 9:00 a.m. in America/New_York is 2026-10-27T09:00:00-04:00. Ask Claude to resolve the offset for your actual date instead of reusing that example across daylight-saving changes. Avoid “tomorrow morning” when the intended account and audience span time zones.

Also open the saved draft. Scheduling uses saved content, so a revised paragraph in chat is not enough unless the saved version matches it. If the versions differ, resolve the mismatch before approving any publication action. For threads or media posts, inspect every part and destination-specific preview.

A suitable authorization is: “Schedule this exact saved draft to the named LinkedIn account for October 27 at 9:00 a.m. America/New_York. Do not publish it now or send it to any other account.” Substitute your real draft and account; this example does not authorize a test post.

Does Claude require another confirmation before scheduling?

Do not rely on an assumed final confirmation screen. Distinctful's MCP write tools act directly when an authorized call reaches them. Claude's tool permissions may ask for approval, and your conversational instructions can require a preview, but those are distinct from a server-enforced review stage. The service can schedule and publish through MCP. Source: Distinctful scheduling FAQ.

If you want a review boundary that leaves publication in your hands, ask for a planned draft and schedule from the application yourself. If you want Claude to complete scheduling, approve the exact saved content, account, and time. Avoid broad instructions such as “handle all my social posts” when you only intend one draft.

The scheduling tool requires an operation key to make retries safe. If a response is lost, the assistant should reuse the same key for the same operation, inspect the result, and avoid creating a fresh duplicate draft just to try again. That is a recovery mechanism, not permission to publish additional content. Source: tool reference.

How do you verify the post was scheduled and later published?

After scheduling, ask Claude to read the saved post or calendar and report the returned state, account, and scheduled time. Open the schedule in Distinctful and check the same details. A message saying “all set” without a saved result is not enough.

At the intended time, check the publishing result and actual public post. Save the public URL and compare its text and destination with the approved version. A scheduled record confirms a future instruction; the public post confirms the visible outcome.

If the operation fails or its outcome is unclear, inspect the existing record before retrying. If the time must change, schedule_post can reschedule an already scheduled draft. Immediate publication is a separate action, so do not ask for publish_now as a generic fix for a delayed schedule. Source: MCP scheduling tools.

Once the single-post workflow is dependable, extend it to a weekly content plan. Keep the same sequence: grounded brief, complete draft, named account, explicit time zone, deliberate approval, and a result you can verify.