Hey everyone! We've developed a Knowledge Base that integrates the latest AWS documentation and stores all that information in a vector database. This allows our users to access up-to-date AWS insights. Recently, I came across the AWS MCP server, and I'm wondering if adopting it would render our vector database obsolete. Since our primary goal is to share the latest knowledge from AWS, I've been concerned about the rising costs of our weekly scraping process. What do you all think?
5 Answers
You might want to consider using the MCP for periodic updates to check for any knowledge gaps. It could complement your existing tool if it's set up correctly.
Sounds like it could be time to reevaluate things. Maybe test some scenarios to see how both options stack up?
Honestly, you're kind of hinting at the answer yourself. If there's already an official MCP tool from AWS, what incentive would users have to stick with your solution? What unique value does it provide?
If your solution isn't highly specialized, it might be a good idea to switch to the MCP. AWS is likely to keep their tools more up-to-date than what you can manage on your own. But is your database specifically for end-users or for the MCP server?
Exactly, and also keep in mind that the official MCP is free whereas your service might come with costs. That might push users away too.
Related Questions
How to Build a Custom GPT Journalist That Posts Directly to WordPress
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads