Bring X analytics to AI agents with CLI access.

Use an MCP client from the terminal

An agent with shell access can use MCPorter to discover and call PMX's remote MCP tools. MCPorter is a third-party client, not a PilotMyX posting CLI.

Use its installation guide for your operating system. Confirm the executable is available with:

mcporter --version

Run it on the computer where the agent executes commands. Installing it on your laptop will not make it available on a separate cloud computer.

Set up a scoped credential

Connect your X/Twitter account to PMX and wait for the import. Create a token with account:read and data:read in MCP Access.

Supply it through the agent computer's private environment as PILOTMYX_MCP_TOKEN. Do not paste it into the agent's conversation, command history or shared files.

Create the client configuration

Create a private pilotmyx-mcporter.json configuration with this entry. The file contains a variable reference, not the token.

{
  "mcpServers": {
    "pilotmyx": {
      "url": "https://pilotmyx.com/mcp",
      "headers": {
        "Authorization": "Bearer ${PILOTMYX_MCP_TOKEN}"
      }
    }
  }
}

MCPorter resolves ${PILOTMYX_MCP_TOKEN} when it starts the transport. The configuration reference covers variable syntax and file precedence.

Discover tools and check the account

Pass the configuration explicitly so an unrelated client's settings cannot override it:

mcporter --config ./pilotmyx-mcporter.json list pilotmyx --schema
mcporter --config ./pilotmyx-mcporter.json call pilotmyx.account \
  --args '{"action":"get","payload":{}}'

Confirm the returned X handle and freshness. Listing tools alone does not prove that the token can read your account.

The compact tool is named account; get is its action. Do not invent commands such as get_account or top_posts.

Give the agent the action contracts

Install the PilotMyX MCP skill using Copy prompt in MCP Access. It documents the action payloads, date ranges, pagination and scope requirements.

Have the agent compare posts and replies over the same period, then draft a proposed post in its response. Do not enable schedule or publish permissions for an initial analysis.

Troubleshooting and revocation

If the executable is missing, install MCPorter on the agent's actual computer. If the variable is missing, fix that process's private environment. If PMX returns 401, check token validity; if it reports insufficient scope, check the requested action.

Keep command output containing private posts out of public logs. Removing the JSON file does not revoke the token: revoke it in MCP Access as well.