Bring your X history in
Connect your account through X. PilotMyX imports the posts and replies included in your plan and refreshes recent data daily.
Claude Cowork + PilotMyX
Bring your X results into Claude Cowork.
Let Cowork inspect your posts and replies before it helps plan your next X/Twitter test. Connect over MCP and ask questions grounded in the posts and replies you actually published.
- Compare your posts and replies on the same date range
- Ask for real examples behind every recommendation
- Keep publishing access separate from read-only analysis
PilotMyX · Dashboard
Your X account, in context
Ask Claude Cowork
Which posts earned the most attention last month, and what should I test next?
From account to action
Your next post starts with what already worked.
Connect once, give Claude Cowork a read-only view of your results, and use the evidence to decide what to try next.
Give Claude Cowork the context
Approve read-only access on the PilotMyX sign-in screen. Ask what performed, over which period, and which real posts support the answer.
Turn a finding into a new test
Use those findings to draft a new angle. Saving or scheduling through PilotMyX needs a separate, explicitly approved write permission.
What Claude Cowork can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. Claude Cowork helps you interpret them and plan the next test. It does not need publishing access to analyze your account.
Find your strongest posts
Inspect reach and engagement for individual posts, with the content behind each result.
Compare posts and replies
See whether original posts or replies are doing the work, using a shared time window.
Check when results changed
Compare periods and account trends before deciding whether an idea is worth repeating.
Plan a specific next test
Ask for a new angle based on examples from your own account, not generic posting advice.
Draft and schedule, if you choose
Ask for a draft in your conversation. Saving or scheduling it through PilotMyX requires a separate write permission.
Keep control of access
Review the requested permissions at sign-in and revoke the connection from PilotMyX when you need to.
The connection
What is the PilotMyX MCP?
It is the bridge between Claude Cowork and your connected X account. Your agent requests cached posts, replies and analytics from PilotMyX, then works with that evidence in your conversation.
PilotMyX does not generate your strategy on the server. Your agent does the reasoning; you decide whether a draft gets published.
Explore the MCP tools
Your X account
PilotMyX MCP
Claude Cowork
Read-only by default · Publishing requires a separate scope
Try asking Claude Cowork
Questions your own data can answer.
“Compare my original posts and replies from the last 30 days. Which had more reach? Show the sample size and three real examples.”
“Find the posts that beat my usual engagement. What do they have in common? Suggest one angle to test next, but don’t publish it.”
Setup guide
Connect Claude Cowork to PilotMyX
Follow these steps for Claude Cowork. The PilotMyX consent screen starts with read-only access; no token needs to be pasted into Claude Cowork.
On this page
Connect once in Claude
Cowork uses the remote connectors attached to your Claude account. Add PilotMyX from Customize → Connectors → + → Add custom connector in Claude, using:
https://pilotmyx.com/mcp
Select Connect, sign in to PilotMyX with your connected X account, and approve the permissions. You do not need a local MCP server or a token in a Cowork file. If your Claude workspace is on Team or Enterprise, its owner must add the custom web connector first.
Use it in a Cowork task
Open Cowork and enable PilotMyX in the task's connector or tool menu. Give Cowork a concrete job with a clear boundary:
Review my original X posts and replies from the last 30 days. Find the posts that drove profile visits, compare them with posts that got likes but few visits, and give me three ideas to test next week. Show the source posts. Do not schedule or publish anything.
This keeps the work tied to your own X history. Cowork can organize the findings and propose a plan, while PilotMyX remains the source of the account data. The PilotMyX MCP guide lists the data and publishing tools.
What Cowork can access
The default connection is read-only. The PilotMyX consent screen shows the account and permissions before you approve it. If you later revoke the connection from MCP Access, Cowork must reconnect before it can call PilotMyX again.
If Cowork cannot see PilotMyX, check that the remote connector is connected and enabled for the task. A Claude Desktop local extension is not the same connection; Cowork needs the remote connector attached to your Claude account. For the Claude chat setup, see the Claude guide.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect Claude Cowork
Does Claude Cowork need permission to publish?
No. The default connection is read-only. Publishing needs a separate permission grant; the setup below does not request one.
Does PilotMyX write posts with AI?
No. PilotMyX provides the account data and publishing tools. Claude Cowork does the writing and analysis in your own agent session.
What happens if my data is not up to date?
Ask the agent to check the last synchronization time before analyzing a period. PilotMyX refreshes subscribed accounts daily; the MCP skill explains how to check freshness and request a refresh when needed.
Find the next thing worth posting.
Connect your X account, then give Claude Cowork the real results behind your ideas.