Skip to main content
Glama

Related Servers

Alternatives to nexterm-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server for interacting with a self-hosted Appsmith instance via its REST API, enabling read/update/create of pages, queries, JS objects, widgets, datasources, and applications with lazy session management and destructive-operation gating.
      30
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      MCP server for the Gripp API, enabling CRUD operations on Gripp entities with built-in confirmation safety for mutations.
      9
      1
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for creating, listing, updating, deleting memos, and managing attachments via the Memos API.
      12
      23 npm
      MIT
    • F
      license
      C
      quality
      C
      maintenance
      A production-ready MCP server for inventory and interaction with Alterios/LIMS instances, enabling project listing, readonly data queries via REST and script-services, and controlled write operations.
      100
      -

    TDQS

    C2.7/5.0

    Scored across 89 tools

    Disambiguation3/5

    Most tools target a distinct resource and action, but the large surface creates real overlap among list variants such as list_scripts/list_all_scripts/list_script_sources and list_snippets/list_snippet_sources. Theme CSS and source/snippet source terminology can also be confused without careful reading.

    Naming Consistency5/5

    Every tool uses the nexterm_ prefix followed by a predictable verb_noun pattern: list_*, get_*, create_*, update_*, delete_*, sync_*, etc. The convention is consistently applied across all domains.

    Tool Count1/5

    89 tools is far beyond a well-scoped MCP surface, even for a broad server-management platform. The toolset is split across many domains, but the count is extreme and makes discovery and selection cumbersome.

    Completeness3/5

    Core domains like entries, folders, tags, organizations, scripts, snippets, themes, sources, monitoring, audit, and backups have substantial coverage. However, notable lifecycle gaps remain for identities, integrations, organization members/invitations, and engines, several of which are read-only or partially exposed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues