Managing MCP Servers in Experience Workspace

This guide is for content administrators and team leads who need to connect, update, or remove a third‑party MCP (Model Context Protocol) server from Experience Workspace. No coding required.

What registration means

When you register an MCP server, Experience Workspace connects to it at the start of each chat session to discover what tools it provides. Those tools then become available to the AI assistant for the duration of that conversation.

All you need to register a server is:

A name you choose (used to identify the server in your configuration)
The server's URL (provided by the team or vendor who built the server)
Optionally, one or more authentication headers (the server team will tell you if these are needed and what values to use)

Do you need to supply credentials?

**If the server is on an Adobe domain (`*.adobe.io`)**

Nothing extra required. Experience Workspace automatically forwards the signed‑in user's Adobe identity to any server hosted under *.adobe.io. The server will recognize the user without any additional configuration on your side.

Examples of Adobe‑domain URLs:

sample (json)

https://governance-agent.adobe.io/mcp
https://my-tool.adobeioruntime.net/api/v1/web/mcp

If you are unsure whether a URL qualifies, check with the team who built the server. If the URL ends in .adobe.io or a subdomain of it, you are covered.

Development teams building MCP servers can check the Building MCPs guide

If the server is on a non‑Adobe domain

The user's Adobe identity is not forwarded automatically. The server team will need to give you a credential (usually an API key or a service token) that you supply as an HTTP header at registration time.

What to ask the server team:

What is the header name I need to send? (e.g. X-Api-Key, Authorization)
What is the header value I need to send? (e.g. a specific API key string)
Does the key expire, and if so, how do I rotate it?

Keep credentials they provide confidential — treat them like a password.

How to register a server

1. Gather the details

Before you start, have ready:

Field	Where to get it
Server name	Choose any short, unique label (e.g. `style-checker`)
Server URL	Provided by the server team — must start with `https://`
Header name + value	Provided by the server team, if needed

2. Open the Skills Editor

Navigate to the Skills Editor using the 'Manage Skills' link in the assistant and click the MCPs tab. Then click + Register MCP to open the registration form.

3. Fill in the form

Enter the server name, URL, and an optional description. If the server requires authentication headers, click + Add header to add each name/value pair.

4. Save

Click Register. The server appears immediately in the MCPs list and its tools become available to the AI assistant.

5. Verify

Start a new chat session. If the server connected successfully, its tools will be available to the assistant. If something went wrong (wrong URL, missing or incorrect credential), the server will appear as DISABLED — go back, click it to edit, and double‑check the URL and header values with the server team.

How to edit a registered server

Click any custom server in the MCPs list to open its editor. Update the URL, description, or headers as needed, then click Update to save.

Built‑in servers (DA Tools, EDS Preview) cannot be edited.

How to delete a registered server

There are two ways to remove a custom MCP server:

From the list — hover over the server card or row and click the trash icon. A confirmation dialog appears. Click Confirm to permanently remove the server, or Cancel to leave it in place.

From the editor — open the server by clicking it, then click the Delete button in the editor footer. The same confirmation dialog appears.

Once confirmed, the server is removed from the configuration immediately and will not reappear after a page reload. Any tools it provided are no longer available to the AI assistant.

Built‑in servers cannot be deleted.

Note: Deleting a server does not automatically remove tool references from existing skill or prompt markdown files that were authored while the server was connected. Those references become inert (the tool simply won't be called) but will not cause errors.

Security reminders

Keep credentials private. Anyone who has the header value can call the server on your behalf.
Only register servers from teams you trust. The AI assistant will be able to call any tool the server exposes on behalf of your users.
Never put credentials in the URL itself (e.g. ?api_key=...). Always use the mcpServerHeaders field.
Servers must use https://. A plain http:// address will not be accepted.

Need the server added to the Adobe trusted domain list?

If the server your team built lives on a non‑Adobe domain but you want it to receive the user's Adobe identity automatically (without managing a separate API key), the server URL needs to be added to the platform's trusted domain allow list. This is a deployment‑level change — raise a request with your platform or infrastructure owner and provide them with the server's hostname.