@lukoweb/apitogo 0.2.60 → 0.2.64

package/docs/customization/fonts.md

@@ -1,105 +1,105 @@
----
-sidebar_icon: baseline
-title: Font & Typography
-sidebar_label: Font & Typography
-description:
-  Learn how to customize fonts and typography in APIToGo using predefined Google Fonts, custom font
-  URLs, or local fonts for sans, serif, and monospace text.
----
-
-APIToGo allows you to customize fonts for text (`sans`), serif content (`serif`), and code (`mono`).
-You can use predefined Google Fonts, external sources, or local fonts.
-
-Fonts go under `fonts` in the portal's theme file, **`apitogo/portal/theme.json`**. See
-[Colors & theme](./colors-theme.mdx) for the rest of that file. Local font files go in
-`apitogo/portal/public/`, which the portal serves at `/`.
-
-## Predefined Google Fonts
-
-The easiest way to use fonts is with predefined Google Fonts. Simply specify the font name as a
-string:
-
-```json title=apitogo/portal/theme.json
-{
-  "fonts": {
-    "sans": "Inter",
-    "serif": "Merriweather",
-    "mono": "JetBrains Mono"
-  }
-}
-```
-
-### Available Google Fonts
-
-The following fonts are available as predefined options:
-
-**Sans Serif:** Inter, Roboto, Open Sans, Poppins, Montserrat, Outfit, Plus Jakarta Sans, DM Sans,
-IBM Plex Sans, Geist, Oxanium, Space Grotesk
-
-**Serif:** Architects Daughter, Merriweather, Playfair Display, Lora, Source Serif Pro, Libre
-Baskerville
-
-**Monospace:** JetBrains Mono, Fira Code, Source Code Pro, IBM Plex Mono, Roboto Mono, Space Mono,
-Geist Mono
-
-## Custom Font URLs
-
-For more control or to use fonts not in the predefined list, you can specify a custom font URL:
-
-```json title=apitogo/portal/theme.json
-{
-  "fonts": {
-    "sans": {
-      "url": "https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap",
-      "fontFamily": "Roboto, sans-serif"
-    },
-    "mono": {
-      "url": "https://fonts.googleapis.com/css2?family=Roboto+Mono:wght@400;700&display=swap",
-      "fontFamily": "Roboto Mono, monospace"
-    }
-  }
-}
-```
-
-## Local Fonts
-
-To use local fonts, add them to the `public` folder and create a `fonts.css` file:
-
-```css
-@font-face {
-  font-family: "CustomFont";
-  font-style: normal;
-  font-weight: 400;
-  src: url("/custom-font-400.woff2") format("woff2");
-}
-```
-
-Then reference the local CSS file:
-
-```json title=apitogo/portal/theme.json
-{
-  "fonts": {
-    "sans": {
-      "url": "/fonts.css",
-      "fontFamily": "CustomFont, sans-serif"
-    }
-  }
-}
-```
-
-## Mixed Configuration
-
-You can mix predefined fonts with custom fonts:
-
-```json title=apitogo/portal/theme.json
-{
-  "fonts": {
-    "sans": "Inter",
-    "serif": {
-      "url": "/custom-serif.css",
-      "fontFamily": "CustomSerif, serif"
-    },
-    "mono": "Fira Code"
-  }
-}
-```
+---
+sidebar_icon: baseline
+title: Font & Typography
+sidebar_label: Font & Typography
+description:
+  Learn how to customize fonts and typography in APIToGo using predefined Google Fonts, custom font
+  URLs, or local fonts for sans, serif, and monospace text.
+---
+
+APIToGo allows you to customize fonts for text (`sans`), serif content (`serif`), and code (`mono`).
+You can use predefined Google Fonts, external sources, or local fonts.
+
+Fonts go under `fonts` in the portal's theme file, **`apitogo/portal/theme.json`**. See
+[Colors & theme](./colors-theme.mdx) for the rest of that file. Local font files go in
+`apitogo/portal/public/`, which the portal serves at `/`.
+
+## Predefined Google Fonts
+
+The easiest way to use fonts is with predefined Google Fonts. Simply specify the font name as a
+string:
+
+```json title=apitogo/portal/theme.json
+{
+  "fonts": {
+    "sans": "Inter",
+    "serif": "Merriweather",
+    "mono": "JetBrains Mono"
+  }
+}
+```
+
+### Available Google Fonts
+
+The following fonts are available as predefined options:
+
+**Sans Serif:** Inter, Roboto, Open Sans, Poppins, Montserrat, Outfit, Plus Jakarta Sans, DM Sans,
+IBM Plex Sans, Geist, Oxanium, Space Grotesk
+
+**Serif:** Architects Daughter, Merriweather, Playfair Display, Lora, Source Serif Pro, Libre
+Baskerville
+
+**Monospace:** JetBrains Mono, Fira Code, Source Code Pro, IBM Plex Mono, Roboto Mono, Space Mono,
+Geist Mono
+
+## Custom Font URLs
+
+For more control or to use fonts not in the predefined list, you can specify a custom font URL:
+
+```json title=apitogo/portal/theme.json
+{
+  "fonts": {
+    "sans": {
+      "url": "https://fonts.googleapis.com/css2?family=Roboto:wght@400;700&display=swap",
+      "fontFamily": "Roboto, sans-serif"
+    },
+    "mono": {
+      "url": "https://fonts.googleapis.com/css2?family=Roboto+Mono:wght@400;700&display=swap",
+      "fontFamily": "Roboto Mono, monospace"
+    }
+  }
+}
+```
+
+## Local Fonts
+
+To use local fonts, add them to the `public` folder and create a `fonts.css` file:
+
+```css
+@font-face {
+  font-family: "CustomFont";
+  font-style: normal;
+  font-weight: 400;
+  src: url("/custom-font-400.woff2") format("woff2");
+}
+```
+
+Then reference the local CSS file:
+
+```json title=apitogo/portal/theme.json
+{
+  "fonts": {
+    "sans": {
+      "url": "/fonts.css",
+      "fontFamily": "CustomFont, sans-serif"
+    }
+  }
+}
+```
+
+## Mixed Configuration
+
+You can mix predefined fonts with custom fonts:
+
+```json title=apitogo/portal/theme.json
+{
+  "fonts": {
+    "sans": "Inter",
+    "serif": {
+      "url": "/custom-serif.css",
+      "fontFamily": "CustomSerif, serif"
+    },
+    "mono": "Fira Code"
+  }
+}
+```

package/docs/customization/landing-page.md

@@ -153,7 +153,7 @@ to the gateway if they must not be discoverable.
 ### Troubleshooting
 
 - **The list is always the fallback:** the project has no plans backend yet. Add `plans` to the
-  config and run `npx apitogo deploy`.
+  config and run `apitogo deploy`.
 - **CORS errors:** the backend only allows the portal's configured frontend URL. Serving the site
   from another domain requires adding it to the backend's allowed origins.
 - **Empty list on a new portal:** the portal is not activated yet, or the gateway has no release.

package/docs/deploy/apitogo.md

@@ -1,9 +1,9 @@
 # Deploy with the APItoGo CLI
 
 ```bash
-npx apitogo login
-npx apitogo deploy
-npx apitogo status
+apitogo login
+apitogo deploy
+apitogo status
 ```
 
 `deploy` creates the project on its first run, then sets up every service in `apitogo.config.json`.

package/docs/deployment.md

@@ -3,7 +3,7 @@
 Your portal, gateway, sign-in and plans are deployed to APItoGo with one command:
 
 ```bash
-npx apitogo deploy
+apitogo deploy
 ```
 
 | Path             | Docs                                                                                      |
@@ -11,5 +11,5 @@ npx apitogo deploy
 | **CLI**          | [Deploy with the APItoGo CLI](./deploy/apitogo.md) · [Go live with CLI](./cli/go-live.md) |
 | **MCP / agents** | [Go live](./mcp/go-live.md)                                                               |
 
-To check the portal before deploying, `npx apitogo run` previews it locally and `npx apitogo build`
-makes a production build.
+To check the portal before deploying, `apitogo run` previews it locally and `apitogo build` makes a
+production build.

package/docs/guides/custom-pages.md

@@ -42,9 +42,9 @@ export default function QuickstartPage() {
 
 ## CLI scaffold
 
-`npx apitogo config` creates a starter React page at `apitogo/portal/pages/<slug>.tsx`. Choose
-`page` in the wizard loop, or pass `--page-slug` and `--page-title`. Add `--page-format mdx` for a
-Markdown page instead.
+`apitogo config` creates a starter React page at `apitogo/portal/pages/<slug>.tsx`. Choose `page` in
+the wizard loop, or pass `--page-slug` and `--page-title`. Add `--page-format mdx` for a Markdown
+page instead.
 
 Predefined UI components (Callout, Card, Button, Heading, and more) are documented under
 [/docs/components](/docs/components).

package/docs/guides/customer-account.md

@@ -94,7 +94,7 @@ the customer calls, those calls show as errors in the usage page.
 | `429`                                         | The plan's limit was reached. The rate limit renews each period; the quota carries `Retry-After`. |
 | A customer paid but has no plan               | The webhook is missing or its signing secret is wrong. Check it in Stripe and in `plans.billing`. |
 | The usage page shows nothing after real calls | Calls only count when made with a key. Check that the gateway has been deployed with plans.       |
-| Calls from the portal's own pages are blocked | Run `npx apitogo deploy` again. The gateway lists the portal's address after the portal exists.   |
+| Calls from the portal's own pages are blocked | Run `apitogo deploy` again. The gateway lists the portal's address after the portal exists.       |
 
 ## Related
 

package/docs/guides/stripe-setup.mdx

@@ -6,8 +6,8 @@ description:
   step by step with pictures.
 ---
 
-A plan with a price is paid through **your own Stripe account**. `npx apitogo deploy` needs two
-things from Stripe:
+A plan with a price is paid through **your own Stripe account**. `apitogo deploy` needs two things
+from Stripe:
 
 | What                   | Starts with              | What it does                                        |
 | ---------------------- | ------------------------ | --------------------------------------------------- |
@@ -37,7 +37,7 @@ restricted key (`rk_`) works too, if it may write Checkout Sessions, Customers a
 Run deploy and paste the key when it asks:
 
 ```bash
-npx apitogo deploy
+apitogo deploy
 # Stripe secret key (hidden):
 ```
 
@@ -93,13 +93,13 @@ Paste it where deploy asks:
 If you skipped it, set it later and deploy the plans again:
 
 ```bash
-npx apitogo secrets set STRIPE_WEBHOOK
-npx apitogo deploy --only plans
+apitogo secrets set STRIPE_WEBHOOK
+apitogo deploy --only plans
 ```
 
 ## Check it works
 
-Run `npx apitogo deploy --only plans` again. When Stripe has sent an event, it reports:
+Run `apitogo deploy --only plans` again. When Stripe has sent an event, it reports:
 
 ```
 Stripe webhook: verified (last event 2 min ago, checkout.session.completed)
@@ -114,9 +114,9 @@ Live mode has its own keys and its own webhooks. Switch to your live account in
 three steps there, and set the new values:
 
 ```bash
-npx apitogo secrets set STRIPE_API_KEY
-npx apitogo secrets set STRIPE_WEBHOOK
-npx apitogo deploy --only plans
+apitogo secrets set STRIPE_API_KEY
+apitogo secrets set STRIPE_WEBHOOK
+apitogo deploy --only plans
 ```
 
 Selling paid plans needs the **Starter** or **Professional** hosting plan. See

package/docs/markdown/frontmatter.md

@@ -133,8 +133,8 @@ draft: true
 
 When `draft: true` is set:
 
-- The document will be visible when running `npx apitogo run`
-- The document will be excluded from builds created with `npx apitogo build`
+- The document will be visible when running `apitogo run`
+- The document will be excluded from builds created with `apitogo build`
 - The document won't appear in the navigation or be accessible via URL in production
 
 :::

package/docs/mcp/go-live.md

@@ -29,11 +29,11 @@ Paid plans need the project's Stripe key and webhook secret. Set them yourself i
 secret's value never goes through the agent:
 
 ```bash
-npx apitogo secrets set STRIPE_API_KEY
+apitogo secrets set STRIPE_API_KEY
 ```
 
 ```bash
-npx apitogo secrets set STRIPE_WEBHOOK
+apitogo secrets set STRIPE_WEBHOOK
 ```
 
 **`apitogo_secrets_list`** shows which names are set. See the
@@ -60,11 +60,11 @@ URL and the sign-in issuer.
 Every tool answers with the CLI's JSON. A failure carries `error` and usually a `hint` with the next
 step, for example to log in:
 
-| Message                  | What to do                                                                        |
-| ------------------------ | --------------------------------------------------------------------------------- |
-| Not logged in            | Run `npx apitogo login`, or give the server API credentials ([setup](./setup.md)) |
-| A secret is missing      | Set it with `npx apitogo secrets set NAME`                                        |
-| Hosting is not ready yet | Wait a few minutes, then deploy again                                             |
+| Message                  | What to do                                                                    |
+| ------------------------ | ----------------------------------------------------------------------------- |
+| Not logged in            | Run `apitogo login`, or give the server API credentials ([setup](./setup.md)) |
+| A secret is missing      | Set it with `apitogo secrets set NAME`                                        |
+| Hosting is not ready yet | Wait a few minutes, then deploy again                                         |
 
 ## Remove it
 

package/docs/mcp/overview.md

@@ -1,58 +1,58 @@
----
-title: MCP overview
-description:
-  Let an AI agent create, shape, check and deploy an APItoGo project through the APItoGo MCP server.
-sidebar_icon: bot
----
-
-The **APItoGo MCP** server (`@lukoweb/apitogo-mcp`) gives an AI agent the same commands you run in a
-terminal: create a project, add services, change plans and pages, check, preview and deploy. Each
-tool runs the [`apitogo` CLI](../cli/overview.md) in the project folder, so an agent and a person
-always get the same result.
-
-**First time?** Wire the server into your agent → **[Configure MCP in your agent](./setup.md)**.
-
-## How it fits together
-
-```
-agent ──MCP tool──> apitogo-mcp ──runs──> apitogo <command> --json   (in the project folder)
-                                              │
-                                              ├── apitogo.config.json, apitogo/   (your files)
-                                              └── APItoGo platform               (deploy, status)
-```
-
-- Everything the project is lives in `apitogo.config.json` (config version 2) and the `apitogo/`
-  folder. See [Configuration](../configuration/overview.md).
-- The tools answer with the CLI's JSON, so the agent sees what changed, what a deploy would do, and
-  why something failed.
-- The agent can also edit the project's files directly (the landing page, docs pages, OpenAPI file,
-  `plans.json`) when no tool covers a change.
-
-## The usual flow
-
-| Step                      | Tool                                                       |
-| ------------------------- | ---------------------------------------------------------- |
-| Make the project folder   | `apitogo_create`, or `apitogo_init` + `apitogo_add`        |
-| Shape it                  | `apitogo_config` (name, OpenAPI, pages, plans), file edits |
-| Check it                  | `apitogo_check`                                            |
-| Make the platform project | `apitogo_project_create`                                   |
-| Preview the deploy        | `apitogo_plan`                                             |
-| Deploy                    | `apitogo_deploy`                                           |
-| See what is live          | `apitogo_status`                                           |
-
-Details: [Shape a project](./shape.md) · [Go live](./go-live.md) · [All tools](./tools.md).
-
-## What the agent never does
-
-- **Handle secret values.** You set secrets such as the Stripe key yourself with
-  `apitogo secrets set NAME` in a terminal. The agent can list their names.
-- **Delete without you.** `apitogo_teardown` needs the project's name typed back, and the server
-  tells the agent to ask you first, as for removing a secret, choosing a paid plan, or a deploy
-  change that cannot be undone.
-- **Pay.** A paid project plan answers with a checkout link that you open and pay.
-
-## Next
-
-- [Configure MCP](./setup.md)
-- [Shape a project](./shape.md) · [Go live](./go-live.md) · [Tools](./tools.md)
-- Without an agent: [CLI overview](../cli/overview.md)
+---
+title: MCP overview
+description:
+  Let an AI agent create, shape, check and deploy an APItoGo project through the APItoGo MCP server.
+sidebar_icon: bot
+---
+
+The **APItoGo MCP** server (`@lukoweb/apitogo-mcp`) gives an AI agent the same commands you run in a
+terminal: create a project, add services, change plans and pages, check, preview and deploy. Each
+tool runs the [`apitogo` CLI](../cli/overview.md) in the project folder, so an agent and a person
+always get the same result.
+
+**First time?** Wire the server into your agent → **[Configure MCP in your agent](./setup.md)**.
+
+## How it fits together
+
+```
+agent ──MCP tool──> apitogo-mcp ──runs──> apitogo <command> --json   (in the project folder)
+                                              │
+                                              ├── apitogo.config.json, apitogo/   (your files)
+                                              └── APItoGo platform               (deploy, status)
+```
+
+- Everything the project is lives in `apitogo.config.json` (config version 2) and the `apitogo/`
+  folder. See [Configuration](../configuration/overview.md).
+- The tools answer with the CLI's JSON, so the agent sees what changed, what a deploy would do, and
+  why something failed.
+- The agent can also edit the project's files directly (the landing page, docs pages, OpenAPI file,
+  `plans.json`) when no tool covers a change.
+
+## The usual flow
+
+| Step                      | Tool                                                       |
+| ------------------------- | ---------------------------------------------------------- |
+| Make the project folder   | `apitogo_create`, or `apitogo_init` + `apitogo_add`        |
+| Shape it                  | `apitogo_config` (name, OpenAPI, pages, plans), file edits |
+| Check it                  | `apitogo_check`                                            |
+| Make the platform project | `apitogo_project_create`                                   |
+| Preview the deploy        | `apitogo_plan`                                             |
+| Deploy                    | `apitogo_deploy`                                           |
+| See what is live          | `apitogo_status`                                           |
+
+Details: [Shape a project](./shape.md) · [Go live](./go-live.md) · [All tools](./tools.md).
+
+## What the agent never does
+
+- **Handle secret values.** You set secrets such as the Stripe key yourself with
+  `apitogo secrets set NAME` in a terminal. The agent can list their names.
+- **Delete without you.** `apitogo_teardown` needs the project's name typed back, and the server
+  tells the agent to ask you first, as for removing a secret, choosing a paid plan, or a deploy
+  change that cannot be undone.
+- **Pay.** A paid project plan answers with a checkout link that you open and pay.
+
+## Next
+
+- [Configure MCP](./setup.md)
+- [Shape a project](./shape.md) · [Go live](./go-live.md) · [Tools](./tools.md)
+- Without an agent: [CLI overview](../cli/overview.md)

package/docs/mcp/setup.md

@@ -12,8 +12,8 @@ projects. The server is the same everywhere; only the host config file changes.
 ## Prerequisites
 
 - **Node.js 20+** on the machine that runs the agent
-- Signed in to APItoGo: run `npx @lukoweb/apitogo login` once in a terminal. Or give the server API
-  credentials (API key id and secret from [apitogo.com](https://apitogo.com)) in its env.
+- Signed in to APItoGo: run `apitogo login` once in a terminal. Or give the server API credentials
+  (API key id and secret from [apitogo.com](https://apitogo.com)) in its env.
 
 ## Shared server definition
 
@@ -22,9 +22,12 @@ Every host launches the same stdio process:
 | Field   | Value                                                |
 | ------- | ---------------------------------------------------- |
 | Command | `npx`                                                |
-| Args    | `-y`, `@lukoweb/apitogo-mcp`                         |
+| Args    | `-y`, `@lukoweb/apitogo-mcp@latest`                  |
 | Env     | Optional: `APITOGO_API_KEY_ID`, `APITOGO_API_SECRET` |
 
+Keep `@latest` in the package name: without it npx can start an older copy it has kept from an
+earlier run, with tools that no longer match this guide.
+
 The tools run the `apitogo` CLI the project installed (`node_modules/@lukoweb/apitogo`), or the
 latest one through npx in a folder without it. Optional env: `APITOGO_API_KEY_ID` and
 `APITOGO_API_SECRET` instead of `apitogo login`, `APITOGO_API_URL`, and `APITOGO_CLI_PATH` (a local
@@ -44,7 +47,7 @@ Add to `~/.cursor/mcp.json` (user) or `.cursor/mcp.json` (project):
   "mcpServers": {
     "apitogo": {
       "command": "npx",
-      "args": ["-y", "@lukoweb/apitogo-mcp"],
+      "args": ["-y", "@lukoweb/apitogo-mcp@latest"],
       "env": {
         "APITOGO_API_KEY_ID": "apk_...",
         "APITOGO_API_SECRET": "..."
@@ -70,7 +73,7 @@ Edit the Claude Desktop MCP config (same `mcpServers` shape as Cursor):
   "mcpServers": {
     "apitogo": {
       "command": "npx",
-      "args": ["-y", "@lukoweb/apitogo-mcp"],
+      "args": ["-y", "@lukoweb/apitogo-mcp@latest"],
       "env": {
         "APITOGO_API_KEY_ID": "apk_...",
         "APITOGO_API_SECRET": "..."
@@ -88,7 +91,7 @@ Fully quit and reopen Claude Desktop after saving.
 
 ```bash
 claude mcp add --scope user --env APITOGO_API_KEY_ID=apk_... --env APITOGO_API_SECRET=... \
-  apitogo -- npx -y @lukoweb/apitogo-mcp
+  apitogo -- npx -y @lukoweb/apitogo-mcp@latest
 ```
 
 **Project scope** (committed `.mcp.json` — use `${VAR}` for secrets):
@@ -96,7 +99,7 @@ claude mcp add --scope user --env APITOGO_API_KEY_ID=apk_... --env APITOGO_API_S
 ```bash
 claude mcp add --scope project --env APITOGO_API_KEY_ID=${APITOGO_API_KEY_ID} \
   --env APITOGO_API_SECRET=${APITOGO_API_SECRET} \
-  apitogo -- npx -y @lukoweb/apitogo-mcp
+  apitogo -- npx -y @lukoweb/apitogo-mcp@latest
 ```
 
 Or hand-edit `.mcp.json` in the project root:
@@ -107,7 +110,7 @@ Or hand-edit `.mcp.json` in the project root:
     "apitogo": {
       "type": "stdio",
       "command": "npx",
-      "args": ["-y", "@lukoweb/apitogo-mcp"],
+      "args": ["-y", "@lukoweb/apitogo-mcp@latest"],
       "env": {
         "APITOGO_API_KEY_ID": "${APITOGO_API_KEY_ID}",
         "APITOGO_API_SECRET": "${APITOGO_API_SECRET}"
@@ -128,7 +131,7 @@ Edit `~/.codex/config.toml` (or project `.codex/config.toml` in a trusted projec
 ```toml
 [mcp_servers.apitogo]
 command = "npx"
-args = ["-y", "@lukoweb/apitogo-mcp"]
+args = ["-y", "@lukoweb/apitogo-mcp@latest"]
 
 [mcp_servers.apitogo.env]
 APITOGO_API_KEY_ID = "apk_..."
@@ -142,9 +145,9 @@ Restart Codex / open a new session. See [Codex MCP docs](https://developers.open
 
 Any client that supports **stdio** MCP can run APItoGo:
 
-1. Set command `npx`, args `["-y", "@lukoweb/apitogo-mcp"]`
-2. Sign in with `npx @lukoweb/apitogo login`, or pass `APITOGO_API_KEY_ID` and `APITOGO_API_SECRET`
-   in the server env
+1. Set command `npx`, args `["-y", "@lukoweb/apitogo-mcp@latest"]`
+2. Sign in with `apitogo login`, or pass `APITOGO_API_KEY_ID` and `APITOGO_API_SECRET` in the server
+   env
 3. Restart the host and confirm tools load
 
 Examples: Windsurf, VS Code Copilot Chat MCP, custom MCP clients — follow that product’s “add stdio
@@ -158,9 +161,11 @@ In a new agent chat:
    `apitogo_create`, `apitogo_deploy` and `apitogo_status`.
 2. Ask it for the status of your project; it calls `apitogo_status`.
 
-If the server fails to start: confirm Node 20+ and that `npx -y @lukoweb/apitogo-mcp` works in a
-terminal. If a tool says you are not logged in, run `npx @lukoweb/apitogo login` or check the API
-key id and secret.
+If the server fails to start: confirm Node 20+ and that `npx -y @lukoweb/apitogo-mcp@latest` works
+in a terminal. If the agent shows many more tools than the ones in [Tools](./tools.md), or asks for
+an API key although you are logged in, the host is running an old copy: add `@latest` as above and
+restart the host. If a tool says you are not logged in, run `apitogo login` or check the API key id
+and secret.
 
 ## Next
 

package/docs/mcp/shape.md

@@ -69,8 +69,8 @@ set yourself; see [Plans](../configuration/plans.md) and the
 
 - **`apitogo_check`** finds mistakes in the config and its files before a deploy. With `offline` it
   asks the platform nothing.
-- To see the portal locally, run `npx apitogo run` in the folder yourself; it keeps running, so it
-  is not an MCP tool.
+- To see the portal locally, run `apitogo run` in the folder yourself; it keeps running, so it is
+  not an MCP tool.
 
 ## Next