AWS Notebook Runner MCP
Related Servers
Alternatives to AWS Notebook Runner MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables LLMs to create, destroy, and manage AWS EC2 instances, including running commands via interactive shells.1-
- FlicenseNot gradedqualityAmaintenanceEnables users to query AWS cost and usage data, audit for wasted resources like stopped EC2 instances and unattached EBS volumes, and monitor budgets across multiple accounts and regions using natural language. Runs locally against existing AWS CLI profiles so credentials never leave the machine.-
- FlicenseNot gradedqualityAmaintenanceEnables users to query AWS cost and usage data, run waste and savings audits, monitor budgets, and compare multiple accounts or regions through natural-language prompts while keeping credentials local.-
- FlicenseNot gradedqualityBmaintenanceEnables querying AWS cost and usage data, monitoring budgets, and auditing for waste such as stopped EC2 instances, unattached EBS volumes, and unassociated Elastic IPs through natural language across multiple AWS profiles and regions. Runs locally using existing AWS CLI credentials to keep them secure.-
- FlicenseNot gradedqualityAmaintenanceEnables users to query AWS cost and usage data, audit for wasted resources like idle EC2 instances and unattached volumes, and check budget status using natural language across multiple profiles and regions. It runs locally against existing AWS CLI credentials, so no keys leave the user's machine.-
- FlicenseNot gradedqualityAmaintenanceEnables users to analyze AWS cloud costs, audit for waste such as unused resources, and monitor budgets using natural language, while keeping AWS credentials on their local machine.-
TDQS
Scored across 13 tools
Each tool targets a distinct action (plan, start, check status, inspect, estimate) for separate AWS execution paths (EC2+SSM vs SageMaker), with clear descriptions that prevent confusion even between start_ec2_smoke_run and start_ec2_smoke_run_async.
All tool names follow a verb_noun pattern in snake_case consistently, using action verbs like check, estimate, explain, get, inspect, plan, start. No mixed conventions.
13 tools cover the full workflow for two execution modes without bloat. Each tool serves a clear purpose in the lifecycle (plan, start, status, cost, setup, inspection).
The tool set covers setup checks, planning, starting (sync and async for EC2), status retrieval, cost estimation, and notebook inspection. Missing a cancel/abort tool for running jobs, but the guarded design mitigates this gap.