Skip to main content
Glama
sueinchoi

nonmem-mcp-server

by sueinchoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to nonmem-mcp-server

No user-submitted related servers found.

    Related Servers

    • relative-interpreter-mcp

      CalWtr
      F
      license
      B
      quality
      C
      maintenance
      An MCP server that enables LLMs to act as an interpreter for the Relative service, providing tools for navigating, reading, editing, executing, and managing models through natural language.
      20
      -

    • ChemLint

      molML
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives LLMs native access to cheminformatics and molecular ML tools, enabling molecular structure manipulation, descriptor calculation, ML model training, and analysis report generation through natural conversation.
      34
      MIT
    • Ansys CFX-MCP by ansys

      Ansys CFX-MCPofficial

      ansys
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI assistants to interact with Ansys CFX through PyCFX, supporting natural-language-assisted CFX-Pre, CFX Solver, and CFD-Post workflows for setup, execution, and postprocessing.
      7
      1,597 PyPI
      1
      Apache 2.0

    • comsol-codex-mcp

      XiaoSe532
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for reproducible COMSOL Multiphysics batch workflows, enabling AI agents to compile, run, and diagnose Java API model scripts with COMSOL.
      4
      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.6/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, such as 'cancel_run' for job cancellation versus 'submit_run' for job submission. However, some overlap exists, like 'check_run_status' and 'list_runs' both providing run status information, which could cause mild confusion in selection.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as 'cancel_run', 'check_nonmem_setup', and 'parse_control_stream'. There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count3/5

    With 22 tools, the count is borderline high for a NONMEM-focused server, potentially feeling heavy. While many tools are specialized for tasks like diagnostics and parsing, the number might overwhelm agents, though it aligns with the comprehensive scope of NONMEM modeling workflows.

    Completeness5/5

    The tool surface provides complete coverage for NONMEM modeling, including setup checks, job submission, status monitoring, result parsing, diagnostics, and simulation. There are no obvious gaps, supporting full lifecycle management from data input to analysis and visualization.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources