Skip to main content
Glama
YummyTastyCode

AWS Notebook Runner MCP

Related Servers

Alternatives to AWS Notebook Runner MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to safely read, edit, and execute local Jupyter notebooks without running a separate service. Edits are guarded by compare-and-swap hashes and execution resumes or replays kernel state, so long-running cells aren't needlessly re-run.
      6
      0
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables creating AWS cost estimates through natural language, generating shareable calculator.aws links, and retrieving actual calculated costs via headless Chrome, without requiring AWS credentials.
      99 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to AWS infrastructure through AWS IAM Identity Center for secure, natural language management of cloud resources across multiple accounts. It enables users to execute AWS CLI commands, monitor resources, and run remote shell commands on EC2 instances via Systems Manager.
      398 npm
      15
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language analysis of AWS costs, automated FinOps waste audits, and budget monitoring across multiple profiles and regions while keeping credentials secure locally.
      29 PyPI
      183
      MIT

    TDQS

    B3.3/5.0

    Scored across 13 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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).

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues