This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Deploy and manage TurboSteed sites from your terminal or CI/CD pipeline.
Deploy sites with a single command
Manage assets (upload, list, delete)
Retrieve contact form submissions
Manage CMS schemas and entries
Progress indicators and formatted output
Works with GitHub Actions, GitLab CI, and Bitbucket Pipelines
MCP server for Claude Code / Claude Desktop integration
Related MCP server: Novence MCP
Node.js 18.0.0 or higher
A TurboSteed account (sign up)
npm install -g @turbosteed/cliVerify installation:
turbosteed --versionnpm install --save-dev @turbosteed/cliRun via npx:
npx turbosteed deployOr add to package.json scripts:
{
"scripts": {
"deploy": "turbosteed deploy --source ./dist"
}
}Log in to the TurboSteed Dashboard
Navigate to Settings > API Keys
Copy your Account SID and API Key
Navigate to your site and copy the Site ID
export TURBOSTEED_ACCOUNT_SID="your-account-sid"
export TURBOSTEED_API_KEY="your-api-key"
export TURBOSTEED_SITE_ID="your-site-id"For permanent setup, add these to your shell profile (~/.bashrc, ~/.zshrc, etc.).
Create turbosteed.json in your project root:
{
"version": "1",
"site": {
"id": "your-site-id",
"accountSid": "your-account-sid"
},
"deploy": {
"source": "./dist",
"exclude": ["**/*.map", ".DS_Store"]
}
}Note: Never put your API key in config files. Always use environment variables for secrets.
Variable | Required | Description |
| Yes | Your account identifier |
| Yes | Your API key (keep secret) |
| Yes* | Site ID (*can be in config file) |
| No | API base URL (defaults to production) |
# Deploy from ./dist (default)
turbosteed deploy
# Deploy from a specific directory
turbosteed deploy --source ./build
# Preview what would be deployed
turbosteed deploy --dry-run
# Output result as JSON
turbosteed deploy --jsonRequirements:
Source directory must contain an index.html file
Maximum zip size: 25 MB
# Upload a file
turbosteed assets upload ./images/logo.png
# List first page of assets
turbosteed assets list
# List ALL assets (automatic pagination)
turbosteed assets list --all
# Manual pagination (next page)
turbosteed assets list --page <token>
# Delete an asset
turbosteed assets delete logo.png# List first page of submissions
turbosteed forms list
# List ALL submissions (automatic pagination)
turbosteed forms list --all
# Manual pagination (next page)
turbosteed forms list --page <formId>
# Get a specific submission
turbosteed forms get <formId># List first page of schemas
turbosteed cms schema list
# List ALL schemas (automatic pagination)
turbosteed cms schema list --all
# Create a schema from JSON file
turbosteed cms schema create ./blog-schema.json
# List first page of entries in a schema
turbosteed cms entry list <schemaId>
# List ALL entries (automatic pagination)
turbosteed cms entry list <schemaId> --all
# Create an entry
turbosteed cms entry create <schemaId> ./post.json
# Publish an entry
turbosteed cms entry publish <schemaId> <entryId>Example schema file (blog-schema.json):
{
"display_name": "Blog Posts",
"schema_mode": "custom",
"fields": [
{ "name": "title", "type": "text", "required": true, "max_length": 200 },
{ "name": "slug", "type": "slug", "source_field": "title", "required": true },
{ "name": "body", "type": "richtext", "required": true },
{ "name": "published_date", "type": "date", "required": false }
]
}Example entry file (post.json):
{
"title": "My First Post",
"slug": "my-first-post",
"body": "# Hello World\n\nThis is my first blog post.",
"published_date": "2026-07-01"
}Create .github/workflows/deploy.yml:
name: Deploy to TurboSteed
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install and Build
run: npm ci && npm run build
- name: Deploy to TurboSteed
env:
TURBOSTEED_ACCOUNT_SID: ${{ secrets.TURBOSTEED_ACCOUNT_SID }}
TURBOSTEED_API_KEY: ${{ secrets.TURBOSTEED_API_KEY }}
TURBOSTEED_SITE_ID: ${{ secrets.TURBOSTEED_SITE_ID }}
run: npx @turbosteed/cli deploy --source ./distCreate .gitlab-ci.yml:
stages:
- build
- deploy
build:
stage: build
image: node:20
script:
- npm ci
- npm run build
artifacts:
paths:
- dist/
deploy:
stage: deploy
image: node:20
dependencies:
- build
script:
- npx @turbosteed/cli deploy --source ./dist
only:
- mainCreate bitbucket-pipelines.yml:
image: node:20
pipelines:
branches:
main:
- step:
name: Build
caches:
- node
script:
- npm ci
- npm run build
artifacts:
- dist/**
- step:
name: Deploy to TurboSteed
deployment: production
script:
- npx @turbosteed/cli deploy --source ./distThis CLI includes an MCP (Model Context Protocol) server that allows AI assistants like Claude to manage your TurboSteed site programmatically.
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"turbosteed": {
"command": "npx",
"args": ["@turbosteed/cli", "--mcp"],
"env": {
"TURBOSTEED_ACCOUNT_SID": "your-account-sid",
"TURBOSTEED_API_KEY": "your-api-key",
"TURBOSTEED_SITE_ID": "your-site-id",
"TURBOSTEED_API_BASE": "https://api-us.turbosteed.com"
}
}
}
}For Claude Code, add to ~/.claude/settings.json:
{
"mcpServers": {
"turbosteed": {
"command": "npx",
"args": ["@turbosteed/cli", "--mcp"],
"env": {
"TURBOSTEED_ACCOUNT_SID": "your-account-sid",
"TURBOSTEED_API_KEY": "your-api-key",
"TURBOSTEED_SITE_ID": "your-site-id",
"TURBOSTEED_API_BASE": "https://api-us.turbosteed.com"
}
}
}
}You can also start the MCP server directly from the command line:
turbosteed --mcpOr via npx:
npx @turbosteed/cli --mcpVariable | Required | Description |
| Yes | Account identifier (e.g., |
| Yes | API key (e.g., |
| Yes | Site identifier (e.g., |
| No | API base URL ( |
The CLI runs a local stdio MCP server that proxies all requests to the TurboSteed backend MCP HTTP endpoint at ${TURBOSTEED_API_BASE}/users/${accountSid}/sites/${siteId}/mcp. It receives MCP protocol messages over stdio from Claude, forwards them via HTTP to the backend, and returns responses back through stdio.
Once configured, Claude can use these tools:
Tool | Description |
| Get site configuration |
| Update site settings |
| List CMS schemas |
| Get a schema definition |
| Create a new schema |
| List entries in a schema |
| Get a specific entry |
| Create a new entry |
| Update an entry |
| Publish an entry |
| List webhooks |
| Create a webhook |
| List contact form submissions |
| Get a specific submission |
| List all assets |
| Delete an asset |
| Get a pre-signed upload URL |
| Trigger deployment |
| Get public site credentials for RAG/widget |
Ask Claude:
"List all my CMS schemas"
"Create a new blog post entry with title 'Hello World'"
"Show me my site configuration"
"What contact form submissions do I have?"
Code | Meaning |
0 | Success |
1 | General error |
2 | Authentication failure |
3 | Resource not found |
4 | Upload/network failure |
5 | Invalid input |
6 | Configuration error |
For environments without Node.js, use shell scripts:
curl -sSL https://raw.githubusercontent.com/turbosteed/shell-tools/main/scripts/deploy.sh | bash -s ./distSee github.com/turbosteed/shell-tools
This software is licensed for use with TurboSteed accounts only. See LICENSE for full terms.
This server cannot be deployed
Hosted MCP for creating, checking, deploying, and hosting static sites for AI agents.
Build, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Build, edit, host, and publish websites from AI assistants. Setup: https://mcp.orivox.org/
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
