MCP

MCP overview

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 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.

How it fits together

Code
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.
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 · Go live · All tools.

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.

Last modified on November 9, 2026

Configure MCP in your agent Shape a project with MCP

How it fits together

Code

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.

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

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.

MCP overview

How it fits together

The usual flow

What the agent never does

Next

MCP overview

How it fits together

The usual flow

What the agent never does

Next