What can you do with this server?

The lattice-mcp server provides direct, typed access to the Lattice container orchestration platform, with 133 tools to monitor and manage the entire infrastructure. Key capabilities: * Fleet overview and health – Retrieve fleet-wide status, API health, version info, and detect anomalies like restart loops, unhealthy containers, or offline workers. * Worker management – List, inspect, reboot, upgrade workers; start/stop all containers on a worker; view CPU/memory/disk/network metrics; register and delete workers. * Stack lifecycle – Create, deploy, update, export/import stacks; manage compose YAML; save as templates; approve deployments. * Container operations – Full lifecycle: start, stop, restart, kill, pause, unpause, remove, recreate containers; view logs, events, and per-container metrics. * Deployment management – List, inspect, rollback deployments; view deployment logs; approve pending deployments; manage CI deploy tokens. * Databases – Provision and manage MySQL, MariaDB, PostgreSQL instances; start/stop/restart database containers; create/restore/delete snapshots; view credentials (audited), logs, and events; open interactive SQL console. * Backup destinations – Configure, test, and manage backup targets (e.g., S3) for database snapshots. * Container registries – Add, update, delete, and test registries; browse repositories and image tags for deployable versions. * Networking and volumes – Create, list, and delete Docker networks and volumes on workers. * Environment variables and templates – Manage global environment variables (with secret masking) and stack templates. * API and deploy tokens – Create, list, delete API tokens and CI deploy tokens. * Audit and security – Search audit logs by user/action/resource; manage users, SSO/SMTP, notifications; secrets and tokens automatically masked (override with LATTICE_ALLOW_SECRET_VALUES=1). * Webhooks – Create, update, delete, and test outbound event webhooks. * Self-update – Trigger lattice-api and lattice-web container updates. * Search and discovery – Search across workers, stacks, and containers by name; aggregated fleet metrics; runner version drift.

Which integrations are available for this server?

Allows provisioning and managing MariaDB database instances within the Lattice platform. Allows provisioning and managing MySQL database instances within the Lattice platform.

How do I use lattice-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@lattice-mcp List all stacks with their status" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

lattice-mcp

by aidenappl

Overview Schema Related Servers Score Discussions

JavaScript

Remote

The lattice-mcp server provides direct, typed access to the Lattice container orchestration platform, with 133 tools to monitor and manage the entire infrastructure. Key capabilities:

Fleet overview and health – Retrieve fleet-wide status, API health, version info, and detect anomalies like restart loops, unhealthy containers, or offline workers.
Worker management – List, inspect, reboot, upgrade workers; start/stop all containers on a worker; view CPU/memory/disk/network metrics; register and delete workers.
Stack lifecycle – Create, deploy, update, export/import stacks; manage compose YAML; save as templates; approve deployments.
Container operations – Full lifecycle: start, stop, restart, kill, pause, unpause, remove, recreate containers; view logs, events, and per-container metrics.
Deployment management – List, inspect, rollback deployments; view deployment logs; approve pending deployments; manage CI deploy tokens.
Databases – Provision and manage MySQL, MariaDB, PostgreSQL instances; start/stop/restart database containers; create/restore/delete snapshots; view credentials (audited), logs, and events; open interactive SQL console.
Backup destinations – Configure, test, and manage backup targets (e.g., S3) for database snapshots.
Container registries – Add, update, delete, and test registries; browse repositories and image tags for deployable versions.
Networking and volumes – Create, list, and delete Docker networks and volumes on workers.
Environment variables and templates – Manage global environment variables (with secret masking) and stack templates.
API and deploy tokens – Create, list, delete API tokens and CI deploy tokens.
Audit and security – Search audit logs by user/action/resource; manage users, SSO/SMTP, notifications; secrets and tokens automatically masked (override with LATTICE_ALLOW_SECRET_VALUES=1).
Webhooks – Create, update, delete, and test outbound event webhooks.
Self-update – Trigger lattice-api and lattice-web container updates.
Search and discovery – Search across workers, stacks, and containers by name; aggregated fleet metrics; runner version drift.

lattice-mcp

Model Context Protocol server for Lattice, the container orchestration platform that runs every appleby.cloud service. Gives Claude Code direct, typed access to workers, stacks, containers, deployments, databases, registries, networks, volumes and instance configuration.

appleby.cloud platform · MCP server · published to npm as lattice-mcp · consumed via npx -y lattice-mcp

Overview

lattice-mcp is a single-file Node ESM program (index.js) that speaks MCP over stdio and translates tool calls into HTTP requests against the lattice-api admin surface. It exposes 136 typed tools and holds no business logic, caching or state of its own — every behaviour (pagination, validation, side effects) comes from lattice-api.

Once configured, ask Claude Code things like:

"What's the status of all stacks?"
"Show me logs for the forta-api container"
"Which containers are unhealthy?" (lattice_get_anomalies is the best first call)
"Deploy stack 5" / "Rollback the last deployment on stack 12"
"What image tags can I deploy from the registry?"

Related MCP server: Claude Orchestrator MCP

Role in the appleby.cloud ecosystem

Repo	Relationship
`lattice-api`	The API this wraps — its route table is the source of truth for tool coverage.
`lattice-web`	Next.js dashboard over the same API.
`lattice-runner`	Agent on each worker VM; WebSocket back to `lattice-api`.
`monitor-mcp` / `forta-mcp` / `keyring-mcp` / `openbucket-mcp`	Sibling MCP servers, same single-file structure.

Tech stack

Node ≥18 (needs global fetch and AbortSignal.timeout), ESM ("type": "module").
@modelcontextprotocol/sdk ^1.29.0 — McpServer + StdioServerTransport.
zod ^4.4.3 for argument schemas (a declared dependency as of 1.1.1).
No build step, no bundler. node --check index.js is the only static gate.

Getting started

Prerequisites

Node ≥18.
A Lattice API URL and API token. Generate a token from the Lattice web dashboard under Settings > API Tokens.

Setup

Quickest — interactive setup writes the lattice block into ~/.mcp.json:

npx lattice-mcp --setup

Or configure it manually in ~/.mcp.json:

{
  "mcpServers": {
    "lattice": {
      "command": "npx",
      "args": ["-y", "lattice-mcp"],
      "env": {
        "LATTICE_API_URL": "https://lattice-api.appleby.cloud",
        "LATTICE_API_TOKEN": "your-api-token"
      }
    }
  }
}

Restart Claude Code after setup so the new server and tools are picked up.

Environment variables

Variable	Required	Description
`LATTICE_API_URL`	Yes	Lattice API base URL
`LATTICE_API_TOKEN`	Yes	Bearer token for authentication (sent on every request)
`LATTICE_ALLOW_SECRET_VALUES`	No	Set to `1` to disable secret masking in responses

Secret values are masked

Every response is passed through a masking step before it reaches the model. Anything that looks like a credential keeps its first two characters and loses the rest to a fixed-width tail — supersecret becomes su**********.

That is enough to tell two credentials apart, or to confirm a rotation actually changed something, and not enough to use. The tail is a fixed width so the mask does not reveal the real length.

This covers container and stack env_vars, compose_yaml environment blocks, global env vars flagged is_secret, database passwords, and freshly minted deploy/worker/API tokens. Variable names are left readable — they are the useful half — as are addresses like TOKEN_URL and AUTH_URL.

This server authenticates as a Lattice admin, and the API only masks global env vars server-side for non-admin callers. Without this step, lattice_list_env_vars returns every secret value in plaintext.

Set LATTICE_ALLOW_SECRET_VALUES=1 to turn masking off if you genuinely need a working value.

Development

Command	What it does
`node index.js --setup`	Interactive setup — writes the `lattice` block into `~/.mcp.json`
`npm install`	Install dependencies (not vendored)
`node --check index.js`	Syntax gate — the only static check that exists
`LATTICE_API_URL=… LATTICE_API_TOKEN=… node index.js`	Run the server on stdio
`grep -c 'server.tool(' index.js`	Confirm the tool count (should be 136)
`npm publish`	Publish to npm — this is deployment (requires 2FA passkey from an interactive terminal)

Tools

All 136 tools, grouped as they appear in index.js. ⚠️ marks destructive tools; their descriptions state the blast radius.

Overview & health

Tool	Description
`lattice_overview`	Fleet overview — worker/stack/container counts, failed stacks, CPU/memory
`lattice_health`	API health and database connectivity
`lattice_get_version`	Deployed lattice-api version string — check deploy drift against GitHub tags

Workers

Tool	Description
`lattice_list_workers`	List workers with status, IP, versions, heartbeat
`lattice_get_worker`	Detailed worker info including metrics
`lattice_get_worker_metrics`	CPU, memory, disk, network metrics
`lattice_reboot_worker`	Reboot a worker machine
`lattice_upgrade_worker`	Upgrade worker runner to latest
`lattice_stop_all_worker`	Stop all containers on a worker
`lattice_start_all_worker`	Start all containers on a worker

Stacks

Tool	Description
`lattice_list_stacks`	List stacks with status and worker assignment
`lattice_get_stack`	Full stack details including compose YAML
`lattice_deploy_stack`	Deploy a stack (all or specific containers)
`lattice_restart_stack`	Restart all containers in a stack
`lattice_stop_stack`	Stop all containers in a stack
`lattice_start_stack`	Start all containers in a stack
`lattice_update_stack`	Update stack configuration

Containers

Tool	Description
`lattice_list_containers`	List containers with status, image, ports, health
`lattice_get_container`	Full container details
`lattice_get_container_logs`	Recent container logs (stdout/stderr); `offset` paginates into older logs, filter by `stream`/`worker_id`
`lattice_get_container_lifecycle`	Lifecycle events (start, stop, health changes)
`lattice_start_container`	Start a stopped container
`lattice_stop_container`	Stop a running container
`lattice_restart_container`	Restart a container
`lattice_kill_container`	Force kill a container
`lattice_pause_container`	Pause a running container
`lattice_unpause_container`	Unpause a paused container
`lattice_remove_container`	Remove a container ⚠️
`lattice_recreate_container`	Remove and recreate a container ⚠️

Deployments

Tool	Description
`lattice_list_deployments`	List deployments with status and timing
`lattice_get_deployment`	Deployment details with container-level status
`lattice_get_deployment_logs`	Pull, create, start, swap events with timing
`lattice_rollback_deployment`	Rollback to previous state ⚠️

Instance self-update

Tool	Description
`lattice_update_api`	Trigger the Lattice API container to self-update
`lattice_update_web`	Trigger the Lattice web container to update

Audit & API tokens

Tool	Description
`lattice_get_audit_log`	Audit log entries (who did what, when); filter by `user_id`/`action`/`resource_type`, `offset` paginates
`lattice_list_api_tokens`	List API tokens
`lattice_create_api_token`	Create a new API token
`lattice_delete_api_token`	Delete an API token ⚠️

Database instances

Tool	Description
`lattice_list_database_instances`	List managed databases (filter by worker, engine, status)
`lattice_get_database_instance`	Full instance config
`lattice_create_database_instance`	Provision mysql/mariadb/postgres on a worker (omit `port` to auto-allocate)
`lattice_update_database_instance`	Update config, limits, snapshot schedule
`lattice_delete_database_instance`	Destroy an instance and its data volume ⚠️ — async; `force` only for an offline worker
`lattice_database_action`	start / stop / restart / remove ⚠️ — `remove` is container-only, the data volume survives
`lattice_get_database_connection`	Host, port, database and username — no secrets
`lattice_reveal_database_credentials`	Reveal live credentials (audited; root only on request)
`lattice_get_database_credentials`	Deprecated — root credentials via GET; use the reveal tool
`lattice_get_database_events`	Lifecycle history — start here when a database looks wrong
`lattice_get_database_backup_posture`	3-2-1 standing — copies, media, off-site, with warnings
`lattice_get_database_runs`	Scheduled snapshot attempts, including skipped slots and why
`lattice_get_database_metrics`	CPU/memory samples for a database (no containers-table row needed)
`lattice_get_database_logs`	Container stdout/stderr
`lattice_get_database_lifecycle_logs`	Worker lifecycle messages, incl. why a create failed
`lattice_open_database_console`	Authorise an interactive SQL console session
`lattice_list_database_snapshots`	Snapshots for an instance
`lattice_create_database_snapshot`	Take a snapshot now
`lattice_restore_database_snapshot`	Restore from a snapshot ⚠️
`lattice_delete_database_snapshot`	Delete a snapshot and its remote file ⚠️

Worker port allocation

Tool	Description
`lattice_get_worker_port_availability`	Claimed host ports on a worker, plus a free suggestion

Backup destinations

Tool	Description
`lattice_list_backup_destinations`	List backup destinations
`lattice_get_backup_destination`	One destination's configuration
`lattice_create_backup_destination`	Create a destination
`lattice_update_backup_destination`	Update a destination
`lattice_delete_backup_destination`	Delete a destination ⚠️
`lattice_test_backup_destination`	Test connectivity without writing a backup (requires a connected `worker_id`)

Registries

Tool	Description
`lattice_list_registries`	Configured container registries
`lattice_create_registry`	Add a registry
`lattice_update_registry`	Update a registry
`lattice_delete_registry`	Delete a registry ⚠️
`lattice_test_registry`	Test a saved registry's stored credentials
`lattice_test_registry_inline`	Test registry credentials before saving
`lattice_list_registry_repositories`	What images exist
`lattice_list_registry_tags`	What versions are deployable

Discovery & diagnostics

Tool	Description
`lattice_search`	Search workers, stacks and containers in one call
`lattice_get_anomalies`	Restart loops, unhealthy containers, offline workers — best first call
`lattice_get_fleet_metrics`	Aggregated fleet CPU/memory/disk/network
`lattice_get_versions`	Runner versions and what's outdated
`lattice_refresh_versions`	Re-poll every worker for its current runner version
`lattice_get_container_metrics`	Per-container metrics over time
`lattice_get_self`	Which user the token authenticates as

Stacks — lifecycle, compose & deploy tokens

Tool	Description
`lattice_create_stack`	Create an empty stack
`lattice_delete_stack`	Delete a stack and all its containers ⚠️
`lattice_get_stack_containers`	Containers in a stack
`lattice_update_stack_compose`	Replace a stack's compose YAML
`lattice_sync_stack_compose`	Reconcile container records against stored compose YAML
`lattice_import_compose`	Create a stack from compose YAML
`lattice_export_stack`	Export a stack's full definition as portable JSON
`lattice_import_stack_export`	Recreate a stack from an export document
`lattice_save_stack_as_template`	Save a stack as a reusable template
`lattice_list_deploy_tokens`	CI deploy tokens — `last_used_at` shows whether CI reaches Lattice
`lattice_create_deploy_token`	Create a CI deploy token
`lattice_delete_deploy_token`	Delete a CI deploy token ⚠️
`lattice_approve_deployment`	Approve a deployment awaiting approval

Container definitions

Tool	Description
`lattice_create_container`	Add a container definition to a stack
`lattice_update_container`	Update a container definition
`lattice_delete_container`	Delete definition and its running container ⚠️

Workers — registration, tokens, volumes, networks

Tool	Description
`lattice_create_worker`	Register a worker
`lattice_update_worker`	Update a worker's name, hostname, IP, status, labels
`lattice_delete_worker`	Delete a worker ⚠️
`lattice_get_worker_container_stats`	Live per-container stats from one worker
`lattice_list_worker_tokens`	Worker registration tokens
`lattice_create_worker_token`	Create a registration token for a worker
`lattice_delete_worker_token`	Delete a worker token ⚠️
`lattice_list_worker_volumes`	Docker volumes on a worker
`lattice_create_worker_volume`	Create a Docker volume on a worker
`lattice_delete_worker_volume`	Delete a Docker volume ⚠️
`lattice_list_worker_networks`	Docker networks on a worker
`lattice_create_worker_network`	Create a Docker network on a worker
`lattice_delete_worker_network`	Delete a Docker network ⚠️
`lattice_list_all_networks`	Every tracked network across the fleet
`lattice_delete_network`	Delete a tracked network by Lattice ID ⚠️
`lattice_force_remove_container`	Force-remove a wedged container ⚠️

Env vars, templates & webhooks

Tool	Description
`lattice_list_env_vars`	Global `${VAR}` interpolation values (secrets masked)
`lattice_create_env_var`	Create a global environment variable
`lattice_update_env_var`	Update a global environment variable
`lattice_delete_env_var`	Delete a global environment variable ⚠️
`lattice_list_templates`	Saved stack templates
`lattice_create_template`	Create a stack template
`lattice_delete_template`	Delete a stack template ⚠️
`lattice_list_webhooks`	Outbound event webhooks
`lattice_create_webhook`	Create an outbound webhook
`lattice_update_webhook`	Update a webhook
`lattice_delete_webhook`	Delete a webhook ⚠️
`lattice_test_webhook`	Send a test payload to a webhook

Users & instance configuration

Tool	Description
`lattice_list_users`	List Lattice users with roles and status
`lattice_create_user`	Create a local Lattice user
`lattice_update_user`	Update a user's name, role or active flag ⚠️
`lattice_delete_user`	Delete a Lattice user ⚠️
`lattice_get_sso_config`	Get the Forta SSO configuration
`lattice_update_sso_config`	Update SSO config ⚠️ (can lock out SSO users)
`lattice_get_smtp_config`	Get the SMTP configuration
`lattice_update_smtp_config`	Update the SMTP configuration
`lattice_test_smtp`	Send a test email with the saved SMTP config
`lattice_get_notification_prefs`	Per-event notification preferences
`lattice_update_notification_prefs`	Update notification preferences

Project structure

Everything lives in one file:

Path	Role
`index.js`	The whole server: `--setup` flow, config read, `api()` HTTP helper, `text()`/`body()` helpers, all 136 `server.tool(...)` registrations, transport connect.
`package.json`	npm metadata; `bin.lattice-mcp` → `index.js`.
`AGENTS.md`	Contributor/agent guide — conventions, handler contracts, verification.
`README.md`	This file.

Deployment

Published to npm as lattice-mcp (public). Consumers run npx -y lattice-mcp, which resolves the latest published version — so publishing is deployment, and a running MCP server must be restarted to pick up a new version. npm publish requires 2FA via passkey from an interactive terminal.

Contributing & further reading

Read AGENTS.md before changing code — it documents the one-shape tool pattern, the body()/api() helpers, the "read the handler before adding a tool" rule, and the verification steps. Related repos: lattice-api, lattice-web, lattice-runner.

License

MIT

Install Server

license - permissive license

quality

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Tools

View all tools

Related MCP Servers

Modal MCP
CI/CD & DevOps Cloud Platforms Networking & Infrastructure
george-bobby
A
license
A
quality
B
maintenance
An MCP server for managing Modal — apps, containers, volumes, and secrets — and for deploying & running Modal apps directly from Claude Code and other MCP clients.
Updated 2 months ago (2026-06-11 17:03 UTC)
26
MIT
Claude Orchestrator MCP
Agent Orchestration Project Management Developer Tools
TerminalGravity
F
license
-
quality
D
maintenance
An MCP server for coordinating multiple Claude Code sessions across related projects.
Updated 7 months ago (2026-01-16 16:18 UTC)
agent-network
Agent Orchestration Communication Coding Agents
sharifli4
A
license
-
quality
D
maintenance
MCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.
Updated 5 months ago (2026-03-13 07:21 UTC)
MIT
Lattice MCP Server
ERP Systems Workplace & Productivity Project Management
EoinFalconer
A
license
-
quality
D
maintenance
An MCP server that exposes the Lattice Talent API as tools, enabling AI assistants like Claude to read and manage people data, goals, feedback, reviews, and more.
Updated 5 months ago (2026-03-23 14:16 UTC)
46
MIT

View all related MCP servers

Related MCP Connectors

microservices.sh
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
DataDoe MCP
Hosted Amazon Seller and Vendor MCP server for Claude, ChatGPT, Cursor, Codex, Gemini, Copilot.
agentcentral
Hosted Amazon Seller Central and Amazon Ads MCP server for Claude, ChatGPT, Cursor, and agents.

View all MCP Connectors

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aidenappl/lattice-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

lattice-mcp

Overview

Role in the appleby.cloud ecosystem

Tech stack

Getting started

Prerequisites

Setup

Environment variables

Secret values are masked

Development

Tools

Overview & health

Workers

Stacks

Containers

Deployments

Instance self-update

Audit & API tokens

Database instances

Worker port allocation

Backup destinations

Registries

Discovery & diagnostics

Stacks — lifecycle, compose & deploy tokens

Container definitions

Workers — registration, tokens, volumes, networks

Env vars, templates & webhooks

Users & instance configuration

Project structure

Deployment

Contributing & further reading

License

Maintenance

Resources

Looking for Admin?

Tools

Related MCP Servers

Modal MCP

Claude Orchestrator MCP

agent-network

Lattice MCP Server

Related MCP Connectors

Latest Blog Posts

MCP directory API