← Explore all 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.

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

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.

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 ↗

DOCUMENTED COMMAND

pip install -e .

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

  1. The README shows git clone with a placeholder repository URL, then a change into src/amazon-qindex-mcp-server.
  2. The unindented install line is pip install -e ., which installs that cloned directory in editable mode rather than the published uvx package.
  3. 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

04 / FOLLOW THE EVIDENCE

The source trail.

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

  1. 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

  2. Repository README ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md

    Supports: Apache-2.0 statement and the Q index row for registered data accessors

  3. Repository LICENSE ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE

    Supports: Apache License 2.0

Evidence & Ask