naro-mcp 0.17.0 → 0.18.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +32 -28
- package/dist/index.js +16663 -16355
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,8 +1,9 @@
|
|
|
1
1
|
# naro-mcp
|
|
2
2
|
|
|
3
3
|
MCP server that lets AI agents (Claude Code, Cursor, Codex, ChatGPT, …)
|
|
4
|
-
operate [Naro](https://naro.sh): deploy projects,
|
|
5
|
-
|
|
4
|
+
operate [Naro](https://naro.sh): deploy projects (to production, a preview or a
|
|
5
|
+
named environment such as QA or staging), read build/runtime logs, manage
|
|
6
|
+
environment variables and domains, promote and roll back, work with
|
|
6
7
|
the project's database (SQL, migrations, types, export and restore), and
|
|
7
8
|
read Speed Insights and turn it on or off, read Web Analytics, read or switch
|
|
8
9
|
preview protection, and manage Storage buckets — the same control plane API
|
|
@@ -54,34 +55,36 @@ Headless/CI agents can skip `naro login` and set a token instead:
|
|
|
54
55
|
|
|
55
56
|
## Tools
|
|
56
57
|
|
|
57
|
-
| Tool | Purpose
|
|
58
|
-
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
59
|
-
| `whoami`, `list_teams` | Account / team context
|
|
60
|
-
| `list_projects`, `get_project`, `link_project` | Project discovery + `.naro/project.json` linking
|
|
61
|
-
| `get_team_usage` | Team usage for a UTC month (`month`, the current one by default): requests, builds and custom domains per day and per project, the plan's `limits`, the enforcement mode, and `summary` (each metric against its limit, and `status` paused/over/near). `team` defaults to the team linked in `directory`, then your only team; otherwise `needsTeam` with the list. Owner, billing and enterprise_viewer only (403 `FORBIDDEN` otherwise). Read-only
|
|
62
|
-
| `deploy` | Local Next.js build → upload → live URL (preview
|
|
63
|
-
| `list_deployments`, `get_deployment` | Deployment status / history
|
|
64
|
-
| `get_build_logs`, `get_runtime_logs` | Debugging failed builds and live workers
|
|
65
|
-
| `list_environment_variables`, `set_environment_variable`, `remove_environment_variable` | Env management (secret values never returned)
|
|
66
|
-
| `list_domains`, `add_domain`, `verify_domain`, `remove_domain` | Custom domains: the one CNAME to create (naro connects it within ~5 minutes), plus a re-check that says which of ownership / certificate / routing is still missing. An apex is attached as an apex+www pair by default (`withWww: false` to opt out)
|
|
67
|
-
| `promote_deployment`, `rollback_deployment` | Production traffic control
|
|
68
|
-
| `cancel_deployment` | Stops a build that is still running (QUEUED–BUILDING). Does not undo a deployment that already went live — use `rollback_deployment` for that
|
|
69
|
-
| `
|
|
70
|
-
| `
|
|
71
|
-
| `
|
|
72
|
-
| `
|
|
73
|
-
| `
|
|
74
|
-
| `
|
|
75
|
-
| `
|
|
76
|
-
| `
|
|
77
|
-
| `
|
|
78
|
-
| `
|
|
58
|
+
| Tool | Purpose |
|
|
59
|
+
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
60
|
+
| `whoami`, `list_teams` | Account / team context |
|
|
61
|
+
| `list_projects`, `get_project`, `link_project` | Project discovery + `.naro/project.json` linking |
|
|
62
|
+
| `get_team_usage` | Team usage for a UTC month (`month`, the current one by default): requests, builds and custom domains per day and per project, the plan's `limits`, the enforcement mode, and `summary` (each metric against its limit, and `status` paused/over/near). `team` defaults to the team linked in `directory`, then your only team; otherwise `needsTeam` with the list. Owner, billing and enterprise_viewer only (403 `FORBIDDEN` otherwise). Read-only |
|
|
63
|
+
| `deploy` | Local Next.js build → upload → live URL (preview, `production: true`, or a named environment with `environment: "qa"` — not together with `production`; `production` and `preview` are not environment names). The result's `target` is `production`, `preview` or the environment's slug, and `environment` is the slug or null. Local .env files are never uploaded; unset keys come back as `missingEnvKeys` |
|
|
64
|
+
| `list_deployments`, `get_deployment` | Deployment status / history |
|
|
65
|
+
| `get_build_logs`, `get_runtime_logs` | Debugging failed builds and live workers |
|
|
66
|
+
| `list_environment_variables`, `set_environment_variable`, `remove_environment_variable` | Env management (secret values never returned). `target` is `production`, `preview`, `all` or an environment's slug (`all` by default when setting); without `target`, `remove_environment_variable` removes the `production`, `preview` and `all` rows and leaves an environment's value alone. A name that cannot be a slug is refused as `Invalid target "<value>" — use production, preview, all or an environment name.`; a slug that is not an environment answers `404 ENVIRONMENT_NOT_FOUND` |
|
|
67
|
+
| `list_domains`, `add_domain`, `verify_domain`, `remove_domain` | Custom domains: the one CNAME to create (naro connects it within ~5 minutes), plus a re-check that says which of ownership / certificate / routing is still missing. An apex is attached as an apex+www pair by default (`withWww: false` to opt out) |
|
|
68
|
+
| `promote_deployment`, `rollback_deployment` | Production traffic control |
|
|
69
|
+
| `cancel_deployment` | Stops a build that is still running (QUEUED–BUILDING). Does not undo a deployment that already went live — use `rollback_deployment` for that |
|
|
70
|
+
| `list_environments`, `create_environment`, `update_environment`, `delete_environment` | Named environments (QA, staging), served at `{subdomain}--{slug}` apart from production and the preview. `list_environments` returns `{ projectId, environments, limit }` (`limit` is what the plan allows per project, null for no limit); `create_environment` takes `slug` and optionally `branch` (pushes to it deploy there), `copyEnvFrom` (`preview` by default, `production` or `none`) and `database` (`schema` by default, or `empty`); `update_environment` takes the environment's slug and `branch` (an empty string takes it off) and/or `protectionEnabled`. **`update_environment` is destructive on its `protectionEnabled` argument** (`false` opens the environment to anyone with the link — like `set_preview_protection`) and **`delete_environment` is destructive** (removes its worker and protection key). Deploy to one with `deploy`'s `environment`; set its variables with the env tools' `target` |
|
|
71
|
+
| `enable_database`, `get_database`, `list_tables` | The project's D1 database: turn it on, status/size/limits, schema (verbose: true for columns, indexes and foreign keys) |
|
|
72
|
+
| `execute_sql` | Run SQL (argument `query`, optional `params` for a single statement; several statements run as one transaction). Destructive; under `--read-only` it stays but accepts a single read statement only |
|
|
73
|
+
| `apply_migration`, `list_migrations`, `generate_typescript_types` | Numbered migrations in the `d1_migrations` ledger wrangler also uses (each file all-or-nothing), and TypeScript types for the schema (text only; its `Database` is what `createClient<Database>()` from `naro-js` takes) |
|
|
74
|
+
| `create_table`, `alter_table`, `drop_table`, `create_index`, `drop_index` | Schema changes without SQL: naro renders checked DDL, applies it as one numbered migration (`NNNN_schema_<op>_<table>.sql`) and writes the file like `apply_migration`. `alter_table` adds, renames or drops a column or renames the table. Dropping a table or column needs `confirm`; `alter_table`, `drop_table` and `drop_index` are destructive and hidden under `--read-only`. `dryRun: true` returns the SQL only |
|
|
75
|
+
| `export_database` | SQL dump of the database (`schemaOnly`, `dataOnly`, `tables`): waits up to 5 minutes and returns a signed download link plus `atBookmark`, the point the dump reflects |
|
|
76
|
+
| `restore_database` | Time Travel restore to a `bookmark` or a `timestamp` (last 30 days). Destructive; hidden under `--read-only`. Returns `previousBookmark`, which undoes it |
|
|
77
|
+
| `get_speed_insights`, `set_speed_insights` | Speed Insights: each Web Vital's p75, the selected metric by page, device, browser, operating system, country, element and deployment, or one route's paths; the page load's p75 and the mean of each step (`pageLoad`); production or preview (`environment`); narrowed to one page, country, device, browser or operating system (`path`, `country`, `device`, `browser`, `os`); turn measuring on or off (not destructive: nothing is deleted) |
|
|
78
|
+
| `get_analytics` | Web Analytics: visitors and page views over `range` (24h, 7d or 30d), the trend, and the top 10 pages, referrers, countries, devices, browsers and operating systems by page views; narrowed to one value of each dimension (`path`, `referrer`, `country`, `device`, `browser`, `os`), all given must match. Production only: there is no `environment`, and one is refused. Read-only |
|
|
79
|
+
| `get_preview_protection`, `set_preview_protection` | Preview protection: whether the preview URL (`{subdomain}-preview`) is open to project members only, and whether a bypass secret is set; turn it on or off. **`set_preview_protection` is destructive** (turning protection off publishes unreleased work). Bypass secrets are made in the dashboard or with `naro protection bypass`, never by a tool, so they stay out of the conversation |
|
|
80
|
+
| `get_storage`, `enable_storage`, `list_storage_buckets`, `create_storage_bucket`, `update_storage_bucket`, `delete_storage_bucket`, `list_storage_objects`, `create_storage_signed_url`, `delete_storage_objects` | Naro Storage: on or off, limits, usage, today's operations and whether uploads are stopped, and buckets; turn it on; make, change and remove buckets (`delete_storage_bucket` is destructive: `confirm` is the bucket's name, `empty: true` deletes its objects first; `update_storage_bucket` is destructive on its `public` argument, like `deploy` on `production`: `public: true` needs the same `confirm`); list a folder's files (`search` keeps the names that start with a text; a backend from before it answers `INVALID_REQUEST` — run `naro backend enable` once), make a signed link of up to an hour, and delete files (`delete_storage_objects` is destructive: `confirm` is the bucket's name) — through the control plane, so no service key reaches the MCP process. Files go in through naro-js or `naro storage cp`, not through MCP |
|
|
79
81
|
|
|
80
82
|
Destructive tools say so in their descriptions; agents should confirm with
|
|
81
83
|
the user before calling them. `set_preview_protection` is one of them: turning
|
|
82
84
|
protection off publishes the preview to anyone with the link, so the marker
|
|
83
85
|
sits on its `enabled` argument and clients that confirm on `destructiveHint`
|
|
84
|
-
ask before either value.
|
|
86
|
+
ask before either value. `update_environment` does the same with its
|
|
87
|
+
`protectionEnabled` argument. Domain tools return server-computed
|
|
85
88
|
`instructions`, `guidance` and `cause` — relay those to the user verbatim
|
|
86
89
|
rather than dictating DNS records from memory, because an apex domain
|
|
87
90
|
(`example.com`) cannot take the CNAME a subdomain does. That is also why
|
|
@@ -93,9 +96,10 @@ validation backoff, so space calls out instead of polling tightly. Every result
|
|
|
93
96
|
(`{"success": true, …}` or `{"success": false, "code": "BUILD_FAILED", …}`)
|
|
94
97
|
so agents can chain: deploy → on failure `get_build_logs` → fix code →
|
|
95
98
|
deploy again. A failed build also names its stage in `buildCode`
|
|
96
|
-
(`INSTALL_FAILED`, `NEXT_VERSION_UNSUPPORTED`, …); a Next.js app whose
|
|
97
|
-
|
|
98
|
-
|
|
99
|
+
(`INSTALL_FAILED`, `NEXT_VERSION_UNSUPPORTED`, …); a Next.js app whose own
|
|
100
|
+
`next build` failed reports `BUILD_FAILED`, and one whose own build did not
|
|
101
|
+
fail but no deployment strategy could ship reports `NO_DEPLOYMENT_STRATEGY` — each
|
|
102
|
+
strategy's failure is in the message.
|
|
99
103
|
|
|
100
104
|
## Flags
|
|
101
105
|
|