It is a settings task, not a coding task. Turn on Developer mode, paste a URL, sign in. Five minutes. This walkthrough works for any remote MCP server — the Konshus URL is used as the worked example.
Before you start
Use the web app. Developer mode does not exist in ChatGPT on mobile.
Check your plan. OpenAI lists Pro, Plus, Business, Enterprise and Education.
Have the server URL ready. It must be a remote endpoint over SSE or streaming HTTP. A local stdio server cannot be reached from the web app.
The steps
Turn on Developer mode. Settings → Security and login → Developer mode. Read the warning — OpenAI classifies this as elevated risk, and that is not boilerplate.
Go back to the chat screen and open Plugins. It's in the left sidebar (under More if you don't see it). The plus button at the top right of the Plugins page only offers developer-mode apps once the toggle above is on.
Create the app and paste the URL. For Konshus that is https://konshus.ai/api/mcp. ChatGPT discovers the OAuth settings itself — leave them as found. Notices about CIMD or OIDC being unavailable are normal for servers that use Dynamic Client Registration.
Authenticate. If the server uses OAuth you will be sent to sign in and approve access. Servers with no authentication skip this — which is also a reason to be careful about which ones you trust.
Check the tool list. The app's details page shows every tool the server exposes. It may say "No app actions available yet" for a minute right after connecting — wait, then use Refresh. Use refresh here too after the server ships new tools.
Use it. In a conversation, choose Developer mode from the composer menu and select the app.
One more step: set your permissions in ChatGPT
Give it a minute. After you approve, ChatGPT may show "This connector has no tools available" for up to a minute while it fetches the tool list. That's normal and it's on ChatGPT's side — don't hit Disconnect. Close and reopen the connector and all tools will be there.
Just added a new capability? Refresh the connector.
ChatGPT reads the list of things your Vault can do once, when you first connect it, and then remembers it. If ChatGPT tells you a Konshus capability "isn't available", it's working from the old list.
Fix it inside ChatGPT (not here in Konshus): ChatGPT → Settings → Apps & Connectors → Konshus → Refresh. Give it a minute, then start a new chat.
New: ChatGPT can now read a whole document in your Vault end to end — a filing, a contract, a long export — not just find it and quote a snippet. If it says that capability isn't available, refresh the connector above. Anything you've marked Private stays unreadable, and ChatGPT will say so by name.
In ChatGPT this is one setting, not a list of tools. Go to Settings → Plugins → Konshus → Permissions and pick how often it should stop and ask you.
Allow low-risk actions (the default)
Reads mostly go through, but ChatGPT can still stop and ask before saving anything back to your Vault. Fine to start here.
Allow read actions — the minimum we'd pick
Your Whisper loads silently at the start of a chat instead of interrupting you with a popup. ChatGPT still asks before anything is written.
Allow all actions — on the AI you use every day
This is what makes your Konshus grow without you babysitting it: things worth remembering get saved back as you talk. ChatGPT tags it elevated risk — that's a blanket label it puts on every connector, not a judgement about Konshus. Nothing we expose deletes anything, and everything that lands is reviewable in Sources. Leave it on "Allow read actions" if this is a shared or second machine.
Right after you connect, this page may say "No app actions available yet". That's ChatGPT still fetching the tool list — wait a minute and hit Refresh.
When ChatGPT ignores your tools
This is the most common complaint and it is almost never a broken connection. The model has many tools available and picks what it thinks fits. Be explicit:
Use the "Konshus" app's search_atoms tool to find what you know about my writing style. Do not use browsing or any other tools.
Naming the app, naming the tool, and explicitly ruling out alternatives fixes the large majority of "it did not call my server" reports. OpenAI recommends the same pattern in their own guidance.
Write actions deserve a pause
Read tools are low stakes — worst case you get an unhelpful answer. Write tools can delete, overwrite, or share real data, and the model can get the arguments wrong. ChatGPT asks for confirmation on writes by default. Leave that on, and actually read the payload it shows you before approving. Expanding the tool call to inspect the JSON takes two seconds and has saved people real damage.