Connect Claude or ChatGPT

Connecting takes about a minute. You paste one address into your assistant, sign in to Kops, and approve what the assistant may do. Everything it can reach after that is listed on what your assistant can do.

#What you need

• A Kops account you can sign in to. The assistant acts as you, so it gets the permissions your role already has and never more.
• The workspace you want it to work in. A connection is bound to one workspace, chosen when you approve it — not switchable afterwards.
• On Claude: any plan, including Free, which allows a single connector. On ChatGPT: a paid plan, on the web app.

You do not need an API key, and you will never be asked for your Kops password by the assistant.

#The address

This is the whole configuration — one address, the same for everyone:

Copy it as it is. It has to be the full address including https://; assistants reject anything else.

#Claude

#On a personal plan

1. Open Customize → Connectors.
2. Click +, then Add custom connector.
3. Paste the address above.
4. Click Add.

Leave Advanced settings alone. It asks for an OAuth Client ID and Secret, which exist for servers that hand out credentials by hand — Kops registers your assistant automatically the first time it connects, so filling those in is how you get a connection that fails.

Once added, turn it on for a conversation with the + button at the bottom left of the chat, then Connectors.

#On a Team or Enterprise plan

An owner adds it once for everyone:

1. Organization settings → Connectors.
2. Click Add, hover Custom, choose Web.
3. Paste the address, click Add.

Members then open Customize → Connectors, find it in the list, and click Connect — which is where each person signs in and picks their own workspace. The owner's setup does not connect anybody's account, and it cannot: the approval is per member, because the permissions are per member.

#ChatGPT

ChatGPT reaches outside servers through developer mode, on the web app only — a connector added on chatgpt.com shows up in the desktop and mobile apps afterwards, not the other way round.

1. Enable developer mode in Settings. On a Business, Enterprise or Education workspace an administrator has to allow it first, and cannot enable it for one person only.
2. Add a custom connector, giving it a name and the address above.
3. Approve the warning ChatGPT shows about third-party servers, then sign in to Kops when it sends you there.

warning Two things move here and one is worth checking before you start. OpenAI has renamed this surface more than once — look for Apps or Connectors in Settings — and what your plan may do with a custom connector is gated: several plans can only use tools that read. Kops publishes tools that write (creating a filter, blocking a seller), so those simply will not appear on a read-only plan. Everything that reads still works.

Deep research is not the path. That mode expects a server built around two generic tools, and Kops publishes named ones instead — it will connect and find nothing to call.

#What you approve

Whichever assistant you use, the last step is a Kops screen, and it is the one worth reading rather than clicking through. It names three things:

• which application is asking,
• which workspace it will act in,
• exactly what it will be allowed to do, one sentence per permission.

Approving grants that list and nothing outside it. An assistant that later tries something the list did not cover is refused — there is no setting that widens a connection after the fact, and no way for the assistant to ask for more without sending you back to this screen.

#Check that it works

Ask for something you can verify in a second, in plain language:

list my filters

You should get your own filters back, from the workspace you picked. If the assistant answers from general knowledge instead — describing what a filter is, or inventing plausible names — it is not actually connected. Check that the connector is toggled on for this conversation before assuming the connection failed.

#Disconnecting

Two places, and they do different things.

In Kops — Settings → Connections. Disconnect there and every credential that application holds stops working immediately, not at the end of a session. This is the one to use if something is wrong.

In your assistant. Removing the connector there stops it offering the tools, but is a change to your assistant's configuration rather than to what Kops will accept. Do both when you are done with an assistant for good; do the Kops one first when you are in a hurry.

#When it does not work

The assistant cannot see the connector at all. On ChatGPT this is usually the plan or the workspace administrator, not a mistake in the address — see the warning above. On Claude Free, check you are not already using your one connector on something else.

Signing in works, then nothing happens. You approved in a browser where you were signed in to a different Kops account than you expected. Sign out, connect again, and read the workspace name on the approval screen.

It connects but every request is refused. The connection is bound to a workspace where your role does not have the permission being used. The approval screen showed the permission list; your role decides which of those actually resolve.

A tool you expected is missing. It was not part of what you approved, or it does not exist. The full published list is on what your assistant can do — check there first, then disconnect and reconnect to see the approval screen again.