Server providing Argo CD integration for MCP clients.
Nothing to run from here
Lizard is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
29
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Run isolated code and manage apps, databases and deployments on Lizard (lizard.build).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lizard-mcp https://employ-woman-g1q2.us-east-1.onlizard.com/mcp
# 2 — ask your agent for something these tools do
# domain_attach, domain_verify, domain_delete and 26 more
Lizard costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LBAll 1 server
lizard-build1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http lizard-mcp https://employ-woman-g1q2.us-east-1.onlizard.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — the only sign-in is its publisher’s own, with OAuth.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Every app already gets a *.onlizard.com domain automatically on its first deploy (check service_show's domain field before calling this — do not invent or guess a hostname). Only call this tool when the user explicitly wants to attach their own custom domain (pass hostname), or when service_show…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| hostname | string | no | Custom hostname to attach; omit to generate a default subdomain |
| port | integer | no | — |
| force | boolean | no | Move the domain here if it's attached to another of your services |
Use this when the user wants to verify DNS configuration for a custom domain attached to a Lizard service.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| hostname | string | yes | — |
Use this when the user wants to remove a custom domain from a Lizard service. This is destructive and requires explicit confirmation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| hostname | string | yes | — |
| confirm | boolean | yes | Must be true to proceed; there is no interactive confirmation in MCP |
Create a new workspace when the user asks for one. Check workspace_list first. Each call creates another workspace; retries do not reuse the first one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Delete a project when its owner explicitly asks. Stops its services and moves the project to trash for three days. Requires the user's confirmation; do not call this to delete only one service.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project name, slug, or ID; use an ID if names are ambiguous |
| confirm | boolean | yes | Set only after the user approves deleting this project |
Use this when you need to identify the currently authenticated Lizard user, e.g. before asking which workspace or project to act on.
No parameter schema on file.
Use this when the user wants to see which Lizard workspaces they belong to, or needs a workspace ID to scope a project lookup.
No parameter schema on file.
Use this when the user wants to see their Lizard projects, optionally filtered to one workspace.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Filter to this workspace ID |
Use this when the user wants to create a brand-new empty Lizard project to hold services. Calling this again creates another project, even with the same name — it does not update an existing one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Project name |
| workspaceId | string | yes | Workspace to create the project in |
Use this when the user needs to know which deployment regions are available before creating a service or addon.
No parameter schema on file.
Use this when the user wants to see all apps and addons in a Lizard project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project name, slug, or ID |
Use this when the user wants details about a single Lizard service (app or addon) — status, config, resource limits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
Use this when the user wants to create a new empty Lizard service, or deploy a GitHub repository as a new service. Omit repoUrl for an empty service you configure later; provide repoUrl to deploy that repo immediately. Calling this again creates another service, even with the same name — it does…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| name | string | yes | Service name |
| region | string | yes | Deployment region code — call region_list first if unsure of valid values, do not guess |
| repoUrl | string | no | GitHub repo URL — when provided, this becomes a deploy of that repo |
| containerPort | integer | no | — |
| envVars | object | no | — |
| skipInitialDeploy | boolean | no | With repoUrl: attach the repo but skip the initial build |
Use this when the user wants to provision a managed database or storage addon (Postgres, Redis, or S3) in a Lizard project. Calling this again creates another addon, even with the same name — it does not update an existing one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| type | string | yes | — |
| region | string | yes | Deployment region code — call region_list first if unsure of valid values, do not guess |
| name | string | no | Stable reference key for ${{name.KEY}} templates |
Use this when the user wants to rename an existing Lizard service.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| name | string | yes | New name |
Use this when the user wants to permanently delete a Lizard service (app or addon). This is destructive and cannot be undone — requires explicit confirmation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| confirm | boolean | yes | Must be true to proceed; there is no interactive confirmation in MCP |
Use this when the user asks whether a Lizard service (app or Postgres/Redis database) is serverless, i.e. sleeps when idle: returns enabled, idleMinutes, how many times it slept and woke, and the last error if it could not sleep.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project name, slug, or ID |
| service | string | yes | App or database name or ID |
Use this when the user wants a Lizard service to be serverless (sleep when idle) or always on. On: with no traffic for idleMinutes (5-1440, default 15) it sleeps with its memory saved, costs almost nothing, and the next request or connection wakes it in about a second. Turning it on restarts the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | Project name, slug, or ID |
| service | string | yes | App or database name or ID |
| enabled | boolean | yes | true: sleep when idle; false: always on |
| idleMinutes | integer | no | Minutes without traffic before it sleeps |
Use this when the user wants to change replica count, CPU, memory, or storage limits for a Lizard service.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| replicas | integer | no | Apps only |
| cpu | no | CPU cores, apps only | |
| memory | integer | no | Memory in MB, apps only |
| storage | no | Storage in MB, addons only, grow-only |
Use this when the user wants to know which container port a Lizard app is listening on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
Use this when the user wants to change the container port a Lizard app listens on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| containerPort | integer | yes | — |
Use this when the user wants to change a Lizard service's build/deploy configuration — source repo, branch, build command, start command, etc.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| sourceType | string | no | — |
| repoUrl | string | no | — |
| branch | string | no | — |
| rootDirectory | string | no | — |
| buildCommand | string | no | — |
| watchPatterns | array | no | — |
| dockerfilePath | string | no | — |
| startCommand | string | no | — |
| preDeployCommand | string | no | — |
| containerPort | integer | no | — |
| force | boolean | no | Skip the optimistic-concurrency revision check |
Use this when the user wants to trigger a new deployment of an existing Lizard service (rebuild and redeploy current source). Returns immediately once the build is triggered — use deploy_events to check progress. Each call starts another build, even if called again immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
Use this when the user wants to restart a running Lizard service without rebuilding it. Returns immediately. Each call restarts it again, even if called again immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
Use this when the user wants to see recent deploy/build history and current replica status for a Lizard service.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
Use this when the user wants to see recent log output from a Lizard service or a specific build. Returns a bounded snapshot, not a live stream.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | yes | — |
| limit | integer | no | — |
| level | string | no | Filter runtime logs by level |
| build | boolean | no | Fetch build logs instead of runtime logs |
| buildId | string | no | Specific build ID; defaults to the most recent build |
Use this when the user wants CPU, memory, or network metrics for a Lizard app or addon over a time range.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project | string | yes | — |
| service | string | no | Omit for project-level live metrics |
| range | string | no | — |
Use this when a tool fails with PAYMENT_REQUIRED, or the user asks about their plan, trial or bill.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | no | Read the plan of this workspace's owner instead of your own |
Use this when the user wants a cost/billing summary for a Lizard workspace, including current usage and live spend.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| workspaceId | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lizard or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lizard can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.