Skip to main content

Manus + PilotMyX

Turn your X results into a plan with Manus.

Add PilotMyX as a custom MCP server in Manus and ask it to compare what actually worked on your X/Twitter account. 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 Manus

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

See what is worth repeating — and what is not.

PilotMyX supplies the facts. Manus 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 Manus 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
Manus

Read-only by default · Publishing requires a separate scope

Try asking Manus

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

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

On this page

Before you connect

You need a PMX plan or trial with an imported X/Twitter account, and access to Manus's custom MCP servers.

This setup uses a scoped PMX token. Create one in MCP Access with account:read and data:read. Use a separate token for Manus so you can revoke that connection without affecting your other agents.

Add a custom MCP server

  1. Open Settings → Integrations → Custom MCP Servers in Manus.
  2. Choose Add Server.
  3. Name the server PilotMyX and enter the HTTPS endpoint below.
  4. Choose bearer-token authentication and enter your PMX token in the credential field.
  5. Run the connection test and confirm that Manus retrieves the tool list.
Server name: PilotMyX
Server URL: https://pilotmyx.com/mcp
Authentication: Bearer token
Authorization header: Bearer YOUR_PILOTMYX_TOKEN

If the form asks for a token value, enter only the token. If it asks for a complete Authorization header, use Bearer followed by a space and the token. Put the credential in the private authentication form, not in a task prompt or the URL.

The endpoint is already hosted by PMX. You do not need to build or deploy a server for Manus.

Check a real account query

Once the connection is available, start a Manus task and explicitly ask it to use PilotMyX:

Check which X account PilotMyX returns and how fresh its data is. Compare posts and replies over the last 30 days. Show which topics earned profile visits, with the examples behind the conclusion. Do not make changes.

Check the account, period and tool calls. The setup test retrieves tools; this task also tests the token's read scopes.

Give Manus the PMX workflow

Use Copy prompt in MCP Access to install the PilotMyX MCP skill. It explains how to page through data, separate posts from replies, and chain the compact tools without inventing action names.

Ask Manus to draft a post from one supported finding. Keep proposed text in the task response until you review it. PMX draft, schedule and publish permissions are separate from analytics access.

Troubleshooting and removal

If the connection test returns 401, check the token and bearer authentication. If an account query is denied, check account:read; post and analytics queries require data:read.

If results are empty, check the import and the requested dates in PMX. Do not authorize refresh or publishing just to resolve an empty comparison.

Remove the custom server in Manus and revoke its token in MCP Access to disconnect it.

Platform documentation

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

Read the platform documentation ↗

FAQ

Before you connect Manus

Does Manus 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. Manus 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 Manus 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: