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.
OpenClaw + PilotMyX
Let OpenClaw plan from your X results.
Use an OpenClaw MCP connection to inspect your X/Twitter account before delegating a posting workflow. 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 OpenClaw
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 OpenClaw a read-only view of your results, and use the evidence to decide what to try next.
Give OpenClaw 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 OpenClaw can do with PilotMyX
See what is worth repeating — and what is not.
PilotMyX supplies the facts. OpenClaw 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 OpenClaw 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
OpenClaw
Read-only by default · Publishing requires a separate scope
Try asking OpenClaw
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 OpenClaw to PilotMyX
Follow these steps for OpenClaw. Start with a read-only token; add publishing permissions only when you need them.
On this page
Start with a read-only token
Connect your X account to PilotMyX and create a read-only token in MCP Access. OpenClaw can keep running beyond a single conversation, so do not give an always-on agent publishing access by default.
Add the remote MCP server
In OpenClaw's Control UI, open Settings → MCP → Add server. Choose Streamable HTTP and enter:
Name: pilotmyx
URL: https://pilotmyx.com/mcp
Header: Authorization: Bearer YOUR_PILOTMYX_TOKEN
Use OpenClaw's secret mechanism for the real token rather than storing it as a literal in shared configuration. Server definitions live under mcp.servers; the UI writes that entry for you. Set the authorization header in the scoped configuration editor if the initial form only asks for the URL.
Verify tools before delegating work
Run openclaw mcp doctor pilotmyx --probe. A saved server entry only proves that the configuration exists; the probe checks the live connection and lists the tools OpenClaw can call.
Install the PilotMyX MCP skill with Copy prompt from MCP Access. Then ask OpenClaw to check account freshness and compare posts with replies, with the actual samples behind its answer. Keep the first request read-only:
Look at my PilotMyX posts and replies from the same 30-day period. Which topics brought profile visits? Show the evidence and one idea to test next. Do not draft, schedule or publish.
If the probe returns 401, verify the header and token. If it reports no tools, check the MCP tool filter or session policy. Only add draft or scheduling scopes when you know which actions the agent is allowed to take.
Platform documentation
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
Before you connect OpenClaw
Does OpenClaw 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. OpenClaw 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 OpenClaw the real results behind your ideas.