Skip to main content

Muse Code + PilotMyX

Bring your X results into Muse Code.

Connect Meta's Muse Code terminal agent to your X/Twitter analytics with PilotMyX. This guide covers Muse Code, not the consumer Muse app. 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 Muse Code

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 Muse Code 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 Muse Code 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.

03 / TEST

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

See what is worth repeating — and what is not.

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

Read-only by default · Publishing requires a separate scope

Try asking Muse Code

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 Muse Code to PilotMyX

Follow these steps for Muse Code. The PilotMyX consent screen starts with read-only access; no token needs to be pasted into Muse Code.

On this page

Choose Muse Code, not the consumer app

This guide connects Muse Code, Meta's terminal agent. It does not describe a native connector in the consumer Muse app.

You need Muse Code installed and signed in, plus an active PilotMyX plan or trial with an imported X/Twitter account. The MCP connection gives Muse Code access to PMX's data; it does not give it your X credentials.

Add a Streamable HTTP server

Merge the following server into ~/.config/muse/settings.json. If you use a custom XDG configuration directory, edit its Muse settings file instead.

{
  "mcp_servers": {
    "pilotmyx": {
      "transport": "streamable_http",
      "url": "https://pilotmyx.com/mcp",
      "enabled": true,
      "mode": "required"
    }
  }
}

Keep existing settings and other servers. required means an unavailable server stops the run instead of continuing without your account data.

Sign in and inspect the tools

Complete browser authorization with:

muse mcp login pilotmyx

On the PMX screen, check the X handle and select read-only access before choosing Allow connection. Leave dynamic client registration enabled in Muse Code; PilotMyX supports it.

Open an interactive Muse Code session and run /mcp. Confirm that pilotmyx is connected and its tools are listed.

Run an account-specific analysis

Ask:

Use PilotMyX to check my account and data freshness. Compare posts and replies from the last 30 days. Which recurring topics earned profile visits? Show the examples and keep this read-only.

Check the account, timestamps and samples behind the answer. A plausible content plan without PMX tool calls does not verify the connection.

Install the PMX analysis skill using Copy prompt in MCP Access. Muse Code supports user skills under ~/.agents/skills; the installation prompt provides the current PMX bundle and workflow.

Drafting, permissions and troubleshooting

Read-only access lets Muse Code analyze results and write proposed text in the conversation. PMX draft, schedule and publish actions require their own permissions.

If a session reports 401, run muse mcp login pilotmyx and complete consent again. If the server fails at startup, check the URL and JSON settings rather than changing required to hide the error.

Use muse mcp logout pilotmyx to remove the local sign-in, and revoke its credential in MCP Access to end server-side access.

Platform documentation

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

Read the platform documentation ↗

FAQ

Before you connect Muse Code

Does Muse Code 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. Muse Code 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 Muse Code 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: