Copy page

MCP

Configure MCP in your agent

Connect @lukoweb/apitogo-mcp to your AI agent so it can create, shape and deploy APItoGo 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 apitogo login once in a terminal. Or give the server API credentials (API key id and secret from apitogo.com) in its env.

Shared server definition

Every host launches the same stdio process:

Field	Value
Command	npx
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 doc-tool checkout, for CLI development).

The server runs the commands in the folder your host starts it in, unless a tool gets a directory. Start it in your workspace, or tell the agent where the project is.

Never commit secrets. Prefer host env blocks or ${VAR} expansion where the client supports it.

Cursor

Add to ~/.cursor/mcp.json (user) or .cursor/mcp.json (project):

Code
{
  "mcpServers": {
    "apitogo": {
      "command": "npx",
      "args": ["-y", "@lukoweb/apitogo-mcp@latest"],
      "env": {
        "APITOGO_API_KEY_ID": "apk_...",
        "APITOGO_API_SECRET": "..."
      }
    }
  }
}

Restart Cursor (or reload MCP). Confirm the apitogo server is connected in MCP settings.

Claude Desktop

Edit the Claude Desktop MCP config (same mcpServers shape as Cursor):

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json

Code
{
  "mcpServers": {
    "apitogo": {
      "command": "npx",
      "args": ["-y", "@lukoweb/apitogo-mcp@latest"],
      "env": {
        "APITOGO_API_KEY_ID": "apk_...",
        "APITOGO_API_SECRET": "..."
      }
    }
  }
}

Fully quit and reopen Claude Desktop after saving.

Claude Code

CLI (user scope — all projects):

Code
claude mcp add --scope user --env APITOGO_API_KEY_ID=apk_... --env APITOGO_API_SECRET=... \
  apitogo -- npx -y @lukoweb/apitogo-mcp@latest

Project scope (committed .mcp.json — use ${VAR} for secrets):

Code
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@latest

Or hand-edit .mcp.json in the project root:

Code
{
  "mcpServers": {
    "apitogo": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@lukoweb/apitogo-mcp@latest"],
      "env": {
        "APITOGO_API_KEY_ID": "${APITOGO_API_KEY_ID}",
        "APITOGO_API_SECRET": "${APITOGO_API_SECRET}"
      }
    }
  }
}

User/local scope without a project file lives in ~/.claude.json. Start a new Claude Code session after changing config. Approve project-scoped servers when prompted.

OpenAI Codex

Edit ~/.codex/config.toml (or project .codex/config.toml in a trusted project). The key must be mcp_servers (not mcpServers):

Code
[mcp_servers.apitogo]
command = "npx"
args = ["-y", "@lukoweb/apitogo-mcp@latest"]

[mcp_servers.apitogo.env]
APITOGO_API_KEY_ID = "apk_..."
APITOGO_API_SECRET = "..."

You can also use codex mcp add if your Codex version supports it, then confirm the TOML entry. Restart Codex / open a new session. See Codex MCP docs.

Other MCP hosts

Any client that supports stdio MCP can run APItoGo:

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 server” UI and paste the same command/args/env.

Verify

In a new agent chat:

1. Ask the agent to list the APItoGo tools: they all start with apitogo_, such as 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@latest works in a terminal. If the agent shows many more tools than the ones in Tools, 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

• Shape a project — make and change the project folder
• Go live — deploy
• Tools — every tool