@awesomate/hosting-mcp 0.1.0

package/README.md

@@ -0,0 +1,48 @@
+# @awesomate/hosting-mcp
+
+MCP server that lets Claude read (and, in later releases, manage) your
+Awesomate WordPress hosting: provisioning status, sites, domains, plan,
+limits, and upgrade nudges.
+
+## Setup
+
+The intended path is the **Connect Claude Code** card on
+[hub.awesomate.ai/sites](https://hub.awesomate.ai/sites): it generates a
+one-time prompt that has Claude run the bundled `skill/awesomate-hosting/scripts/bootstrap.mjs`,
+which redeems a setup code for a scoped access token (stored at
+`~/.awesomate/credentials.json`, chmod 600), provisions an SSH key
+(Support Plus+), and registers this server. The **`awesomate-hosting` skill**
+(bundled under `skill/`) makes Claude plan-aware and enforces snapshot-before-change.
+
+Manual registration:
+
+```bash
+claude mcp add awesomate-hosting --env AWESOMATE_PAT=amt_pat_... -- npx -y @awesomate/hosting-mcp
+```
+
+Config resolution: `AWESOMATE_PAT` / `AWESOMATE_API_BASE` env vars, falling
+back to `~/.awesomate/credentials.json` (`{ "pat": "...", "apiBase": "..." }`).
+
+## Tools (v0.1 — read-only)
+
+| Tool | What it returns |
+|---|---|
+| `awesomate_get_context` | Plan, capabilities, scopes, token expiry, cPanel routing |
+| `awesomate_get_hosting_status` | Provisioning state, primary domain, DNS targets |
+| `awesomate_get_hosting_account` | cPanel package/server details |
+| `awesomate_list_sites` | WordPress sites with SSL/WP-version state |
+| `awesomate_list_domains` | Included + custom domains, DNS/SSL state |
+| `awesomate_get_limits` | Usage vs plan limits + upgrade nudges |
+| `awesomate_get_plan_features` | Static plan-ladder reference |
+
+Access tokens are plan-scoped server-side: what the token can do always
+reflects the account's **live** plan. Tokens are revocable from the hub Sites
+page.
+
+## Development
+
+```bash
+npm install
+npm run typecheck
+npm run build     # esbuild bundle → dist/index.js (single file, no runtime deps)
+```