Connecting to the MCP server
Before an AI client can use SD Elements, it has to authenticate to the SD Elements MCP server. There are two ways to do this.
Choose how to connect
| OAuth sign-in | API key | |
|---|---|---|
How users connect |
Sign in to SD Elements in the browser, using your normal login or single sign-on |
Copy a personal API key into the client’s configuration |
Credentials stored in the AI client |
None. Short-lived tokens are managed automatically |
A long-lived API key |
Availability |
SD Elements SaaS, release 10.1 and later. Off by default |
All supported deployments. This is the default |
Who turns it on |
Your CSM or Tech Support. See Administrators: Turn On OAuth |
Nothing to turn on |
Where to start |
| OAuth and API keys are all-or-nothing for an environment. Once OAuth is turned on, the MCP server rejects API keys for every user. Plan the switch before you request it. |
| In a later release, OAuth will become available to all customers by default, and administrators will get a setting in SD Elements to turn it on or off. |
Supported AI Clients
| Client | OAuth | API Key | Notes |
|---|---|---|---|
Claude Code |
Yes |
Yes |
Validated. Setup steps |
GitHub Copilot in VS Code |
Yes |
Yes |
Validated. Setup steps |
Cursor |
No |
Yes |
Validated with API key only. If your users work in Cursor, talk to your CSM or Tech Support before turning on OAuth |
Claude Desktop |
Yes |
Requires proxy configuration |
|
ChatGPT / Codex |
Yes |
Not validated |
OAuth works only with clients that support Client ID Metadata Documents (CIMD). The clients above are allowed by default.
Other MCP-capable clients may work but have not been fully validated. For the models validated with each client, see Supported AI Clients and Agents.
Next steps
-
Administrators: Turn on OAuth
-
Users: Connect your AI client
-
Something not working? OAuth troubleshooting