agda-mcp
Related Servers
Alternatives to agda-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server for Agda, providing type checking, go-to-definition, case splitting, auto proof search, and more directly from Claude Code or any MCP client.303-
- AlicenseNot gradedqualityDmaintenanceExposes Language Server Protocol (LSP) tools such as diagnostics, goto definition, find references, symbols, and rename as a stdio MCP server.8MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and interact with VS Code virtual workspaces and live editor buffers, including reading, searching, editing, saving, and diagnostics without shell access.1MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to analyze call graphs, run Grover-ranked code searches, generate boundary test cases, get refactoring suggestions, and inspect quantum backends through stdio JSON-RPC tools.2-
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP-compatible clients to pull real-time language-server data from a running editor instance, including diagnostics, hover/definition/signature info, symbol references, file opening, and workspace-wide renames. This replaces slow tsc and eslint runs with instant feedback, with a matching CLI for agents that shell out instead of registering an MCP server.MIT
- AlicenseNot gradedqualityDmaintenanceA stateful Model Context Protocol server for interactive Agda proof development, enabling persistent sessions with goal-aware proof actions.10 npm1MIT
TDQS
Scored across 18 tools
Most tools map to clearly distinct actions: job lifecycle (cancel/list/await/await_any/status), retrieval (goals/context/contexts/constraints), and mutations (case_split/refine/auto) are well separated. Minor confusion risks remain between agda_retrieve_context vs agda_retrieve_contexts (singular/plural one-vs-many) and between agda_retrieve_goals vs agda_query_metavariables, since goals are metavariables in Agda.
Nearly all names follow the agda_<verb>_<noun> snake_case pattern and job-related tools share a coherent agda_job_* prefix. A few deviate to noun-only or bare-verb forms (agda_server_info, agda_job_status, agda_typecheck, agda_auto), which is readable but slightly inconsistent.
18 tools is on the heavy side but each maps to a real Agda interaction-protocol operation, and the job-management cluster is needed for async/multi-workspace use. Nothing appears obviously redundant, though a few retrieval tools could conceivably be folded together.
The core proof-interaction lifecycle is covered (load, typecheck, goals, context, constraints, case split, refine, auto, normalize, infer, metavariable queries, job control). However, notable Agda operations are missing: 'give' (fill a goal with an expression, distinct from refine) and 'search/about' for lemma discovery, plus no explicit combined goal type-and-context call.