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.
DeepSeek + PilotMyX
Run DeepSeek in OpenCode and give it access to your X/Twitter analytics through PilotMyX's remote MCP server. 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 DeepSeek 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 DeepSeek can do with PilotMyX
PilotMyX supplies the facts. DeepSeek 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 DeepSeek 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 DeepSeek
“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 DeepSeek. Start with a read-only token; add publishing permissions only when you need them.
DeepSeek is the model; OpenCode is the MCP client in this setup. These instructions do not add a connector to the DeepSeek consumer chat website.
Install OpenCode and connect your DeepSeek provider using /connect. Then use /models to select a tool-capable DeepSeek model available to your account. Model-provider usage and your PilotMyX subscription are separate.
The OpenCode provider guide describes provider sign-in.
Connect your X/Twitter account to PilotMyX and wait for its import. In MCP Access, create a token with account:read and data:read.
Store it privately as PILOTMYX_MCP_TOKEN in the environment of the process that launches OpenCode. Do not paste the token into the conversation or commit it to a project.
Merge this entry into opencode.json in your working directory, or into your existing user configuration.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pilotmyx": {
"type": "remote",
"url": "https://pilotmyx.com/mcp",
"enabled": true,
"oauth": false,
"headers": {
"Authorization": "Bearer {env:PILOTMYX_MCP_TOKEN}"
}
}
}
}
The {env:PILOTMYX_MCP_TOKEN} syntax belongs to OpenCode. oauth: false selects the scoped-token route rather than starting an OAuth flow.
Restart OpenCode with the environment variable set, and run opencode mcp list to check the server.
Install the PilotMyX MCP skill using Copy prompt in MCP Access, then ask:
Use PilotMyX to check my account and data freshness. Compare posts and replies over the same 30 days. Show which topics earned profile visits, with examples and sample sizes. Do not make changes.
Check that OpenCode calls PMX tools while the DeepSeek model is selected. The answer should name your account and use imported records, not generic posting advice.
A missing-variable error means OpenCode did not inherit PILOTMYX_MCP_TOKEN. A 401 means the credential is missing, revoked or invalid. A scope error means that particular action is not allowed.
If the selected model does not call tools, select a tool-capable model or check OpenCode's tool settings. Do not broaden the token just to make a model invoke it.
Ask for proposed text in the conversation first. Saving or scheduling through PMX needs separate write scopes. Remove the client entry and revoke the token in MCP Access when finished.
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. DeepSeek 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 DeepSeek the real results behind your ideas.