Skip to main content

Grok Build + PilotMyX

Review your X results from Grok Build.

Connect Grok Build to PilotMyX over HTTP, then compare your X/Twitter posts and replies from the terminal. 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 Grok Build

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

See what is worth repeating — and what is not.

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

Read-only by default · Publishing requires a separate scope

Try asking Grok Build

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 Grok Build to PilotMyX

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

On this page

Before you connect

Use a current Grok Build installation with HTTP MCP support. Connect your X account to PilotMyX, start a plan or trial, and wait for the account import.

This guide is for the grok terminal client, not the Grok web app or Grok Bot. Grok Build supports OAuth for remote servers, so the main setup does not require a manually copied PMX token.

Register the HTTP server

From your terminal, run:

grok mcp add --transport http pilotmyx https://pilotmyx.com/mcp
grok mcp doctor pilotmyx

On first use, complete the browser authorization. Check the connected X handle on PilotMyX's consent screen, keep read-only access selected, and choose Allow connection.

For a configuration-file setup, merge this entry into your user-level ~/.grok/config.toml:

[mcp_servers.pilotmyx]
url = "https://pilotmyx.com/mcp"

Keep your existing settings. Do not replace the whole file with this snippet.

Confirm that the tools can read PMX

Run grok mcp list and inspect the server with grok mcp doctor pilotmyx. In the TUI, /mcps opens the MCP panel; its authenticate action lets you finish OAuth when needed.

Then ask:

Check my PilotMyX account and sync freshness. Find the posts with the strongest profile-visit results over the last 30 days. Compare them with my replies over that same period. Show the evidence and do not make changes.

A successful test returns account data through PMX tools. Server registration alone is not a successful analytics query.

Install the analysis workflow

Use Copy prompt in MCP Access to install the PilotMyX MCP skill in the agent. It describes pagination, comparing like-for-like periods, and the payloads used by PMX's compact tools.

Start by asking for a draft in chat. Grant draft or schedule permissions separately if you want Grok Build to save that draft in PMX. Do not disable approvals to make publishing easier.

Fix or remove a connection

Use grok mcp doctor pilotmyx for connectivity and authentication errors. Check that you edited the active configuration: a project-level .grok/config.toml can override a user-level server with the same name.

Run grok mcp remove pilotmyx to remove the client entry. Revoke its credential in MCP Access as well; removing a local setting does not revoke server-side access.

Platform documentation

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

Read the platform documentation ↗

FAQ

Before you connect Grok Build

Does Grok Build 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. Grok Build 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 Grok Build 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: