Skip to main content

Gemini CLI + PilotMyX

Ask Gemini CLI what worked on X.

Use Gemini CLI to inspect your X/Twitter results before planning the next posting test. 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 Gemini CLI

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

See what is worth repeating — and what is not.

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

Read-only by default · Publishing requires a separate scope

Try asking Gemini CLI

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 Gemini CLI to PilotMyX

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

On this page

Before you connect

This guide is for Gemini CLI, not the Gemini web app. Connect your X account to PilotMyX and create a read-only token in MCP Access before you edit Gemini CLI settings.

Add the HTTP server

Open your user-level ~/.gemini/settings.json. Add pilotmyx under mcpServers, keeping any existing servers in place:

{
  "mcpServers": {
    "pilotmyx": {
      "httpUrl": "https://pilotmyx.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_PILOTMYX_TOKEN"
      }
    }
  }
}

Replace YOUR_PILOTMYX_TOKEN locally. This example is for a private user-level file. Never commit a file containing the real header value. If your environment offers a secret store for headers, use it instead.

Confirm Gemini can read your account

Run gemini mcp list and check that pilotmyx is connected. Install the PilotMyX MCP skill with Copy prompt from MCP Access so Gemini knows how to use the tools in a useful sequence.

Check when PilotMyX last refreshed my X data. Compare original posts and replies from the same recent period, show the sample size, and suggest one post to test. Do not save or publish it.

If the server connects but produces generic advice, ask Gemini to call PilotMyX tools and show the posts behind its conclusion. If it reports 401, confirm the header starts with Bearer and that the token is still active. Grant write scopes only after you have reviewed a read-only analysis.

Platform documentation

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

Read the platform documentation ↗

FAQ

Before you connect Gemini CLI

Does Gemini CLI 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. Gemini CLI 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 Gemini CLI 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: