RAG endpoints for AWS Documentation

[artcerna]

Is this related to an existing feature request or issue?

aws-documentation-mcp-server: https://github.com/awslabs/mcp/blob/main/src/aws-documentation-mcp-server/awslabs/aws_documentation_mcp_server

Summary

Currently, the aws-documentation_mcp_server usese the AWS Docs Search Endpoint. The ask here is to migrate to a new endpoint that uses a Retrieval-Augmented Generation model(RAG) instead of the current AWS Docs Search

Use case

• Better integration with Agentic workflows
• Allows for the addition of features that allow more control to agentic models on what parameters they can use to tweak results based on use case

Proposal

This change should be simply be changing the Search API endpoint to use an existing RAG endpoint. Details on this RAG endpoint should be already implemented/out of scope

Out of scope

Creation/Maintenance of the RAG backend we will use. This change should solely focus on updating the endpoint to use the new API

Potential challenges

Changing endpoints would require some work to ensure the new endpoint works as expected and does not introduce any regressions for the server itself.

Dependencies and Integrations

This change should change dependencies from the AWS Docs Search Endpoint to a new endpoint

Alternative solutions

[theagenticguy]

@tuanknguyen does this endpoint exist? Thoughts?

[tuanknguyen]

I'm not 100% sure which endpoint is referenced here. I'll double check and get back.

Better integration with Agentic workflows

Could you clarify how you're using agentic workflows with the AWS Documentation MCP server?

Allows for the addition of features that allow more control to agentic models on what parameters they can use to tweak results based on use case

Model selection and parameters sound like something you adjust at the client-level, and is not an MCP server setting.

Since RAG is just search + LLM, which your agent client already has that capability anyway. I'm not sure introducing another layer of LLM between the search result and the agent will improve the experience. Would love to get some concrete example of your use case.

[sidharthgulati1412]

Could you clarify how you're using agentic workflows with the AWS Documentation MCP server?

Maybe I can clarify. There is no agentic workflow. The idea is the new endpoint is tailor made for LLM context use case which motivates the statement.

Would love to get some concrete example of your use case.

So the use case is to use a Search API that is tailor made for the LLM use case.

[theagenticguy]

Converted to a discussion. This isn't really an issue or RFC that can be implemented in this project itself.