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 Code + PilotMyX
Compare your X posts with Claude Code.
Let Claude Code compare your X/Twitter posts and replies without pasting analytics into the chat. 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 Code
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 Code a read-only view of your results, and use the evidence to decide what to try next.
Give Claude Code the context
Create a scoped MCP token and install the PilotMyX skill. 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. Add separate write permissions only if you want the agent to save or schedule it.
What Claude Code can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. Claude Code 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
Grant separate write scopes when you want the agent to prepare or schedule an approved post.
Keep control of access
Start read-only, scope each token, and revoke access from PilotMyX when you need to.
The connection
What is the PilotMyX MCP?
It is the bridge between Claude Code 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 Code
Read-only by default · Publishing requires a separate scope
Try asking Claude Code
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 Code to PilotMyX
Follow these steps for Claude Code. Start with a read-only token; add publishing permissions only when you need them.
On this page
Before you connect
Connect your X account to PilotMyX, then create a read-only token in MCP Access. Keep it in a private environment variable named PILOTMYX_MCP_TOKEN. Claude Code needs that variable in its own process, not just in another terminal window.
Claude Code is different from the Claude web app. This guide uses Claude Code's local MCP configuration and does not require PilotMyX OAuth.
Add a user-level MCP server
Add the following entry under mcpServers in your user-level ~/.claude.json. If that object already exists, add only the pilotmyx entry; do not overwrite your other servers.
{
"mcpServers": {
"pilotmyx": {
"type": "http",
"url": "https://pilotmyx.com/mcp",
"headers": {
"Authorization": "Bearer ${PILOTMYX_MCP_TOKEN}"
}
}
}
}
Claude Code expands ${PILOTMYX_MCP_TOKEN} when it loads the connection. This keeps the token out of the file. Do not put a real token in a project-level .mcp.json or a shell command that may be saved to history.
Verify the connection
Run claude mcp list, then open /mcp in Claude Code. Confirm that pilotmyx is connected and that its tools appear. The PilotMyX MCP skill gives Claude the workflow for checking freshness, comparing posts and replies, and keeping write actions under your control. You can install it using Copy prompt in MCP Access.
Try this first:
Check my PilotMyX data freshness, then compare the reach and profile visits of my original posts and replies over the same period. Show the examples behind the result. Do not create a draft or publish anything.
If /mcp shows a missing variable or 401, check the environment inherited by Claude Code and the token you issued in MCP Access. Revoke an exposed token rather than reusing it. Add draft or scheduling scope only when you want Claude Code to change something in PilotMyX.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect Claude Code
Does Claude Code need permission to publish?
No. Start with a read-only token to analyze posts and replies. Drafting, scheduling and publishing require separate write scopes that you choose in MCP Access.
Does PilotMyX write posts with AI?
No. PilotMyX provides the account data and publishing tools. Claude Code 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 Code the real results behind your ideas.