Skip to main content
Glama
shanewwarren

MCP-SST

by shanewwarren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP-SST

No user-submitted related servers found.

    Related Servers

    • Koyeb MCP Server

      samihalawa
      A
      license
      C
      quality
      D
      maintenance
      Enables programmatic management of Koyeb resources including apps, services, deployments, and instances via the Model Context Protocol. It allows users to query build and runtime logs and perform resource lifecycle operations through the Koyeb API.
      16
      63 npm
      MIT

    • devir

      Davidkata1234
      A
      license
      Not graded
      quality
      C
      maintenance
      A command-line interface and MCP server for managing and monitoring multiple development services through a unified terminal UI. It enables users to interact with service logs, filter messages, and control development environments directly via Model Context Protocol integration.
      -

    • DuploCloud Docker MCP Server

      robford-brookai
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables comprehensive management of DuploCloud infrastructure, including tenants, services, hosts, databases, and storage. It provides tools for lifecycle operations on cloud resources like ECS tasks and S3 buckets through the Model Context Protocol.
      31
      MIT

    • procm-mcp

      hunmer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely create, manage, and monitor local processes such as dev servers, docker-compose, and test watchers, including restarting, checking status, and retrieving logs via MCP, HTTP, or WebSocket messaging.
      33 npm
      1
      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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting different aspects of SST dev monitoring: discovery, events, invocations, status, log tabs, and log reading. There is no overlap or ambiguity between tools.

    Naming Consistency5/5

    All tools follow a perfect 'sst_verb_noun' pattern with consistent snake_case naming. The verb choices (discover, get, list, read) are appropriate and uniformly applied.

    Tool Count5/5

    With 6 tools, this is well-scoped for monitoring SST dev servers. Each tool serves a specific monitoring function, and the count is neither too sparse nor excessive for the domain.

    Completeness4/5

    The toolset provides comprehensive coverage for monitoring SST dev environments, including discovery, status, events, invocations, and logs. A minor gap is the lack of tools for controlling or interacting with the servers (e.g., restarting or deploying), but the monitoring surface is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources