Change a custom connector's definition
A custom connector holds your organization's own REST API or MCP server: its name, its address and how a connection signs in. When the service moves or changes how it signs in, change the definition here, once, for the whole organization.
Who can do this: an Org Owner or Org Admin. For other members the Definition tab only lists the fields, with no Save and no ⋯ menu.
Change the definition
- In the sidebar, select Directory, then the Secrets tab.
- Select Add secret, then the Custom category.
- On the connector's card, select Connect, or Add another once it has a connection. The connector opens on its Connections tab.
- Select the Definition tab.
- Change what needs changing:
- Name and Description: both show in the connector list.
- Base URL for a REST API, or Server URL for an MCP server.
- Auth: how a connection signs in. It decides what a connection asks for.
- Fill in the fields the Auth choice adds:
- Header: with Header key, the header the key is sent in.
- Prefix: on a REST API with Bearer token or Header key, the word sent before the key. Picking Bearer token with an empty prefix fills in Bearer. Picking Header key clears a Bearer prefix.
- Authorize URL and Token URL: on a REST API with OAuth2.
- Scope: with OAuth2, what sign-in asks for, separated by spaces.
- Test path: on a REST API, where Test on the Connections tab sends a GET.
- Transport: on an MCP server, Streamable HTTP or SSE.
- Select Save. It stays off until something changed and both the name and the URL are filled in. Saved. shows beside it when the change is stored.
A connector stays a REST API or an MCP server. The form has no way to switch it. To change that, add a new connector.
If the save is refused, the form says Could not save. Retry. or the reason. Fix the field and select Save again. Cancel goes back to the Custom category without saving. Leaving with changes not saved opens Unsaved changes: Save, Discard or Cancel to stay.
Delete the connector instead
- On the connector's page, select ⋯ beside its name, then Delete.
- The dialog is titled Delete and the connector's name, such as Delete Billing API? It reads The definition is deleted. Refused while connections use it.
- Select Delete. Jaah returns to the Custom category.
While the Connections tab lists any connection, the delete is refused. Each connection is a secret: delete those first, as in Replace or delete a secret.
Related
- Add a custom API or MCP server: define a connector and connect to it.
- How secrets work: who owns a secret and how tasks use it.
- Secrets: every field of a custom connector.