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.
NanoClaw + PilotMyX
Add PilotMyX to your NanoClaw agent as a remote MCP server, with a read-only credential managed outside its chat. Connect over MCP and ask questions grounded in the posts and replies you actually published.
Which posts earned the most attention last month, and what should I test next?
From account to action
Connect once, give NanoClaw a read-only view of your results, and use the evidence to decide what to try next.
Connect your account through X. PilotMyX imports the posts and replies included in your plan and refreshes recent data daily.
Create a scoped MCP token and install the PilotMyX skill. Ask what performed, over which period, and which real posts support the answer.
Use those findings to draft a new angle. Add separate write permissions only if you want the agent to save or schedule it.
What NanoClaw can do with PilotMyX
PilotMyX supplies the facts. NanoClaw helps you interpret them and plan the next test. It does not need publishing access to analyze your account.
Inspect reach and engagement for individual posts, with the content behind each result.
See whether original posts or replies are doing the work, using a shared time window.
Compare periods and account trends before deciding whether an idea is worth repeating.
Ask for a new angle based on examples from your own account, not generic posting advice.
Grant separate write scopes when you want the agent to prepare or schedule an approved post.
Start read-only, scope each token, and revoke access from PilotMyX when you need to.
The connection
It is the bridge between NanoClaw 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 toolsRead-only by default · Publishing requires a separate scope
Try asking NanoClaw
“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
Follow these steps for NanoClaw. Start with a read-only token; add publishing permissions only when you need them.
Use a NanoClaw release that supports remote Streamable HTTP MCP servers. You need an agent group to attach the server to, a working credentials proxy, and an imported PMX account with a plan or trial.
Create a PMX token with account:read and data:read in MCP Access. Keep it outside the agent's chat and container files.
From the intended NanoClaw agent group, add a user-owned server:
ncl groups config add-mcp-server \
--name pilotmyx \
--url https://pilotmyx.com/mcp
Group-scoped agent calls target their own group. An operator running ncl on the host must select the intended group using that installation's group identifier.
You can also ask the agent to request the same server through its admin-approved add_mcp_server tool. Review and approve the change; do not disable the approval gate.
Use the exact HTTPS endpoint. Do not put credentials in its query string or change the URL to a local stdio command.
In the credentials proxy's private setup, register the PMX bearer token for outbound requests to pilotmyx.com. The request must receive:
Authorization: Bearer YOUR_PILOTMYX_TOKEN
The proxy injects the credential at the network boundary; the real token does not belong in mcp.json, agent environment variables or a message.
NanoClaw also documents an on-demand flow: a failed credentialed request can return a private connect link for the host. Open that link yourself, supply the token, and ask the agent to retry. Keep the credential scoped to the intended group and service.
Let the approved configuration change restart the affected agent, then ask:
Use PilotMyX to check my X account and data freshness. Compare posts and replies over the same 30 days. Show the evidence behind one topic worth testing again. Do not refresh, save or publish anything.
A discovered server without a successful account query is not enough. A 401 means the agent is reaching PMX without a valid credential; check the proxy's host match and Authorization header.
Install the PilotMyX MCP skill using Copy prompt from MCP Access. It teaches the agent how to page through posts, compare date ranges, and use PMX's action payloads.
Start with one bounded review. Drafting ideas in chat does not require a write token. Do not grant schedule or publish scopes to an always-on agent just to analyze data.
If registration rejects the URL, check HTTPS and remove credential-bearing URL parameters. If a server name belongs to an installed plugin template, do not edit that plugin-owned entry; add a separately named user-owned PMX server.
Remove the server from the group, remove its credentials-proxy entry, and revoke the PMX token in MCP Access when the connection is no longer needed.
Client settings change. Check the platform's current requirements before connecting.
Read the platform documentation ↗FAQ
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.
No. PilotMyX provides the account data and publishing tools. NanoClaw does the writing and analysis in your own agent session.
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.
Connect your X account, then give NanoClaw the real results behind your ideas.