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.
Cue + PilotMyX
Use a terminal MCP client on your Cue agent's computer to read PilotMyX data. This setup requires terminal access; it is not a Cue marketplace connector. 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 Cue 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 Cue can do with PilotMyX
PilotMyX supplies the facts. Cue 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 Cue 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 Cue
“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 Cue. Start with a read-only token; add publishing permissions only when you need them.
Cue is Manus's personal-agent app. Each agent has a computer, but access and tools depend on your workspace.
This guide uses a terminal MCP client on that computer. It requires an agent that can run terminal commands and a way to supply a private environment variable. It does not assume that a Manus connector is inherited by Cue, or that a PMX plugin appears in Cue's marketplace.
If your Cue setup does not expose those capabilities, use Manus's custom MCP connection instead.
Connect your X/Twitter account to PMX and wait for the import. Create a token with account:read and data:read in MCP Access.
Supply it privately as PILOTMYX_MCP_TOKEN on the computer where the Cue agent runs. Keep it out of the chat. Ask the agent to pause for private credential setup if its environment is not ready.
Install MCPorter there using its official installation instructions.
Have the agent create pilotmyx-mcporter.json with this token-free content:
{
"mcpServers": {
"pilotmyx": {
"url": "https://pilotmyx.com/mcp",
"headers": {
"Authorization": "Bearer ${PILOTMYX_MCP_TOKEN}"
}
}
}
}
The terminal MCP guide explains the client configuration and command syntax. Do not replace the variable reference with a real token in an agent-readable file.
Ask Cue to run these commands on its own computer:
mcporter --config ./pilotmyx-mcporter.json list pilotmyx --schema
mcporter --config ./pilotmyx-mcporter.json call pilotmyx.account \
--args '{"action":"get","payload":{}}'
Check that PMX returns the expected X handle and freshness. If Cue reports that it cannot run commands or access a private credential, stop this setup; do not paste the token into chat as a substitute.
Install the PilotMyX MCP skill, then give Cue this task:
Review my PilotMyX posts and replies from the same 30-day period. Show which repeated topics earned profile visits and the examples behind them. Suggest one post to test next. Do not refresh data, save drafts, schedule or publish.
Review the evidence before asking for recurring work. This task should use your imported account records, not a public-search summary.
Revoke the scoped token in MCP Access to end PMX access. Remove the client configuration from the agent computer as well.
If terminal access is unavailable, the Manus guide gives the native custom-connector route without assuming Cue shares its connections.
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. Cue 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 Cue the real results behind your ideas.