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.
Codex + PilotMyX
Give Codex your real X/Twitter post and reply data before asking it what to write next. Connect over MCP and ask questions grounded in the posts and replies you actually published.
Which posts earned the most attention last month, and what should I test next?
From account to action
Connect once, give Codex a read-only view of your results, and use the evidence to decide what to try next.
Connect your account through X. PilotMyX imports the posts and replies included in your plan and refreshes recent data daily.
Create a scoped MCP token and install the PilotMyX skill. Ask what performed, over which period, and which real posts support the answer.
Use those findings to draft a new angle. Add separate write permissions only if you want the agent to save or schedule it.
What Codex can do with PilotMyX
PilotMyX supplies the facts. Codex helps you interpret them and plan the next test. It does not need publishing access to analyze your account.
Inspect reach and engagement for individual posts, with the content behind each result.
See whether original posts or replies are doing the work, using a shared time window.
Compare periods and account trends before deciding whether an idea is worth repeating.
Ask for a new angle based on examples from your own account, not generic posting advice.
Grant separate write scopes when you want the agent to prepare or schedule an approved post.
Start read-only, scope each token, and revoke access from PilotMyX when you need to.
The connection
It is the bridge between Codex 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 toolsRead-only by default · Publishing requires a separate scope
Try asking Codex
“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
Follow these steps for Codex. Start with a read-only token; add publishing permissions only when you need them.
Connect your X account to PilotMyX and start a plan. In MCP Access, create a read-only token for Codex. Keep it in your local secret store or environment as PILOTMYX_MCP_TOKEN; PilotMyX shows the token only once.
This connection gives Codex your authorized X/Twitter posts, replies and metrics. It does not give Codex permission to publish unless you create a token with write scopes.
Open your user-level ~/.codex/config.toml and add this server. Merge it with your existing configuration; do not replace other MCP servers.
[mcp_servers.pilotmyx]
url = "https://pilotmyx.com/mcp"
bearer_token_env_var = "PILOTMYX_MCP_TOKEN"
bearer_token_env_var names the variable that holds the token. Do not paste the token itself into config.toml or commit it to a repository. Restart Codex after setting the environment variable so the new process can read it.
The MCP connection supplies tools; the PilotMyX MCP skill teaches Codex how to use them together. In MCP Access, use Copy prompt and give it to Codex. The prompt installs the current skills bundle and configures the server for your client. You can skip the optional voice skill if you only want analytics.
If you configured the server manually, still install the MCP skill before asking for account analysis. It explains freshness checks, representative samples and the difference between original posts and replies you wrote.
Run codex mcp list or inspect the available MCP tools in Codex. Then try a request that cannot be answered from general knowledge:
Use PilotMyX to check when my X data last refreshed. Compare my original posts and my replies over the last 30 days. Show the sample size and three real examples behind your conclusion. Suggest one post to test next, but do not create or publish it.
If PilotMyX is missing from the tool list, check that Codex can read PILOTMYX_MCP_TOKEN in the environment where it runs. A desktop app may not inherit variables set in a separate terminal. If the server returns 401, verify the token in MCP Access and create a new one if it may have been exposed.
Keep the read-only token for analysis. Create a separate scoped token for drafts or scheduling when you are ready. Ask Codex to show the exact text, account, date, time and timezone before it takes a write action. You can review the result in the PilotMyX calendar.
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
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.
No. PilotMyX provides the account data and publishing tools. Codex does the writing and analysis in your own agent session.
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.
Connect your X account, then give Codex the real results behind your ideas.