PilotMyX Documentation

What does PilotMyX do?

PilotMyX is the data and publishing layer between an X account and an agent workflow.

The platform imports posts, replies, and available account data through the official X API, stores a durable copy, and records when each metric set was last refreshed.

Dashboard and MCP queries read that stored copy. The scheduler keeps drafts and future publications visible so the account owner can review, change, or cancel them.

• Synchronize account posts, replies, and account-level metrics
• Inspect post and reply totals, changes, freshness, and rankings
• Give a compatible agent narrowly scoped MCP access
• Create drafts with images or quoted-post links
• Publish now or manage an editorial schedule

How does PilotMyX fit into an agent workflow?

PilotMyX owns the deterministic data and publishing layer.

Your connected workflow can interpret the source data returned through MCP, while PilotMyX remains responsible for synchronization, factual analytics, draft storage, and controlled publication.

A typical workflow

Connect X once, then let your preferred workflow query the synchronized data as often as needed.

Create an account and authorize the X connection. PilotMyX performs the initial synchronization and shows its progress. Create an MCP token with the minimum required scopes, connect it to a compatible client, and use the retrieved analytics in your local workflow. When posts are ready, place them on the calendar and keep final control in PilotMyX.

How fresh is the data?

Every analytics response should be read together with its freshness fields.

X metrics change over time. PilotMyX synchronizes incrementally and refreshes due metrics instead of refetching every resource for every view. The interface and MCP responses identify the relevant data timestamp and flag unavailable post metrics.