Skip to content

Custom Connector OAuth Credentials Not Saving — Client ID and Secret Lost After Add #344

Description

@sethmclane

MCP server URL

https://NCSOICATESTic-ncsoic.integration.us-ashburn-1.ocp.oraclecloud.com/mcp-server/v1/projects/PRODUCTMANAGEMEN_MCP/mcp

Where does the issue occur?

Other

Transport used

streamable-http

Client registration type

My server does not have auth

SSE only: Does your server return the expected status code for POST requests?

Not applicable (my server does not use SSE)

When did you last reproduce this?

2026-05-22 2:25pm

Browser and OS

Chrome Version 148.0.7778.97 Windows 11

Describe the issue

When creating a custom MCP connector in Claude Enterprise (web and desktop app), the OAuth Client ID and Client Secret fields under Advanced Settings do not persist after saving.

Issue details

Steps to reproduce:

Go to Organization Settings → Connectors
Click + Add → enter connector name and MCP server URL
Expand Advanced Settings
Enter OAuth Client ID and Client Secret
Click Add
Go back to the connector → three dots → See details → expand Advanced Settings

Expected result: Client ID and Secret should be saved and visible (Secret masked)
Actual result: Both fields are blank — showing only the placeholder text "OAuth Client ID (optional)" and "OAuth Client Secret (optional)"
Impact: Without saved OAuth credentials, the connector never presents a Connect button to users, making it impossible to complete the OAuth Authorization Code flow. The connector is effectively non-functional for any MCP server requiring OAuth authentication.
Environment:

Claude Enterprise (web)
Claude Desktop app
Both exhibit the same behavior
Connector type: Custom MCP
OAuth flow required: Authorization Code

Additional context: This connector is pointing to an Oracle Integration Cloud (OIC) MCP Server that requires OAuth. The IDCS OAuth application is fully configured with Authorization Code grant type, redirect URL (https://claude.ai/oauth/callback), and bypass consent enabled. All OAuth settings on the server side are correct — the credential save issue appears to be entirely on the Claude side.

Expected behavior

The connection is created with the OAuth credentials, and a connect button made available.

Logs from your server

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions