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.
Any MCP client + PilotMyX
Bring your X results into any MCP client.
Connect a compatible MCP client to PilotMyX's remote Streamable HTTP endpoint. 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 Any MCP client
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 Any MCP client a read-only view of your results, and use the evidence to decide what to try next.
Give Any MCP client 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 Any MCP client can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. Any MCP client 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 Any MCP client 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
Any MCP client
Read-only by default · Publishing requires a separate scope
Try asking Any MCP client
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 Any MCP client to PilotMyX
Follow these steps for Any MCP client. Start with a read-only token; add publishing permissions only when you need them.
On this page
Check the client first
PilotMyX exposes a remote Streamable HTTP MCP server. Your client must support that transport and send an Authorization bearer header. A model name or a shell alone is not enough; the application running the model needs an MCP connection screen or configuration file.
Create a scoped token
Connect your X account, start a PilotMyX plan, then create a read-only token in MCP Access. Give each client its own token so you can revoke one connection without changing the others. PilotMyX shows a token only once.
Add the server
Use these values in your client's remote MCP settings:
Transport: Streamable HTTP
URL: https://pilotmyx.com/mcp
Authorization: Bearer YOUR_PILOTMYX_TOKEN
Store the real token using the client's secret mechanism or a private environment variable. Do not paste it into a tracked project file, a screenshot or a public prompt. Some clients accept a custom header; others only support OAuth. PilotMyX's current endpoint uses a bearer token, so an OAuth-only client will not connect through these instructions.
Confirm the tools work
List the available MCP tools, then ask the client to check when your PilotMyX data last refreshed. That proves it reached your account rather than answering from memory. Next, ask it to compare original posts and replies over the same period and show representative examples.
The PilotMyX MCP skill teaches this workflow. Install it with Copy prompt from MCP Access if your client supports skills. If the server returns 401, check the token and header. If it connects but cannot see data, check token scopes and whether your X account import has completed. Grant write access only when you want the client to change drafts or scheduled posts.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect Any MCP client
Does Any MCP client 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. Any MCP client 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 Any MCP client the real results behind your ideas.