gauss-mcp
Enables LLM clients to run GAUSS code against a real GAUSS installation, with persistent workspace state and full-precision data exchange.
README
gauss-mcp
Drive GAUSS from Python, and expose it to LLM clients over the Model Context Protocol.
Author: Dr Merwan Roudane
Built and tested against GAUSS 26.1.1 on Windows.
Why this exists
Aptech publishes a reference for AI assistants so they write better GAUSS, but writing is not running: an assistant that cannot execute the code never learns whether it worked or what the numbers were. This connects an assistant to a real GAUSS installation, so the results come from GAUSS rather than from the model.
How it drives GAUSS
Through tgauss, the terminal build that ships with an ordinary GAUSS
installation — not the GAUSS Engine, which is richer but needs a separate
licence key from Aptech.
Each call is its own tgauss process, so nothing would normally carry over.
The workspace is saved on the way out and restored on the way in, which makes a
run of calls behave like one continuous session: a matrix built in one call is
still there in the next.
Install
The distribution is gauss-lang-mcp on PyPI: plain gauss-mcp was already
taken by an unrelated package about import workflows, nothing to do with the
Aptech language. The import name stays gauss_mcp.
pip install "gauss-lang-mcp[pandas]"
GAUSS is found automatically under C:\gauss* and C:\Program Files\gauss*.
Set GAUSS_HOME to choose between installations.
Library use
from gauss_mcp import Gauss
with Gauss() as g:
g.run("""
rndseed 90210;
n = 400;
x = rndn(n, 1);
y = 1.25 + 0.8*x + 0.3*rndn(n, 1);
des = ones(n,1)~x;
bhat = invpd(des'des)*des'y;
""")
print(g.get_matrix("bhat")) # [[1.2489...], [0.8043...]]
Values cross as CSV rather than as printed text, so they keep full double precision instead of GAUSS's display rounding:
g.run("pi_like = 3.14159265358979;")
g.get_scalar("pi_like") # 3.14159265358979, every digit
pandas both ways:
frame = g.to_dataframe(["x", "y"])
g.from_dataframe(frame)
MCP server use
{
"mcpServers": {
"gauss": { "command": "gauss-lang-mcp" }
}
}
Tools
| Tool | Purpose |
|---|---|
gauss_status |
Where GAUSS is, its version, what the workspace holds |
run_gauss_code |
Main tool. Run GAUSS code and return what it printed |
list_symbols |
Every symbol with its type and dimensions |
describe_symbol |
Type and shape of one symbol |
get_matrix |
Read a matrix out at full precision |
put_matrix |
Create a matrix from numbers given in the conversation |
read_csv / write_csv |
Move data between files and the workspace |
clear_workspace |
Start again from empty |
Errors
GAUSS reports its own code, message and line, and those are passed through:
GaussError: G0025: Undefined symbol: 'no_such_thing' on line 2
The line refers to your code. The workspace restore is prepended to every generated program, which shifts GAUSS's own numbering by a line; that offset is corrected before you see it.
Behaviour worth knowing
Characteristics of GAUSS and of tgauss that this package handles for you,
each confirmed against a live installation rather than assumed.
- The exit code is always 0, whether the program succeeded or died. It carries nothing, so errors are read from stderr instead.
- stdout is clean. The banner and job header go to stderr, so the program's own output needs no filtering.
- GAUSS compiles before it runs. An undefined symbol anywhere means nothing executed and no output appears. A runtime error leaves the output produced up to that point, followed by "Program execute failed".
- Symbol names ignore case.
Xandxare the same symbol, so assigning to one overwrites the other. This surprises people arriving from R or Python. - The child must not inherit stdin. Under MCP, the server's stdin is the
JSON-RPC stream; a
tgaussthat inherited it would read the protocol itself. Every subprocess call detaches stdin. - Restoring a workspace uses
use, notloadall.saveallwrites a.gcganduse <name>;must be the first statement of the program that reads it.
Tests
python tests/test_offline.py # 10 tests, no GAUSS needed
python tests/test_live.py # 24 tests, drives a real installation
Licence
MIT. Copyright (c) 2026 Merwan Roudane.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。