Skip to main content
Glama
Sign In
AFSIM MCP Server

AFSIM MCP Server

by Yookio-Z
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AFSIM MCP Server

No user-submitted related servers found.

    Related Servers

    • CMO Agent Bridge

      Nuclear2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to read and control Command: Modern Operations scenarios locally via MCP tools, supporting real-time battle assessment, task planning, and scenario editing.
      10
      MIT

    • STK-MCP

      alti3
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables Large Language Models or other MCP clients to interact with Ansys/AGI STK (Systems Tool Kit), allowing users to control STK Desktop simulations programmatically or via natural language.
      42
      -

    • Ollama MCP Server

      claudiayoung104
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible applications to interact with local and cloud-hosted LLM models for model management, text generation, chat, embeddings, and web search/fetch.
      897 npm
      AGPL 3.0

    • agent-control

      loulanyue
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.
      189
      Apache 2.0
    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.8/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: scenario, platform, component, simulation, results, or configuration. Even closely related tools like run_simulation, run_warlock, run_mission are clearly differentiated by their specific AFSIM binary and purpose. No two tools overlap in functionality.

    Naming Consistency5/5

    All tools follow a verb_noun naming pattern (e.g., create_scenario, list_platforms, run_simulation). Verbs are descriptive and consistent (create, delete, list, get, set, run, query, etc.). Even longer names like export_results_to_json maintain the pattern with additional qualifiers.

    Tool Count3/5

    With 37 tools, the server is above the typical range but still appropriate for the complex AFSIM domain. Each tool serves a specific need across scenario creation, platform management, simulation execution, and result analysis. The count is high but not excessive given the breadth of functionality.

    Completeness5/5

    The tool set covers the full lifecycle: scenario CRUD, platform and component management, simulation execution (multiple binaries), result querying/export, and configuration. There are no critical gaps; all major operations for managing AFSIM simulations are represented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources