๐—ฆ๐˜๐—ผ๐—ฝ ๐—ฃ๐˜‚๐˜๐˜๐—ถ๐—ป๐—ด ๐—”๐—ฃ๐—œ ๐—ž๐—ฒ๐˜†๐˜€ ๐—ถ๐—ป ๐—บ๐—ฐ๐—ฝ.๐—ท๐˜€๐—ผ๐—ป

Teams often share one API key for AI tools. This is a security risk. One leak ruins everything. You also lose your audit trail. You do not know who ran which prompt.

Many vendors lack OAuth. Internal tools are worse. They rely on one shared secret.

You need a front door for your APIs. Use this stack to fix it:

The secret stays on the server. It never reaches the user laptop.

Stop using stdio transport. Stdio puts secrets in your config files. Switch to http transport. Your config file now only needs a URL. No secrets to leak.

This setup is serverless. It costs almost nothing. You get per-user logs. Revoke access in seconds.

Source: https://dev.to/aws-builders/stop-putting-api-keys-in-mcpjson-per-user-oauth-with-amazon-cognito-aws-lambda-4h2i

Optional learning community: https://t.me/GyaanSetuAi