Skip to main content

Cue + PilotMyX

Give your Cue agent the context behind your X posts.

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.

  • 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
PilotMyX dashboard showing post and reply performance, follower growth and scheduled posts

PilotMyX dashboard showing post and reply performance, follower growth and scheduled posts

Swipe to explore

PilotMyX dashboard showing post and reply performance, follower growth and scheduled posts
PilotMyX dashboard showing post and reply performance, follower growth and scheduled posts
Ask Cue

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 Cue a read-only view of your results, and use the evidence to decide what to try next.

01 / CONNECT

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.

02 / ANALYZE

Give Cue 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.

03 / TEST

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 Cue can do with PilotMyX

See what is worth repeating — and what is not.

PilotMyX supplies the facts. Cue 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 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 tools
Your X account
PilotMyX MCP
Cue

Read-only by default · Publishing requires a separate scope

Try asking Cue

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 Cue to PilotMyX

Follow these steps for Cue. Start with a read-only token; add publishing permissions only when you need them.

On this page

Use Cue's computer, not a marketplace plugin

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.

Prepare the read-only connection

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.

Give Cue an explicit configuration

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.

Check account access before assigning a job

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.

Assign a bounded growth review

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.

Disconnect or switch clients

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.

Platform documentation

Client settings change. Check the platform's current requirements before connecting.

Read the platform documentation ↗

FAQ

Before you connect Cue

Does Cue 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. Cue 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 Cue the real results behind your ideas.

Start 7-day free trial
PilotMyX

Your account. Your data.

Here’s what PilotMyX needs, and what it doesn’t.

Only what makes the product work

Your posts, replies and stats, plus your profile to identify your account.

Not for sale. Not for ads.

We don’t sell your personal data. Your connected X data is used to run PilotMyX, not for advertising.

Your connection is protected

Access tokens are encrypted. We never see your password or read your DMs. You can revoke access anytime in X.

X asks for publishing access so you can schedule posts. We only publish when you, or an agent you authorize, ask us to.

Any question? You can reach me directly here: