ChatGPT
Connect TwexAPI to ChatGPT with Developer mode and sign in with your TwexAPI account to search X posts, profiles, followers, and trends.
ChatGPT connects to the TwexAPI MCP server at https://api.twexapi.io/mcp and signs you in with your TwexAPI account. ChatGPT cannot send custom headers, so it does not use API keys; every connection goes through the sign-in page. Calls use your TwexAPI credits.
Requirements
- Developer mode, which lets ChatGPT connect to your own MCP servers. OpenAI offers it on selected plans and lets workspace admins restrict it. If you cannot find it, check OpenAI’s Developer mode guide for your account.
- A TwexAPI account with an active API key and credits. Create the key in the TwexAPI dashboard.
ChatGPT on the web
Turn on Developer mode
Open Settings and turn on Developer mode. In recent versions it is under Security and login; older versions put it under Connectors → Advanced settings.
Add TwexAPI
Open Plugins (or Apps), select +, and add a custom MCP server. Enter TwexAPI as the name and https://api.twexapi.io/mcp as the URL. Choose OAuth if ChatGPT asks for an authentication type, then create it.
Sign in
ChatGPT opens the TwexAPI sign-in page. Sign in, choose whether ChatGPT may post for you, and select Approve.
Use it in a chat
Start a new chat, select TwexAPI from the + menu or by typing @, and describe your task.
ChatGPT desktop app
Open the custom MCP form
Open the app’s settings and choose to connect a custom MCP server.
Choose Streamable HTTP
Enter TwexAPI as the name and switch the type from STDIO to Streamable HTTP. Enter https://api.twexapi.io/mcp as the URL. Leave any token, header, or environment variable fields empty, then save.
Sign in
Your browser opens the TwexAPI sign-in page. After you select Approve, the browser shows a 127.0.0.1 page that says authentication is complete. That local address is how the desktop app receives the result; close the window and return to ChatGPT.
Tools
ChatGPT sees the same tools as every other client:
| Tool | What it does |
|---|---|
explore |
Finds the endpoint for a task and its inputs. Uses no credits. |
twexapi_request |
Reads X data: search, tweets, replies, threads, profiles, followers, communities, lists, and trends. |
twexapi_write |
Posts a tweet or reply. Listed only when you granted write access. ChatGPT asks before each call. |
Posting needs the X account cookie of the account that posts, and the cookie passes through your ChatGPT conversation. To keep ChatGPT read-only, clear the write checkbox on the sign-in page.
See the MCP tools reference for details.
Credits
Each call costs the same as the equivalent REST request. When your balance runs out, the connection keeps working and ChatGPT reports “No credits left on this TwexAPI account”. Top up in the dashboard and ask again.
Troubleshooting
| Problem | Fix |
|---|---|
| Developer mode or the add button is missing | Your plan or workspace admin may not allow custom MCP servers. See OpenAI’s guide. |
| Sign-in fails or loops | Remove TwexAPI from ChatGPT, add it again, and sign in. |
| The sign-in page says you have no API key or no credits | Fix it in the dashboard, then select Approve again within 10 minutes. |
| A tool is missing | Refresh the connector in ChatGPT. If twexapi_write is missing, you connected read-only. |
| You want to disconnect | Revoke ChatGPT under Authorized apps in the dashboard, and remove the connector in ChatGPT. |
Older guides suggested a Custom GPT with an OpenAPI Action. That still works with an API key for the REST API, but Developer mode with sign-in is the supported way to use the MCP server.