Skip to main content
Glama
sudeepan

mathematica-wstp

by sudeepan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mathematica-wstp

No user-submitted related servers found.

    Related Servers

    • notebook-agent-mcp

      KJH-Sun
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to execute Jupyter notebook cells with persistent kernel state, output persistence, and structured JSON control surface.
      2
      -

    • agent-testbench

      sarptandoven
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to start and operate live kernels on local machines, Modal GPUs, or Colab VMs, running code, notebook cells, shell commands, and file transfers while inspecting variables, plots, and errors. It also runs notebooks, scripts, and web UIs end to end as budget-capped plans that verify expectations and report what failed and what changed.
      MIT

    • baltamatica.mcp

      wzlwww
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to interact with the Baltamatica scientific computing kernel, executing code, managing variables, and running scripts while preserving workspace state across calls.
      6
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools map cleanly to different resources or actions: kernel evaluation, notebook/cell access, rendering, variable inspection, and batch orchestration. There are a couple of overlapping boundaries—abort vs kernel(action='abort') and status vs kernel(state)—but the descriptions generally clarify which one is intended.

    Naming Consistency3/5

    Names are readable and mostly action-oriented, but the convention is mixed: bare verbs (evaluate, abort, render), bare nouns (kernel, status, notebooks, cells, vars), and underscore compounds (evaluate_cells, read_notebook_file, verify_derivation). It is not chaotic, but there is no single predictable verb_noun pattern.

    Tool Count5/5

    Fourteen tools is within the well-scoped range and each tool addresses a genuinely distinct part of the server's purpose: persistent evaluation, kernel admin, notebook sessions, cell operations, rendering, symbol inspection, batching, and guidance. The count is substantial but not padded.

    Completeness5/5

    The surface covers the main lifecycle for both the persistent kernel (evaluate, abort, restart, vars) and notebooks (open/create/list/save/close, read cells, write/delete cells, evaluate cells), plus rendering and derivation verification. There are no obvious dead ends or missing core operations for this domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources