Skip to main content
Glama
RadiumGu

AWS FIS MCP Server

by RadiumGu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AWS FIS MCP Server

No user-submitted related servers found.

    Related Servers

    • FIS Recommender MCP Server

      pimisael
      A
      license
      Not graded
      quality
      B
      maintenance
      Analyzes DevOps findings to automatically recommend and generate AWS Fault Injection Simulator (FIS) experiment templates. It helps teams validate system resilience by mapping reported issues to specific chaos engineering actions across AWS services.
      MIT

    • permission-aware-mcp

      TanvirIslam-BD
      F
      license
      A
      quality
      D
      maintenance
      Enables secure file system operations (read, write, delete) and simulated command execution with server-enforced permission policies, risk assessment, and human-in-the-loop approval.
      5
      -

    • Cloud Operations Runbook

      skmahe1077
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables cloud and platform engineers to investigate AWS incidents by grounding responses in approved runbooks and operational evidence, with authenticated access, citations, observability, and human approval before any write action.
      MIT

    • MCP Operations Server

      ivanfdz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to operations and telemetry data across 12 domains through 45 agent tools, including asset inventory, metrics, outages, incidents, and platform settings, with support for AWS SigV4-signed live access and a fixture-based mock mode that runs without a backend.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific AWS FIS operations with no overlap. Tools like create_experiment_template, delete_experiment_template, and get_experiment_template handle different lifecycle stages of templates, while start_experiment and stop_experiment manage experiment execution separately. The list_* tools provide distinct listing functions for different resource types.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case throughout. The naming convention is perfectly predictable: create_experiment_template, delete_experiment_template, get_experiment, list_experiments, start_experiment, stop_experiment, etc. This consistency makes the tool set immediately understandable and navigable.

    Tool Count5/5

    With 10 tools, this server is well-scoped for AWS FIS operations. Each tool earns its place by covering essential CRUD operations for experiment templates (create, delete, get, list), experiment management (start, stop, get, list), plus supporting utilities like list_action_types and generate_template_example. This provides comprehensive coverage without being overwhelming.

    Completeness5/5

    The tool set provides complete lifecycle coverage for AWS FIS operations. It includes full CRUD for experiment templates (create, get, list, delete), experiment execution (start, stop, get, list), plus discovery tools (list_action_types) and a helpful utility (generate_template_example). There are no obvious gaps - agents can create templates, run experiments, monitor them, and clean up resources as needed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources