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.
Grok Bot + PilotMyX
Give Grok Bot a job grounded in your X results.
Add PilotMyX as a remote MCP server so your Grok Bot can review X/Twitter performance before planning content. 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 Grok Bot
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 Grok Bot a read-only view of your results, and use the evidence to decide what to try next.
Give Grok Bot 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 Grok Bot can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. Grok Bot 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 Grok Bot 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
Grok Bot
Read-only by default · Publishing requires a separate scope
Try asking Grok Bot
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 Grok Bot to PilotMyX
Follow these steps for Grok Bot. The PilotMyX consent screen starts with read-only access; no token needs to be pasted into Grok Bot.
On this page
Before you connect
You need Grok Bot with access to custom remote MCP servers, and a PilotMyX plan or trial with an imported X/Twitter account.
Use a Remote HTTPS MCP connection. PMX is a hosted service, not a command that Grok Bot needs to run locally, and these instructions do not rely on a PMX marketplace listing.
Ask the Bot to add the remote server
In your Bot's chat, request a custom MCP connection:
Add a custom MCP server named PilotMyX using Remote HTTPS:
https://pilotmyx.com/mcp
Use OAuth sign-in. Ask me to complete authentication privately.
Start with read-only access; do not schedule or publish.
Complete the connection card and browser authentication. On PMX's consent screen, check the X handle, retain read-only permissions, and choose Allow connection.
For a Team Bot you own, its info pane exposes Setup → Plugins → Add. Choose a custom MCP server with Remote HTTPS, using the same URL. OAuth lets each person connect their own account; a shared bearer credential would instead expose the same PMX account to everyone who can use it.
Verify that the Bot sees your PMX account
Ask:
Use PilotMyX to check my X handle and sync freshness. Compare posts and replies over the last 30 days, with the real examples behind the result. Do not refresh, draft, schedule or publish.
Confirm that the Bot used the custom MCP tools and returned your account. If it answers from public X search, ask it to repeat the query using PMX explicitly.
Set the boundaries before recurring work
Give the Bot the PilotMyX MCP workflow through Copy prompt in MCP Access. Ask for a single growth review first, then decide whether you want a recurring review.
Keep the credential read-only for analysis. A recurring task can prepare ideas in chat without having permission to publish. Grant write scopes only for a workflow you have explicitly chosen.
Do not place private credentials in shared Bot files or command arguments. Grok Bot's cloud computer and installed connectors can be shared across your Bots; do not assume each Bot is an isolated credential store.
Troubleshooting and revocation
If the Bot cannot offer a custom remote-server connection, check your client version and workspace policy. Grok web and Grok Build have their own MCP settings; installing one does not configure the others.
If sign-in is incomplete, finish the connection's browser flow. For scope errors, check the action against the permissions in MCP Access. Revoke the credential there and remove the custom connection in Grok Bot to disconnect it.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect Grok Bot
Does Grok Bot 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. Grok Bot 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 Grok Bot the real results behind your ideas.