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.
Cursor + PilotMyX
Bring your X results into Cursor.
Connect Cursor to the performance behind your X/Twitter ideas, not just a blank editor. 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 Cursor
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 Cursor a read-only view of your results, and use the evidence to decide what to try next.
Give Cursor 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 Cursor can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. Cursor 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 Cursor 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
Cursor
Read-only by default · Publishing requires a separate scope
Try asking Cursor
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 Cursor to PilotMyX
Follow these steps for Cursor. Start with a read-only token; add publishing permissions only when you need them.
On this page
What this connection does
Cursor can use PilotMyX as an MCP source while you work in the editor. That lets your agent inspect your own X/Twitter posts, replies and results before it suggests what to publish next. A read-only token cannot schedule or publish.
Add PilotMyX in Cursor
First connect your X account and create a read-only token in MCP Access. Put the token in PILOTMYX_MCP_TOKEN in the environment where Cursor runs. Open your personal ~/.cursor/mcp.json and add this server under mcpServers, preserving any entries you already have:
{
"mcpServers": {
"pilotmyx": {
"url": "https://pilotmyx.com/mcp",
"headers": {
"Authorization": "Bearer ${env:PILOTMYX_MCP_TOKEN}"
}
}
}
}
Cursor expands ${env:PILOTMYX_MCP_TOKEN} in the header. Keep the real token out of ~/.cursor/mcp.json and never put it in a project-level .cursor/mcp.json shared with teammates. Restart Cursor if it was already running before you set the variable.
Test it before asking for a post
Refresh Cursor's MCP tools and confirm that pilotmyx appears. Ask the agent to check data freshness, then to compare original posts and replies over the same window. It should cite examples from your account, not invent numbers.
Using PilotMyX, find the posts and replies that brought profile visits in the last 30 days. Separate the two content types, show a typical result beside a strong one, and suggest one new angle. Do not create or schedule anything.
Install the PilotMyX MCP skill through the Copy prompt action in MCP Access so Cursor learns the account-analysis workflow. If the server reports 401, check the header and rotate the token if it may have leaked. If no tools appear, verify that the server URL ends in /mcp and that Cursor is using Streamable HTTP, not a local command.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect Cursor
Does Cursor 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. Cursor 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 Cursor the real results behind your ideas.