macaulay2-mcp
Related Servers
Alternatives to macaulay2-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.4014MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for scientific computing with multiple backends (Mathematica, Octave, Python, R, SageMath, etc.) enabling mathematical computation and visualization through AI coding assistants.5-
- AlicenseAqualityBmaintenanceEnables AI assistants to execute Julia code efficiently with persistent sessions, avoiding startup costs and maintaining state across calls.386MIT
- AlicenseAqualityCmaintenanceEnables LLM clients to run GAUSS code against a real GAUSS installation, with persistent workspace state and full-precision data exchange.9MIT
- AlicenseNot gradedqualityCmaintenanceExposes the full SageMath computer algebra system to LLM clients through MCP tools for symbolic mathematics, solving, calculus, plotting, and number theory.45 npm1Creative Commons Zero v1.0 Universal
TDQS
Scored across 8 tools
The tools are largely distinct: evaluating code, interrupting, resetting, getting help, running scripts, and managing packages each have clear roles. The only mild overlap is between m2_evaluate, m2_import_file, and m2_run_script, but their descriptions clearly separate persistent-session evaluation, file import into the session, and isolated batch execution.
All tools share the m2_ prefix and most follow a verb_noun pattern like run_script, list_packages, load_package, and import_file. Minor deviations include m2_session_reset (object before verb instead of reset_session) and verb-only names like m2_evaluate, m2_interrupt, and m2_help, but the overall style is readable and predictable.
Eight tools is a well-scoped size for an interactive computation server. Each tool covers a necessary operation—evaluation, interrupt, reset, help, script execution, package listing, package loading, and file import—without redundancy or bloat.
The tool surface covers the full lifecycle of an interactive Macaulay2 session: evaluate code, interrupt long runs, reset state, load packages, import files, run standalone scripts, and access documentation. There are no obvious dead ends or missing operations for the stated purpose.