macaulay2-mcp
Related Servers
Alternatives to macaulay2-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables agents to run and manage SageMath computations through a persistent kernel over stdio, including executing code, polling long-running jobs, interrupting or resetting sessions, running files, and driving notebooks.7MIT
- AlicenseNot gradedqualityCmaintenanceA local stdio Model Context Protocol server that exposes exact arithmetic, algebra, calculus, matrices, and Sage script execution to AI clients without requiring accounts, API keys, or cloud services.MIT
- AlicenseNot gradedqualityCmaintenanceEnables zero-install Macaulay2 computations from JupyterLab in a browser, including Groebner bases, resolutions, Betti tables, and package loading via the Model Context Protocol.GPL 3.0
- AlicenseBqualityAmaintenanceA universal mathematics MCP server that gives LLM clients full access to SageMath for symbolic calculus, number theory, linear algebra, and more, with persistent state across tool calls.4020MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for scientific computing with multiple backends (Mathematica, Octave, Python, R, SageMath, etc.) enabling mathematical computation and visualization through AI coding assistants.4-
- AlicenseAqualityCmaintenanceEnables AI assistants to execute Julia code efficiently with persistent sessions, avoiding startup costs and maintaining state across calls.396MIT
TDQS
Scored across 9 tools
Each tool targets a clearly distinct operation: persistent evaluation vs. isolated script execution vs. file import, package management, help, memory, and interrupt. The few potential overlaps (e.g., m2_evaluate vs. m2_import_file) are well-separated by input source and session-state semantics.
All tools use the same m2_ prefix and snake_case, making the set highly readable. Minor deviations from a strict verb_noun pattern appear in m2_session_reset (noun_verb) and single-word tools like m2_help, m2_memory, and m2_interrupt.
The 9 tools are well-scoped for controlling a Macaulay2 session. Each tool covers a discrete need (execute, batch, import, packages, help, reset, memory, interrupt) without redundancy.
The surface covers the full session lifecycle: code evaluation, batch execution, file import, package listing/loading, documentation lookup, kernel reset, memory monitoring, and interruption. No obvious gaps exist for the stated domain, and noted M2 limitations (e.g., no unload) are appropriately handled.