Skip to main content
Glama
README.md
# MCP-SST

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

## Quick Start

Add to Claude Code:

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

## Alternative: Manual Configuration

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

```json
{
  "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

```bash
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

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