MCP-SST
Allows for streaming SST dev logs and controlling the SST dev process, including starting, stopping, and restarting the dev environment, as well as monitoring deployment status and Lambda invocations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP-SST show me the latest logs from the dev process"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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/projectRelated 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 |
| List available log tabs |
| Read last N lines from a log tab |
| Get deployment status |
| Get Lambda invocations |
| Get event stream |
| Start SST dev |
| Stop SST dev |
| Restart SST dev |
| 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/projectLicense
MIT
Available Tools
6 toolssst_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
Scored across 6 tools
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.
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.
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.
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
Related MCP Connectors
Model Context Protocol server for Studex tools, notifications, and profile integrations
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Develop, manage, and debug Railway projects, services, and deployments from within agents.
Manage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA 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.-
- AlicenseBqualityNot gradedmaintenanceEnables 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.31MIT
- AlicenseCqualityDmaintenanceEnables 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.1635 npmMIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server integrating DevOps tools for GitHub, Docker, and filesystem operations.9MIT