tlaplus-mcp
Related Servers
Alternatives to tlaplus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceIntegrates the Quint formal specification language into LLM workflows for accessible formal verification. It provides tools for type-checking, random simulation, exhaustive model checking, and syntax documentation.62PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityDmaintenanceExposes Salesforce development tools (scan, lint, test, deploy, verify) to AI assistants via the Model Context Protocol, enabling programmatic interaction with Salesforce projects.4 npmMIT
- AlicenseNot gradedqualityFmaintenanceExposes Language Server Protocol (LSP) functionality as Model Context Protocol (MCP) tools, enabling AI clients to programmatically analyze and edit code in any language supported by VS Code.17 npm33MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI models to convert LaTeX snippets to Typst, validate Typst syntax, retrieve documentation chapters, and render Typst code as PNG images.-
- AlicenseAqualityBmaintenanceEnables AI models to use custom tools defined in TypeScript — such as launching applications on the user's computer, reading notes, or calling APIs — exposed over the Model Context Protocol. Includes minimal example tools (current time, greeting, listing and opening installed apps) and connects to clients like opencode, Claude Desktop, or Cursor.444 npmMIT
- AlicenseBqualityAmaintenanceEnables AI agents to write, compose, and check assume-guarantee contracts, including refinement, consistency, compatibility, realizability, and LTL checks, and to use returned counterexamples to fix specifications.39976 PyPIBSD 3-Clause
TDQS
Scored across 9 tools
Each tool has a distinct purpose covering different aspects of TLA+ workflow: parsing, model checking, simulation, coverage, trace generation, state graph analysis, evaluation, translation from PlusCal, and typesetting. No two tools overlap in functionality.
Names follow a consistent pattern with prefixes (tla_, tlc_, pcal_) indicating the tool, followed by a descriptive verb or noun. The only minor inconsistency is 'tla_state_graph' which deals with TLC-generated files, but overall the pattern is clear and predictable.
9 tools is appropriate for a TLA+ toolset, covering essential operations without being too many or too few. Each tool earns its place in the workflow.
The tool set covers the core TLA+ lifecycle: parsing, evaluation, model checking, simulation, coverage, trace generation, state graph analysis, PlusCal translation, and typesetting. Minor gaps exist (e.g., no explicit LTL property checking tool, but tlc_check handles properties; no distributed mode) but the surface is largely complete.