Search AEM Content Using the Content AI MCP Server
Use the Content AI MCP Server from Adobe CX Coworker to search and analyze Content AI indexes in natural language, no low-level API code or UI navigation.
In this tutorial you discover available indexes, run keyword, semantic, and hybrid searches, and use natural language search to express complex intent, all from Adobe CX Coworker against a Content AI index.
Overview
AEM as a Cloud Service provides MCP Servers so your IDE or chat app can work with AEM securely. The Content AI MCP Server exposes search and discovery tools over Content AI indexes. See MCP Servers in AEM for more information.
The Content AI MCP Server provides six tools:
list_indexesget_index_configfulltext_searchsemantic_searchhybrid_searchnatural_language_searchThe Content AI MCP Server supports two access modes, selected by which header you configure:
- Public (anonymous) — Search public, read-only indexes using the
X-Api-Keyheader. Use this for openly available, non-sensitive content. See Searching Public Indexes. - Authenticated — Search entitled or access-controlled indexes using the
x-content-ai-mcp-api-keyheader together with your signed-in Adobe identity (passed through by CX Coworker). Results respect your permissions.
How Developers Can Use It
Connect Adobe CX Coworker to the Content AI MCP Server and run the scenario below.
Setup - Content AI MCP Server in Adobe CX Coworker
Let’s set up the Content AI MCP Server in Adobe CX Coworker with these steps.
-
Sign in to Adobe CX Coworker.
-
From the side rail, click MCP Servers.
-
Click Add MCP Server.
-
In the Add MCP Server dialog, enter the following details:
table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 Field Value Server name content-ai-mcpMCP URL https://mcp.adobeaemcloud.com/adobe/experimental/aemagents-expires-20260331/mcp/content-aiConnection type HTTPAuthentication type Passthrough
note NOTE Authentication type is set to Passthroughso CX Coworker forwards your signed-in Adobe identity to the MCP Server. You do not need a separate sign-in or OAuth step. -
Click Add headers and add the headers for the access mode you need:
For public indexes (anonymous):
table 0-row-2 1-row-2 2-row-2 Header Value X-Api-KeyYour public API key. Present this header when you only want to search public indexes. x-content-ai-mcp-routing(Optional) Environment/routing info, for example tier=publish,bucket=p12345-e67890,cluster=ethos21-prod-va7,namespace=ns-team-example.For non-public (entitled) indexes:
table 0-row-2 1-row-2 2-row-2 Header Value x-content-ai-mcp-api-keyThe API key from the Adobe Developer Console. x-content-ai-mcp-routing(Optional) Environment/routing info, for example tier=publish,bucket=p12345-e67890,cluster=ethos21-prod-va7,namespace=ns-team-example.note important IMPORTANT When the X-Api-Keyheader is present, the server treats the request as anonymous and only searches public indexes. Any signed-in identity is ignored, so there is no accidental escalation to authenticated access. Usex-content-ai-mcp-api-key(notX-Api-Key) when you intend to search entitled indexes.note NOTE If you do not set the x-content-ai-mcp-routingheader, the server asks for your environment (tierandbucket) in chat the first time you run a tool, then retries automatically. -
Click Add. The content-ai-mcp server now appears in your list of MCP Servers.
-
Click New chat to start using the Content AI MCP Server.
Searching Public Indexes
Some Content AI indexes are marked public and can be searched anonymously, without an entitled identity. Public indexes are read-only and are intended for openly available, non-sensitive content. Anyone with the public API key can search them.
Use this mode when:
- You want to search openly available content (for example, public documentation or a demo catalog).
- You do not need per-user, permission-scoped results.
- You want a simple setup that only requires an API key.
To search public indexes, add the Content AI MCP Server in CX Coworker exactly as described in Setup - Content AI MCP Server in Adobe CX Coworker, but in the Add headers step add only the X-Api-Key header (plus an optional x-content-ai-mcp-routing header for the environment):
X-Api-Keyx-content-ai-mcp-routingtier=publish,bucket=p12345-e67890.X-Api-Key header is present, the server treats the request as anonymous and only searches public indexes. Any signed-in identity is ignored. Do not use X-Api-Key when you intend to search entitled indexes, use x-content-ai-mcp-api-key instead.With the server connected, discover and search public indexes the same way as authenticated indexes.
-
In CX Coworker, open a new chat and list the public indexes available to your API key:
code language-text List all Content AI indexes available in my environment.The server searches only public indexes for this request and returns matching results.
Summary
You set up the AEM Content AI MCP Server in Adobe CX Coworker and used it to search Content AI indexes. You discovered available indexes and searched them in natural language, using keyword, semantic, hybrid, and natural language search. You also learned how to search public indexes anonymously with an API key, and how to reduce response size with field selection. You can use the same human-centric flow from CX Coworker to search and analyze Content AI indexes without switching to a UI or writing low-level search API code.