flask

This MCP server integrates a Flask-based application with an AWS Cost Optimizer to provide real-time cost analytics, route discovery, health monitoring, and Claude AI-driven control for the Flask app. The server exposes a suite of tools to manage, test, and observe the Flask application alongside AWS resource usage. Use the AWS-enabled endpoints to monitor costs, deploy optimizations, and validate route behavior. The included Claude Desktop integration allows you to control the Flask app via natural language commands and automated workflows.

Key capabilities include starting and stopping the Flask app, checking its health, listing all accessible routes, testing individual endpoints, and retrieving application logs. The AWS cost optimizer component provides live cost tracking, resource monitoring across EC2, S3, and EBS, and recommendations for optimization. The Claude integration enables you to issue high-level commands to deploy changes, fetch metrics, and apply AI-driven optimization suggestions within the Flask environment.

Prerequisites:

• Python 3.8+ and virtual environment tooling (venv or virtualenv)
• Access to the repository with the Flask MCP server implementation
• AWS credentials configured (via AWS CLI or environment variables) with permissions to read cost and resource data

Step-by-step installation:

1. Clone the repository: git clone <repository-url> flask-mcp-server cd flask-mcp-server

2. Create and activate a virtual environment: python -m venv venv source venv/bin/activate # On Windows use: venv\Scripts\activate

3. Install dependencies: if you have a requirements.txt at the project root, run: pip install -r requirements.txt

4. Configure environment variables (example):

   • FLASK_APP_PATH=/path/to/your/flask/app
   • AWS_REGION=us-west-2
   • FLASK_HOST=127.0.0.1
   • FLASK_PORT=5000

5. Run the MCP server utilities to start the Flask MCP server: python start_flask.py

6. Verify the server is running and accessible, then use the available tools (start-flask-app, stop-flask-app, check-flask-status, etc.) to manage the Flask application and AWS cost optimizer integration.

Tips and tips:

• Ensure AWS credentials are configured and have permissions to access cost and resource data for accurate optimization.
• The environment variable AWS_REGION should match the region where your resources are monitored.
• If the Flask app uses a specific port or host, update FLASK_HOST and FLASK_PORT accordingly.
• When deploying, verify that the Claude Desktop config references the correct path to flask_app_mcp.py and includes necessary environment variables.
• Common issues: mismatched Python version, missing dependencies in requirements.txt, or incorrect paths to the Flask app. Check logs via get-flask-logs for troubleshooting.
• For production, consider securing access to the MCP endpoints and implementing proper IAM roles for AWS access.