Credentials. The Runtime API key controls the Secure MCP Tunnel, so store it only in the OS credential store and never paste it into chat or commit it to Git.
Who it is forA developer who wants ChatGPT to read, change, and test a local project without copying code back and forth by hand.
The problemChatGPT in a chat window cannot touch the files and commands on your machine, so every change needs manual copying.
The outcomeChatGPT calls OpenChatX file and shell tools against a bound project folder and reports the results in the same chat.
What you need first
- A ChatGPT account with access to Developer Mode and MCP apps, or the Plugins flow described in the README
- An OpenAI Platform account with permission to create a Secure MCP Tunnel and a Runtime API key
- Windows or macOS for the Desktop App, or Node.js 22.18+, npm, ripgrep, and OpenAI tunnel-client for the source install
Steps
- Download the matching installer from https://github.com/XiaoPuOuO/openchatx-mcp/releases/latest and install OpenChatX Desktop.
- In OpenAI Platform, create a tunnel on the Tunnels page and copy the tunnel_... ID.
- Create a Runtime API key on the API Keys page and store it safely.
- Open OpenChatX Desktop, go to More, choose Connect Tunnel, and enter the Tunnel ID and control-plane API key.
- In ChatGPT, finish the MCP app by selecting the openchatx tunnel, setting authentication to No authentication, and clicking Create.
Prompt for your agent
Using the OpenChatX MCP connection in the openchatx-mcp repo, open the project at <project-folder> as a Projects workspace and list its files, then run its test command through the shell tool. Report which files changed and the test result. Verify that the shell output matches what you see in the project folder.
Caveat. OpenChatX runs with your local user permissions, so a trusted ChatGPT caller can change files and run commands on the machine.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page