Provision Stack MCP
# Provision Stack MCP
Cloud infrastructure provisioning via natural language. Deploy production-ready infrastructure on your own AWS, GCP, Azure, or Oracle account with a single prompt.
## Quick Start
### Remote (recommended)
Point your MCP client directly at the hosted API — no local process needed:
```json
{
"mcpServers": {
"provision-stack": {
"url": "https://api.provision-stack.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
}
}
}
}
```
Get a token: `curl -X POST https://api.provision-stack.com/auth/tokens -H 'Content-Type: application/json' -d '{"agentId":"your-agent","scopes":[]}'`
### Local stdio (via npx)
```bash
npx @provision-stack/mcp
```
Or add to your MCP client config:
```json
{
"mcpServers": {
"provision-stack": {
"command": "npx",
"args": ["-y", "@provision-stack/mcp"],
"env": {
"PROVISION_STACK_API_TOKEN": "YOUR_TOKEN"
}
}
}
}
```
### Install globally
```bash
npm install -g @provision-stack/mcp
provision-stack-mcp
```
## Tools (12)
| Tool | Purpose |
|------|---------|
| `suggestions.generate` | Get 4 tier options (Starter/MVP/Startup/Enterprise) with monthly costs |
| `pricing.get` | Detailed cost breakdown for individual cloud resources |
| `region.detect` | Detect configured AWS/GCP/Azure/Oracle region |
| `providers.detect` | Detect all configured cloud providers |
| `credentials.list` | Check cloud credential configuration |
| `deploy.run` | Provision infrastructure via the Execution API |
| `deploy.status` | Check deployment progress |
| `deploy.destroy` | Tear down a specific deployment |
| `deploy.list` | List all tracked deployments |
| `deploy.teardown_latest` | Destroy most recent active deployment |
| `billing.balance` | Check account credit balance |
| `billing.top_up` | Add credits (XRP or Stripe) |
## Typical Flow
```
1. region.detect → Get your AWS region
2. suggestions.generate → Get 4 tier options with costs
3. Present options → Show costs, resources, tradeoffs
4. WAIT for user choice → Never proceed without explicit selection
5. deploy.run → Provision infrastructure
6. Report results → Deployment ID, resources, costs
```
## Environment Variables
| Variable | Description | Default |
|----------|-------------|---------|
| `PROVISION_STACK_EXECUTION_API_URL` | API base URL | `https://api.provision-stack.com` |
| `PROVISION_STACK_API_TOKEN` | Bearer token | (none — read-only tools work without) |
| `AWS_REGION` | AWS region override | `~/.aws/config` or `us-east-1` |
| `AWS_PROFILE` | AWS profile name | `default` |
## Architecture
This package is a **thin client** — it defines MCP tools and forwards calls to the hosted Execution API. All business logic (pattern matching, pricing, Terraform generation, verification) runs server-side.
```
Your AI Client → MCP stdio/HTTP → This Package → Execution API → Your AWS Account
```
The API endpoint requires authentication for write operations (deploy.run, deploy.destroy, billing.top_up).
Read operations (suggestions.generate, pricing.get, region.detect) work without a token.
Pre-0.5.0 underscore names still work on `tools/call` (e.g. `generate_suggestions` → `suggestions.generate`); `tools/list` advertises only the dotted names.
## Links
- **API**: https://api.provision-stack.com
- **Website**: https://provision-stack.com
- **Docs**: https://provision-stack.com/llms.txt
- **Issues**: https://github.com/TravisLinkey/provision-stack-mcp/issues
## License
MIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose. Suggestions.generate for options, providers.detect for provider discovery, pricing.get for component costs, credentials.list for credential checks, region.detect for region resolution, and deploy.* tools cover the full lifecycle with clear differentiation (e.g., deploy.destroy vs deploy.teardown_latest). Billing tools are separate. No overlap.
All tools follow a consistent category.action pattern (noun.verb) using snake_case in the verb part (e.g., suggestions.generate, deploy.teardown_latest, billing.top_up). The pattern is uniform across the set, making it predictable for agents.
With 12 tools, the surface is well-scoped. It covers discovery (detect, list), pricing (get, generate), deployment (run, status, destroy, list, teardown_latest), and billing (balance, top_up). No tool is extraneous, and the count feels appropriate for a provisioning domain.
The tool set appears complete for the domain of provisioning cloud stacks. It covers the full workflow: initial discovery, pricing, deployment, monitoring, teardown, and billing. No obvious gaps like missing deployment modification or log retrieval, given the stated purpose.