---
title: "Amazon Q Index MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/awslabs-amazon-qindex/
description: "ISV-only Amazon Q index search that waits for a pasted OIDC code, then assumes a supplied role before SearchRelevantContent."
---

# Amazon Q Index MCP: review, setup & limitations · Undominated.ai

> ISV-only Amazon Q index search that waits for a pasted OIDC code, then assumes a supplied role before SearchRelevantContent.

[← Explore all mcp servers](/mcp-servers/)

ENTERPRISE SEARCH / AWS Labs

# Amazon Q Index MCP

ISV-only Amazon Q index search that waits for a pasted OIDC code, then assumes a supplied role before SearchRelevantContent.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/awslabs/mcp/tree/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-qindex-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher AWS Labs
 Licence [Apache-2.0 ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE)
 Revision 8840003820a7
 [Read what was—and wasn’t—checked ↓](#review)

“Searches an enterprise Amazon Q index for registered ISV data accessors after an OIDC code and an assumed role.”

 [AWS Labs · upstream description ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-qindex-mcp-server/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Search does not start from the query alone. The README stops for an OIDC redirect and a pasted authorization code, and AuthorizeQIndex takes a random state value for CSRF protection.
- SearchRelevantContent is reached only after CreateTokenWithIAM and AssumeRoleWithIdentityContext. The README says not to hardcode credentials and not to log tokens.

### A good fit for

 - A registered ISV data accessor searching a customer's Amazon Q index after the user finishes the OIDC redirect
- Not for an Amazon Q Business application owner, because the README says that direct integration is not yet available

### Weigh up before choosing

 - The README says this implementation is for demonstration purposes only. The production list tells the reader to add session management, token refresh, validation, and revocation. It does not say the demo already does those.
- The Kiro JSON args use awslabs.amazon_qindex_mcp_server and omit @latest. The Windows args use awslabs.amazon-qindex-mcp-server@latest. Those strings are not the same.
- The install badges set QINDEX_ID. The tool parameters and the usage steps never name that variable. They ask for an application id, a retriever id, an Identity Center ARN, regions, a redirect URL, and a role ARN in the conversation.
- pip install -e . installs the cloned server directory in editable mode. It does not install the published package, and it does not install one file by itself. The uvx package line is indented, so it is not the recorded command.
- AssumeRoleWithIdentityContext returns temporary credentials for the search call. The role ARN is an input. The README does not document creating an IAM user, role, policy, or long-lived access key.
- stdio is named only in the Windows block. The other JSON block does not name a transport.
- A pin does not verify transitive dependencies. The Windows package argument uses @latest, which is not this commit.
- This review did not execute the resource.
- The server was not started and its tools were not called.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - src/amazon-qindex-mcp-server/README.md
- README.md
- LICENSE

### Our findings

 - AuthorizeQIndex returns an OIDC authorization URL and requires a random oauth_state string for CSRF protection, plus the Identity Center region, the registered redirect URL, and the application ARN.
- The usage steps stop until the operator opens that URL, authenticates, and pastes the authorization code from the redirect.
- The server then creates a token through IAM, assumes the supplied role, and only then calls SearchRelevantContent. The result cap is 1 to 100.
- The README says never to hardcode credentials, never to log tokens, and to store them securely. It also says the server is a demonstration of user-aware search, not a production implementation.
- Direct use by Amazon Q Business application owners is described as not yet available. The stated audience is an AWS-registered ISV data accessor, with a separate enterprise account.
- The Windows configuration sets the client type to stdio. The repository LICENSE is Apache License 2.0, and the root README says Apache-2.0.

### Not established by this review

 - The resource was not executed.
- The server was not started and no tool was called.
- OIDC login, token creation, and role assumption were not performed.
- A pin does not verify transitive dependencies.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-qindex-mcp-server/README.md)

DOCUMENTED COMMAND

 pip install -e . Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - The README shows git clone with a placeholder repository URL, then a change into src/amazon-qindex-mcp-server.
- The unindented install line is pip install -e ., which installs that cloned directory in editable mode rather than the published uvx package.
- The Windows block and the install badges name awslabs.amazon-qindex-mcp-server@latest. Those package lines are indented or percent-encoded, so they are not the recorded command.

### Before you start

 - uv and Python 3.10, as the prerequisites section states
- Two AWS accounts, a registered ISV data accessor, IAM Identity Center, and an Amazon Q Business application that uses IAM Identity Center

### Compatibility

Kiro · Cursor · VS Code · Windows · Python 3.10 with uv

### Implementation

Python

### Transports

stdio

### ISV data accessor, OIDC then assumed role

 - Builds an authorization URL and, after a pasted code, creates a token and temporary credentials used for SearchRelevantContent.
- Does not document creating an IAM user, role, policy, or access key. The role ARN is supplied by the operator.

### Cost model

Apache-2.0. Amazon Q Business and IAM Identity Center charges are separate. No call was made.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Amazon Q Index MCP README ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-qindex-mcp-server/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/amazon-qindex-mcp-server/README.md Supports: OIDC state, pasted authorization code, assumed role, search cap, and the editable install line
- [Repository README ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md Supports: Apache-2.0 statement and the Q index row for registered data accessors
- [Repository LICENSE ↗](https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE) Checked 2026-10-14 https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE Supports: Apache License 2.0

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Dropbox Dash MCP ↗ Searches Dash-connected sources and retrieves documents, visual pages or source-native search results for an assistant.](/mcp-servers/dropbox-dash/)[### Algolia MCP Server ↗ Algolia's managed MCP offerings: Public MCP exposes application-scoped search and recommendations on selected indices for customer-facing agents; Productivity MCP gives user-scoped, read-only exploration and analytics; DevEx MCP serves version-matched API client snippets to coding agents without touching data.](/mcp-servers/algolia/)[### Bright Data MCP Server ↗ Search-engine results, page scraping, pre-built structured-data scrapers and a remote browser through Bright Data's proxy infrastructure, from a hosted URL or a local npx package.](/mcp-servers/brightdata/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
