@cloudgrid-io/mcp 0.20.30 → 0.20.31
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cloudgrid-io/mcp",
|
|
3
|
-
"version": "0.20.
|
|
3
|
+
"version": "0.20.31",
|
|
4
4
|
"description": "MCP access to CloudGrid — the live runtime environment where the user's apps run WITH the infrastructure they need out of the box: managed MongoDB, Redis (cache/queues/pub-sub), a pgvector store, persistent disk, and built-in AI with no API keys, in any language or stack, no Docker or Kubernetes to manage. Brainstorm, build, plug, and improve apps, games, dashboards, and tools; instant single-page publishes and full runtime-app deploys with a live URL — for developers and non-technical users. Three editions: local stdio (full toolset), hosted web (light, CLI-free), and a public docs-search server.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -41,9 +41,17 @@ Persistent apps are owned entities.
|
|
|
41
41
|
|
|
42
42
|
## 3. Scaffold
|
|
43
43
|
|
|
44
|
-
`grid_create_project` an app `<name>`. It scaffolds the project folder
|
|
45
|
-
`
|
|
46
|
-
it from the manifest (honoring its `name:`) and
|
|
44
|
+
`grid_create_project` an app `<name>`. It scaffolds the project folder, a
|
|
45
|
+
`cloudgrid.yaml`, and a starter `web` service. No server entity exists yet — the
|
|
46
|
+
first `grid plug` auto-creates it from the manifest (honoring its `name:`) and
|
|
47
|
+
writes `.cloudgrid/link.json`.
|
|
48
|
+
|
|
49
|
+
The starter files are throwaway — the `ai-app` template (step 4) is the source
|
|
50
|
+
of truth. **The template is plain JavaScript.** The `nextjs` scaffold, on the
|
|
51
|
+
other hand, writes a TypeScript starter (`tsconfig.json`, `app/layout.tsx`,
|
|
52
|
+
`app/page.tsx`). Before applying the template, delete the scaffolded
|
|
53
|
+
`tsconfig.json` and `app/*.tsx`, then write the template's `.js` files. Never
|
|
54
|
+
leave both `.tsx` and `.js` for the same route — that breaks `next build`.
|
|
47
55
|
|
|
48
56
|
You then do two things: (a) write the app under **`services/web/`**, and (b) fill
|
|
49
57
|
in `cloudgrid.yaml` to the shape below (`services.web` type `nextjs` + `needs: {
|
package/src/tools/register.js
CHANGED
|
@@ -934,7 +934,7 @@ export function registerTools(server, ctx) {
|
|
|
934
934
|
|
|
935
935
|
regTool(
|
|
936
936
|
"grid_create_project",
|
|
937
|
-
"Scaffold a new CloudGrid app or agent folder (cloudgrid.yaml + a web service), optionally pre-declaring resources. Wraps `grid new` (scaffolds locally; no server entity until you grid_deploy).",
|
|
937
|
+
"Scaffold a new CloudGrid app or agent folder (cloudgrid.yaml + a web service), optionally pre-declaring resources. Wraps `grid new` (scaffolds locally; no server entity until you grid_deploy). Language note: the nextjs starter is TypeScript (writes tsconfig.json + app/*.tsx), but CloudGrid templates are plain JavaScript. When you fill a template, treat the template's files as the source of truth — delete the scaffolded tsconfig.json and app/*.tsx, then write the template's .js files. Never leave both .tsx and .js for the same route.",
|
|
938
938
|
{
|
|
939
939
|
kind: z.enum(["app", "agent"]).describe("Entity kind. 'agent' scaffolds an agent: block."),
|
|
940
940
|
name: z.string().describe("Slug: 3-40 lowercase alphanumerics and hyphens."),
|