Shiped MCP
Official# Shiped MCP
The stdio MCP server for Shiped. It lets MCP-compatible agents deploy and manage projects on `https://shiped.app`.
## Usage
Add Shiped to an MCP-compatible client:
```json
{
"mcpServers": {
"shiped": { "command": "npx", "args": ["-y", "@shiped/mcp"] }
}
}
```
The first tool call opens a device-flow login. For explicit login, run:
```bash
npx @shiped/mcp login
npx @shiped/mcp logout
```
`login` connects the current agent to Shiped. `logout` clears the cached local token.
## Development
```bash
npm ci
npm run build
```
The Docker image runs the server over stdio and can be used for MCP introspection or local container-based clients.
## Publish
```bash
npm login
npm publish
```
[](https://aiagentslisting.com/mcp/shiped-mcp)
TDQS
Scored across 3 tools
Each tool handles a distinct operation: deploy creates a new deployment, list reads all projects, and delete removes one. There is no overlap or chance of confusing one tool with another.
Most tools follow a verb_noun pattern like list_shiped_projects and delete_shiped_project, but deploy_to_shiped uses a different verb + preposition format. The names remain predictable and readable despite the minor inconsistency.
With 3 tools, the server is tightly scoped to core deployment lifecycle operations. The count is well-suited for the simple hosting domain.
The set covers deploy, list, and delete, which are the essential operations for a deployment service. An explicit single-project fetch or update/redeploy operation could improve completeness, but the current surface has no major gaps.