Lizard MCP

What lizard-build/lizard-mcp MCP server does

The lizard-build/lizard-mcp MCP server gives ChatGPT, Claude, Claude Code, Cursor, Codex, and other MCP clients an interface to Lizard at lizard.build. It can inspect accounts, workspaces, projects, regions, billing information, services, deployments, logs, metrics, secrets, domains, volumes, and Git connections.

Its 33 tools cover common application operations. Agents can create, update, rename, scale, restart, redeploy, and delete services; create add-ons; inspect deployment events; manage secrets; attach and verify domains; resize volumes; connect Git sources; check out revisions; apply configuration as code; and execute shell commands over SSH. The available account tools include identity, workspace, project, region, and billing queries.

How it works

The hosted endpoint accepts MCP requests at /mcp over Streamable HTTP. Each request carries a bearer token. OAuth-capable clients can complete the OAuth 2.1 flow using the server’s advertised metadata, while clients that only provide headers can use a liz_ API key. A fresh server instance is created for each caller’s token, allowing one HTTP process to serve multiple users without sharing authentication state.

The server also supports stdio. In that mode, an MCP client starts dist/stdio.js, and the process uses a token supplied through its environment. Stdio has no browser-based OAuth flow and therefore serves one user per process. The server can start without a token, but tool calls then ask for a key.

Setup and configuration

Install dependencies, build the project, and start the HTTP server with npm install, npm run build, and npm start. Use npm run dev for development with reload. The default HTTP port is 3000. PUBLIC_URL identifies the address clients use and must match the production address for OAuth resource metadata. PLATFORM_URL selects the Lizard API endpoint and defaults to https://lizard.build.

For stdio, configure the client to run node /path/to/lizard-mcp/dist/stdio.js and provide LIZARD_TOKEN with a Lizard API key. LIZARD_API_KEY is also accepted. The hosted deployment URL is documented in the repository and can be used in clients that support remote MCP connections.

Tools and capabilities

Tool names use underscores, such as service_list and logs_tail, rather than dots. Destructive operations require an explicit confirmation argument. This applies to service deletion, secret deletion, domain deletion, and ssh_exec, reducing the chance of accidental removal or command execution.

Billing inspection is read-only. Starting, paying for, or cancelling a plan remains a browser action. When payment is required before an operation can proceed, the tool response includes the platform guidance and structured error details.

Limitations and notes

The lizard-build/lizard-mcp MCP server does not store its own authentication secrets; Lizard validates the bearer token on each request. OAuth is unavailable for spawned stdio processes, which must receive a key through the environment. ChatGPT connections require developer mode and a registered connection. The project includes unit tests, type checking, and manual MCP Inspector documentation for local and live checks.

The repository is licensed under MIT.