A
licenseA
qualityA
maintenanceAn MCP server for managing Modal — apps, containers, volumes, and secrets — and for deploying & running Modal apps directly from Claude Code and other MCP clients.
12
68 PyPI
2
MIT
lattice-mcp
by aidenappl
Related Servers
Alternatives to lattice-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude to orchestrate multiple autonomous Claude Code agents working in parallel across different projects, with tools to dispatch, monitor, and manage their progress.640 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP 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.MIT
- AlicenseNot gradedqualityDmaintenanceAn 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.23 npmMIT
- FlicenseAqualityFmaintenanceAn MCP server for coordinating multiple Claude Code sessions across related projects.11-
- AlicenseAqualityBmaintenanceMCP server for orchestrating coding tasks with frontier-model planning and local execution, enabling manifest validation, plan submission, status checks, cancellation, and report retrieval through Claude Code.6MIT
TDQS
B3.2/5.0
Scored across 133 tools
Disambiguation4/5
Nearly every tool targets a distinct resource and action, and the descriptions carefully disambiguate near-overlaps like container metrics vs worker container stats and database events vs lifecycle logs. A few boundaries remain fuzzy—deprecated get vs reveal credentials, sync vs update compose, and force-remove vs remove—but a careful agent can tell them apart.
Naming Consistency4/5
The set overwhelmingly follows a lattice_<verb>_<noun> snake_case pattern, making behavior predictable. Minor deviations include noun-only names like lattice_health, lattice_overview, and lattice_search, the parameter-based lattice_database_action, and the confusing singular/plural pair lattice_get_version vs lattice_get_versions.
Tool Count1/5
With 133 tools this is far beyond the extreme-mismatch threshold and creates a massive selection surface for an agent. Even though the platform domain is broad, this many individual endpoints is inappropriate for an MCP server and could be consolidated into parameterized resource actions.
Completeness4/5
Coverage is unusually thorough: stacks, containers, workers, databases, snapshots, registries, webhooks, users, tokens, and settings all have CRUD plus lifecycle actions. Minor gaps exist—no get-single webhook/registry/template, no template update, no volume/network update—but list endpoints and sensible workarounds cover them.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive