Add an OAuth client for an MCP server
Some MCP servers don’t support dynamic client registration (DCR), so the gateway can’t register itself with them. For these servers, you register an OAuth app with the server’s provider, and then add that app to Fabric as an OAuth client. An MCP connection that uses the client signs people in to the server with your app. This topic shows you how to add an OAuth client and select it on an MCP connection.
Prerequisites
Before you begin, make sure you have the following:
- The Manage IDP permission. The OAuth clients page and its Add OAuth client page are available only to people who have it. People without it can’t open them, but a namespace admin who edits a connection can still pick from the existing clients in the OAuth client list.
- An OAuth app that you created with the MCP server’s provider. Have its client ID, and its client secret if it has one.
- The URL of the MCP server that the app is registered for.
Add an OAuth client
To add an OAuth client, do the following:
-
In the sidebar, select Admin, and then select OAuth clients. The page lists your clients with their Name, MCP server, Client ID, and Client secret.
-
Copy the Redirect URI that the page shows. It’s the data plane URL followed by
/api/v1/oauth/broker/callback. In your OAuth app’s settings with the provider, add it as an allowed redirect URI. Do this before anyone connects, or the provider rejects the sign-in. -
Select Add OAuth client.
-
Under OAuth app, enter a Name, for example
acme-mcp. Connections refer to the client by this name, and you can’t change it later. Start with a letter or number, and then use letters, numbers, dots, dashes, and underscores. The namenewis reserved. -
Enter the Client ID from your OAuth app.
-
For Client secret, enter the secret from your OAuth app. Leave it blank if your OAuth app has no secret. How you enter it depends on where your organization keeps secrets:
- Shared data plane: type the secret. Fabric stores it encrypted and never shows it again.
- Dedicated data plane: pick a Vault and enter the value reference for the secret. Fabric doesn’t store the secret itself.
-
Under MCP server, enter the MCP server URL that your OAuth app is registered for. The URL must start with
https://, except thathttp://is accepted for a loopback host such aslocalhost. It can’t contain a username, password, query string, or fragment. Only connections whose target URL matches this URL can use the client. The gateway also finds the sign-in endpoints from it. -
Optional: Enter Scopes (optional), separated by spaces or commas. Fabric uses them when a connection asks for none. If you leave it blank, Fabric uses the scopes that the server advertises.
-
Optional: If the server doesn’t publish OAuth metadata, select Enter the sign-in endpoints yourself, and then enter the Authorization URL and Token URL.
-
Select Add OAuth client. The client appears in the list.
To change a client later, select Edit in its row. To replace a stored secret, select Replace. To remove a client, select the delete icon in its row, and then confirm. Deleting a client also removes its secret and can’t be undone, and Fabric doesn’t delete a client that connections still use.
Select the client on an MCP connection
A client is available on MCP connections only. Select it when you create the connection, or add it to an existing one.
To select an OAuth client on a new connection, do the following:
- Follow the steps in Connect an MCP server until you reach Upstream auth.
- For Auth type, select OAuth.
- For OAuth client, select the client. The list starts with Dynamic registration, where the gateway registers its own client with the server. Clients registered for a different MCP server URL are listed but can’t be selected.
- Finish the form, and then select Create connection.
Some catalog servers use only your organization’s own OAuth app. For those, the list has no Dynamic registration option, and you must pick a client before you can save the connection.
To select a client on an existing connection, do the following:
- In the sidebar, select MCP servers, and then select the connection.
- Select the Upstream tab.
- Next to Auth requirement, select Edit.
- For OAuth client, select the client, and then save your change.
The OAuth client control doesn’t appear on a connection whose credentials are stored on its upstream instead of on the connection, or on a catalog provider that doesn’t take an organization-level OAuth client.
If you change the client on an existing connection, everyone who connected through it has to connect again.
If no client fits the connection’s target URL, the list shows No OAuth client is registered for this server. If you have the Manage IDP permission, select Add an OAuth client to open the form with the target URL filled in. Otherwise, ask an admin to add one.
Next steps
- To learn how people sign in to the server, see Connect your accounts to MCP servers.
- To add upstreams or change the access mode, see Connect an MCP server.

