aerostack mcp
Convert any NPM/stdio MCP server into a Cloudflare Worker and deploy it to Aerostack. Once deployed, your MCP server is accessible over HTTP from any LLM tool.
Usage
aerostack mcp convert [flags]Exactly one source flag is required.
Flags
| Flag | Description |
|---|---|
--package <name> | NPM package name (e.g., @notionhq/notion-mcp-server) |
--github <url> | GitHub repository URL |
--dir <path> | Local directory path |
-o, --output | Output directory (default: .) |
--slug | Server slug for deployment (auto-derived from package name) |
--deploy | Deploy to Aerostack after conversion |
Examples
# Convert from NPM package
aerostack mcp convert --package @notionhq/notion-mcp-server
# Convert and deploy immediately
aerostack mcp convert --package @notionhq/notion-mcp-server --deploy --slug notion-mcp
# Convert from GitHub
aerostack mcp convert --github https://github.com/user/my-mcp-server
# Convert from local directory
aerostack mcp convert --dir ./my-mcp-server --slug my-mcpWhat it does
- Downloads or clones the MCP server source
- Analyzes MCP tool definitions
- Detects required environment variables
- Generates a Cloudflare Worker wrapper
- Flags any incompatible Node.js APIs
- Optionally deploys to Aerostack
After conversion
# The generated output contains:
my-mcp-worker/
├── src/index.ts # Worker wrapper
├── aerostack.toml # Project config
└── package.jsonDeploy manually:
cd my-mcp-worker
aerostack deploy mcp dist/index.js --slug my-notion-mcpAfter deployment, your MCP server is available at a workers.dev subdomain and can be used in Aerostack workspaces. See Deploy an MCP Server for the full workflow.