Skip to main content

Kimi K3 + PilotMyX

Plan your next X test with Kimi K3.

Use Kimi Code's MCP client to analyze your X/Twitter posts and replies with the Kimi model available on your 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 Kimi K3

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

See what is worth repeating — and what is not.

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

Read-only by default · Publishing requires a separate scope

Try asking Kimi K3

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 Kimi K3 to PilotMyX

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

On this page

Connect Kimi through Kimi Code

This guide uses Kimi Code CLI as the MCP client. Kimi K3 is a model choice, not an MCP configuration screen. Select the model available on your Kimi account; this setup does not unlock a model your plan does not include.

You need Kimi Code installed and signed in, and a PilotMyX plan or trial with imported X/Twitter posts and replies.

Keep the PMX credential in the environment

Create a token in MCP Access with account:read and data:read. Store it as PILOTMYX_MCP_TOKEN in Kimi Code's private process environment.

Do not put the value in a chat message, a shared repository, or a command saved to history.

Add an HTTP server in Kimi Code

Merge this entry into your user-level ~/.kimi-code/mcp.json:

{
  "mcpServers": {
    "pilotmyx": {
      "url": "https://pilotmyx.com/mcp",
      "bearerTokenEnvVar": "PILOTMYX_MCP_TOKEN",
      "enabled": true
    }
  }
}

If you configured KIMI_CODE_HOME, use its mcp.json instead. A project-level .kimi-code/mcp.json with the same server name overrides the user-level entry.

Kimi Code treats a URL entry as HTTP unless another transport is specified. Use this remote setup, not a local stdio command or a legacy SSE transport.

Open a new session and test the tools

Start a new Kimi Code session after editing the file. Run /mcp to inspect connection status; /mcp-config manages server settings.

Install the PMX analysis skill with Copy prompt from MCP Access, then ask:

Check my PilotMyX account and freshness. Compare the last 30 days of posts with replies. Which repeated topics brought profile visits? Show the posts behind the conclusion. Keep this read-only.

Verify actual PMX calls, the account identity, and the date range before using the answer as a content plan.

Permissions and troubleshooting

Keep approval for unfamiliar actions. A client-level allow rule is not a replacement for PMX's scoped token.

If the server is missing from an existing session, start a new one. If authentication fails, check the environment variable in the Kimi process and whether the token is active. If a tool cannot write, read-only access is working as designed.

Draft in the conversation before granting draft or scheduling scopes. Revoke the token in MCP Access when you stop using the connection.

Platform documentation

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

Read the platform documentation ↗

FAQ

Before you connect Kimi K3

Does Kimi K3 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. Kimi K3 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 Kimi K3 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: