nexterm-mcp
Related Servers
Alternatives to nexterm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP 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.30MIT
- FlicenseAqualityBmaintenanceMCP server for the Gripp API, enabling CRUD operations on Gripp entities with built-in confirmation safety for mutations.91-
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
- AlicenseAqualityDmaintenanceMCP server for creating, listing, updating, deleting memos, and managing attachments via the Memos API.1223 npmMIT
- FlicenseCqualityCmaintenanceA 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-
- FlicenseNot gradedqualityDmaintenanceA minimal, containerized MCP server that exposes a Streamable HTTP transport with API key authentication, allowing secure access to MCP endpoints.-
TDQS
Scored across 89 tools
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.
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.
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.
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.