Skip to main content
Glama

MCP-SST

MCP server for streaming SST dev logs and controlling the SST dev process.

Quick Start

Add to Claude Code:

claude mcp add sst -- npx github:shanewwarren/mcp-sst /path/to/your/sst/project

Related MCP server: DuploCloud Docker MCP Server

Alternative: Manual Configuration

Add to ~/.claude/mcp.json (or .claude/mcp.json in your project):

{
  "mcpServers": {
    "sst": {
      "command": "npx",
      "args": [
        "github:shanewwarren/mcp-sst",
        "/path/to/your/sst/project"
      ]
    }
  }
}

Available Tools

Tool

Description

sst_list_tabs

List available log tabs

sst_read_logs

Read last N lines from a log tab

sst_get_status

Get deployment status

sst_get_invocations

Get Lambda invocations

sst_get_events

Get event stream

sst_start

Start SST dev

sst_stop

Stop SST dev

sst_restart

Restart SST dev

sst_process_status

Get process status

Development

git clone https://github.com/shanewwarren/mcp-sst.git
cd mcp-sst
npm install
npm run build
npm start /path/to/sst/project

License

MIT

Available Tools

6 tools
sst_discoverC

Discover running SST dev servers and available stages.

Inputs: directory.

sst_get_eventsC

Get recent events from the SST dev event stream.

Inputs: timeoutMs, eventType.

sst_get_invocationsC

Get recent Lambda function invocations from SST dev.

Inputs: timeoutMs.

sst_get_statusB

Get current deployment status and resources from SST dev.

Inputs: stage.

sst_list_tabsB

List all available log tabs/files from SST dev.

Inputs: stage.

sst_read_logsC

Read the last N lines from a specific SST dev log tab.

Inputs: tab (required), lines, offset.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • 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.
      -
    • 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
    • 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
      35 npm
      MIT