How-To Guide

Use Claude Cowork as your
social media manager for X

Claude Cowork is Anthropic's workspace where Claude works autonomously on ongoing tasks. Connect it to X through OpenTweet's hosted MCP server, hand it a standing brief, and it schedules posts, keeps your calendar full, and matches your voice. No Twitter API.

Connect Cowork to X

7-day free trial. Connect in under two minutes.

Why a social media manager fits Cowork

Claude Cowork is Anthropic's agent workspace, where Claude works autonomously on ongoing tasks rather than one-off chat replies. Managing a social account is a good match for that shape of work: it is recurring, it needs judgment about what to post and when, and it runs on tools rather than pure text. That is precisely the kind of standing job Cowork is designed to hold.

The one thing Claude cannot do on its own is reach X. That is where OpenTweet comes in. Add OpenTweet's Twitter MCP server as a connector and Claude gains a set of X tools: post, schedule, thread, recycle evergreen content, and read analytics. From there you give Claude the standing instruction to run the account, and it works the brief on its own.

Set it up in five steps

1

Get your OpenTweet API key

Sign up for OpenTweet (7-day free trial on every plan), connect your X account once from the dashboard, then go to Settings, API Keys and generate a key. It starts with ot_. This single key is what lets Claude post to X through OpenTweet, with no X developer account and no Twitter API app of your own.

2

Add the hosted MCP server to Claude

Add OpenTweet's hosted MCP server at https://mcp.opentweet.io/mcp to Claude's connectors, passing your key in an Authorization: Bearer header. It speaks streamable-http, so there is nothing to install. Once connected, Claude can see 30 X tools including create_tweet, create_thread, schedule_tweet, batch_schedule, and get_analytics.

3

Give Cowork a standing brief

A social media manager task is recurring and judgment-based, which is exactly what Cowork is built for. Write a standing brief that describes the ongoing job rather than a one-off request. Tell Claude what to review, how far ahead to keep the queue, whose voice to match, and what it must never do, such as auto-reply or mass-engage.

4

Let it keep the queue full

With the brief in place, give Claude the standing instruction to keep your calendar stocked. It uses schedule_tweet and batch_schedule to queue posts days ahead, and the evergreen tools to recycle your best posts on a cooldown. The account stays active on a natural cadence without you writing every post.

5

Review and adjust

Ask Claude to summarize what it posted and what performed using get_analytics, then tune the brief. Start with a draft-for-approval brief if you want a human in the loop, and widen its autonomy as the output earns your trust. The brief is the dial, from suggest to fully scheduled.

The MCP config

Add OpenTweet's hosted MCP server to Claude's connectors. One URL, your key in the header, nothing to install. The same setup works in Claude Desktop.

// add to Claude's MCP connectors

{
  "mcpServers": {
    "opentweet": {
      "type": "streamable-http",
      "url": "https://mcp.opentweet.io/mcp",
      "headers": { "Authorization": "Bearer ot_your_key" }
    }
  }
}

Give Cowork a standing brief

A standing brief tells Claude what its job is on an ongoing basis, not just for one message. Adapt this to your account and paste it in as Claude's instructions.

# example standing brief

You are my social media manager for my X account.

Ongoing brief:
- Review my analytics once a week and note what performed.
- Keep two weeks of posts scheduled at all times.
- Match my voice and keep the tone consistent.
- Post original content only. Never auto-reply or mass-engage.
- Before scheduling anything new, show me the drafts first.

Three instructions to try

"Draft five posts in my voice about this week's launch and schedule them across the next seven days."

"Check my analytics from the last two weeks and tell me which posts to add to the evergreen queue."

"My calendar is thin. Batch-schedule ten posts to keep two weeks stocked, spaced out sensibly."

Posting original content and scheduling it is allowed by X rules. Auto-replies, mass engagement, and impersonation are not. Keep your brief to original posting and scheduling. For the terminal-first version of this setup, see how to post to Twitter from Claude Code.

Frequently asked questions

Can Claude Cowork manage my Twitter?

Yes, once you connect it to X. Claude Cowork is an agent workspace where Claude works on ongoing tasks using the tools you give it. Add OpenTweet's hosted MCP server as a connector and Claude gains posting, scheduling, and analytics tools for your X account. Then give Claude the standing instruction to manage the account inside a brief you set.

Can Claude Cowork post tweets automatically?

It can post through the tools you connect. With the OpenTweet MCP server added, Claude can call create_tweet to post now, schedule_tweet and batch_schedule to queue posts for later, and create_thread for threads. You decide how much runs on its own by the brief you give Claude, from draft-for-approval to fully scheduled.

Does Claude Cowork need the Twitter API?

No. You do not need an X developer account or your own Twitter API app. OpenTweet owns the connection to X. You connect your X account to OpenTweet once, add the hosted MCP server to Claude with your OpenTweet key, and Claude posts through OpenTweet.

How do I keep it posting in my voice?

Turn on OpenTweet's voice profile, which learns from your existing posts and shapes new ones to match. Then include a line in your brief such as match my voice and keep the tone consistent. Give Claude the standing instruction to draft in your style and review before it schedules.

Is it safe to let an agent run my account?

Posting original content and scheduling it is allowed by X rules. Auto-replies, mass engagement, and impersonation are not. Keep your brief to original posting and scheduling, and instruct Claude never to auto-reply or mass-engage. You can also start with a draft-for-approval brief and expand its autonomy once you trust the output.

Everything you can build on X with OpenTweet

Connect Claude, an MCP client, or your code to X. Start anywhere in the cluster.

OpenTweet vs the X API

Post, schedule, and automate X without a developer account or the $200/mo minimum.

Post to X without an API

The clean, account-safe way to post to X from your code or an AI agent.

Twitter MCP Server

Give Claude, Cursor, and OpenClaw the ability to post to X. 30 tools included.

XMCP vs OpenTweet

X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.

MCP for AI agents

Connect your AI client to X in under two minutes, no X developer account.

Developer API and keys

REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.

OpenTweet for AI agents

The posting layer for autonomous agents and automations that live on X.

Build an AI Twitter persona

Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.

Hand X to Cowork. Keep the strategy.

Connect your account, add the MCP server, and give Claude the brief. It schedules, recycles, and reports for a flat fee.

Start your 7-day free trial