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 web and desktop + PilotMyX
Give Claude the results behind your X posts.
Compare what your X/Twitter audience responds to before you ask Claude to draft another post. 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 web and desktop
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 web and desktop a read-only view of your results, and use the evidence to decide what to try next.
Give Claude web and desktop 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 web and desktop can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. Claude web and desktop 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 web and desktop 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 web and desktop
Read-only by default · Publishing requires a separate scope
Try asking Claude web and desktop
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 web and desktop to PilotMyX
Follow these steps for Claude web and desktop. The PilotMyX consent screen starts with read-only access; no token needs to be pasted into Claude web and desktop.
On this page
Before you connect
Your X account must already be connected to PilotMyX with an active plan. Claude uses a remote MCP connector for this setup, so there is no token to paste into Claude and no local configuration file to edit. Claude Code uses a different setup.
Add the connector in Claude
Open Customize → Connectors in Claude. Choose + → Add custom connector, name it PilotMyX, and enter:
https://pilotmyx.com/mcp
You do not need to supply a client ID or secret in Advanced settings. After adding the connector, select Connect. Claude will send you to PilotMyX to sign in with X and approve read-only access to your account.
On a Team or Enterprise workspace, an owner must add the custom web connector in Organization settings → Connectors first. Each member then connects their own PilotMyX account. Claude Desktop uses the same remote connector through your Claude account; a local desktop extension is a different kind of integration.
Put your X history to work
Enable PilotMyX from Claude's + → Connectors menu in a conversation. Start with one decision you need to make:
Look at my original posts and replies from the last 30 days. Which topics led to more profile visits? Show the posts behind your answer, then suggest one angle to test next. Do not save or publish a draft.
PilotMyX supplies the posts, replies and metrics. Claude does the analysis in your conversation. If the connection is enabled but Claude answers from general knowledge, ask it to check PilotMyX data freshness first. The MCP guide explains the available tools.
Permissions and troubleshooting
The default OAuth connection is read-only. You can revoke it from MCP Access. If Claude reports an authentication error, reconnect the connector and check that your PilotMyX plan and X connection are active. If the connector does not appear at all, check your Claude workspace's custom connector settings.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect Claude web and desktop
Does Claude web and desktop 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 web and desktop 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 web and desktop the real results behind your ideas.