Acts as a proxy for Amazon's MCP server, providing managed access to Amazon tools with capabilities for authentication, token management, and subscription-based tool filtering.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Geenie MCP Proxy Serverlist the available Amazon tools for my account"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Geenie MCP Proxy Server
The Geenie MCP proxy server sits between Claude Desktop and Amazon's MCP server, handling authentication, token management, and subscription-based tool filtering.
Quick Start
1. Install Dependencies
2. Set Up Environment
Copy .env.example to .env and fill in your credentials:
For local development, the mock Amazon MCP server endpoints are pre-configured.
3. Run the Servers
You'll need two terminal windows:
Terminal 1 - Mock Amazon MCP Server:
Terminal 2 - Geenie Proxy Server:
The mock server runs on port 9000, and the proxy runs on port 3000.
4. Test the Health Check
5. Test the MCP Proxy
You should see a list of tools returned from the mock Amazon server.
Project Structure
Development Phases
✅ Phase 1: Basic Proxy (Current)
Project setup with TypeScript
Fastify server with CORS
Health check endpoint
Basic MCP proxy route
Mock Amazon MCP server
⏳ Phase 2: Authentication (Next)
API key validation middleware
Subscription status checking
Supabase integration
Caching layer
⏳ Phase 3: Token Management
Amazon token refresh logic
Multi-account handling
Token expiry checks
⏳ Phase 4: Tool Filtering
Subscription tier restrictions
Global tool blacklist
Disabled tools injection
⏳ Phase 5: Production Ready
Token encryption
Rate limiting
Error handling improvements
Railway deployment
Available Scripts
npm run dev- Start proxy server with hot reloadnpm run dev:mock- Start mock Amazon MCP servernpm run build- Compile TypeScript to JavaScriptnpm start- Run production buildnpm test- Run tests (coming soon)
Environment Variables
See .env.example for all available configuration options.
Testing
Currently using a mock Amazon MCP server that simulates:
tools/list- Returns available MCP toolstools/call- Simulates tool execution with mock data
Next Steps
Add API key validation (Phase 2)
Integrate with Supabase for user/subscription data
Implement Amazon token refresh logic
Add subscription-based tool filtering
Deploy to Railway
License
MIT