MCP SageMath Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for HTTP mode | |
| SAGE_PATH | No | Path to the SageMath executable | |
| MCP_TRANSPORT | No | Transport mode for MCP server (http or stdio) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sagemath_versionA | Get local SageMath version information |
| sagemath_evaluateB | Evaluate SageMath code locally |
| sagemath_healthA | Lightweight self-check of SageMath availability and basic readiness |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: sagemath_evaluate executes code, sagemath_health checks system readiness, and sagemath_version retrieves version info. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent snake_case pattern with the 'sagemath_' prefix followed by a descriptive action (evaluate, health, version). This uniformity enhances predictability and readability across the tool set.
With only 3 tools, the server feels thin for a SageMath domain, which typically involves complex mathematical operations. While the tools cover basic evaluation and system checks, more operations (e.g., for algebra, calculus, or plotting) would be expected for a comprehensive server.
The tool surface is severely incomplete for a SageMath server. It lacks core mathematical operations like solving equations, symbolic manipulation, or numerical computation, leaving significant gaps that will hinder agents from performing typical SageMath tasks beyond simple code evaluation.