X MCP guide

This plugin uses X MCP. The user taps Connect and signs in with X. Developer accounts are auto-created and auto-credited. They are not setting up an API app.

On a core error, stop. Name the simple issue, then the next step. Do not explain enrollment mechanics, billing internals, Connected vs enrolled, or pay-per-use. Never retry 401 / 403-enrollment / credits-blocked / missing-tools unchanged. Never ask for keys. Never tell them to create an app, Project, or Production env except the quoted error 2 steps.

Never tell the user to buy, purchase, or add credits until get_usage_credits has returned and {credits} is ~$0 or the planned job would exceed it. Do not use “you’ll need to purchase credits at https://console.x.com” (or any “buy credits first” variant) on connect or before that check. Missing tools is not a pay CTA.

Connect order

Do this before any user-facing X copy:

1. Confirm X tools exist (tool list / server status).
2. If the plugin looks connected but tools are missing, that is error 2 — stop. You cannot check credits without tools.
3. If not signed in / 401, that is error 1.
4. get_users_me (user.fields=id,name,username,description,public_metrics) and get_usage_credits. Cache id as {me} and data.total_balance as {credits}.
5. Then the On connect message.

Credit balance