glin

CLI tool and Python library that equips AI agents with an instant, statistical "gut feeling" (System 1 thinking).

glin trains an Explainable Boosting Machine on a CSV, then exposes it to LLM agents over MCP — locally over stdio, or remotely over MCP's standard streamable-http transport. Every prediction comes with an exact, zero-approximation breakdown of which features drove it, straight from the model's own additive structure (no SHAP/LIME approximation).

Install

The PyPI package is named glin-ml (the name glin was already taken by an unrelated project) — but the CLI command and Python import are both just glin.

uv tool install glin-ml     # recommended: installs the `glin` command in an isolated env

pipx install glin-ml        # equivalent, if you use pipx instead of uv

pip install glin-ml         # plain pip also works, into whatever environment is active

Either way, you get the glin command:

glin --help

For development (editable install from a clone of this repo):

git clone https://github.com/AkashChatterjee/glin.git
cd glin
pip install -e ".[dev]"

Related MCP server: TabPFN MCP Server

Train a model

glin train path/to/data.csv --target churn --name churn_v1

Models are saved under ~/.glin/models/<name>/.

glin list

glin delete churn_v1        # prompts for confirmation
glin delete churn_v1 --yes  # skips the prompt

Use it locally (Claude Desktop, Cursor, ...)

Add to your MCP client's config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "glin": {
      "command": "glin",
      "args": ["serve", "--mode", "stdio"]
    }
  }
}

Deploy it remotely (e.g. one EC2 box, any MCP-aware agent)

docker build -t glin .
docker run -p 8000:8000 -v ~/.glin:/root/.glin glin

Then point any MCP client at the standard streamable-http endpoint:

claude mcp add --transport http glin http://<host>:8000/mcp

Tools exposed over MCP

• list_models() — all trained models available.

• inspect_model(model_name) — feature schema and target classes.

• predict(model_name, features, top_n=10) — predicted class and probabilities, plus the full glassbox audit: base rate, every term's contribution (sorted by magnitude), and an explicit additivity check against the model's own predicted probability.

Example: ask Claude directly

Once a model's trained and the MCP server is attached (see above), just talk to Claude in plain language — no need to know the tool schema:

"I've got 3 deals to prioritize before quarter close: Northwind Systems ($42k, Opportunity stage, came from a referral, VP contact, owned by Carla Nguyen, 8 touches logged), Summit Retail Group ($8k, still a Lead, paid social source, owned by Brian Kessler), and Anchor Nonprofit ($3k, still a Lead, owned by Frank Suarez, no activity logged yet). Run them through deal_predictor_v1 and tell me which to prioritize."

Claude calls predict once per deal and comes back with a ranked, explained answer, not just a number:

Worth knowing before you ask: any field you don't mention comes through as missing to the model, not as "average" — so naming a rep and a lifecycle stage (using the model's own trained categories, e.g. Lead / Opportunity / Customer) matters far more for a well-differentiated answer than adding extra color to fields the model already has.

Data requirements

glin train validates your CSV before doing any work — hard problems (e.g. a target column with only one class) stop training with a clear error; soft issues (e.g. a date-like column) print a warning and training proceeds anyway. These rules live in glin/validation.py as a flat, appendable list, so support for a currently-unsupported shape below can be added by adding one rule and one preprocessing case, without touching the rest of the pipeline.

Feature columns — supported today:

Feature columns — not yet supported (each is flagged by glin train's validator when detected):

Target column requirements:

• At least 2 distinct non-null values (binary or multiclass) — a single-class target is a hard error.

• Rows with a missing target value are dropped automatically (with a warning); the rest are unaffected.

• A numeric target with many distinct values (>20) triggers a warning that it looks like a regression target — glin trains classifiers, not regressors.

Releasing (maintainers)

PyPI rejects re-uploading a version number, so bump version in pyproject.toml first and double check the metadata (description, classifiers, URLs) before publishing — there's no fixing a released version after the fact, only shipping a new one.

rm -rf dist
uv build

Dry run against TestPyPI first:

twine upload --repository testpypi dist/*
# username: __token__, password: a TestPyPI API token

Verify it actually installs from there before touching the real index:

pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ glin-ml

Then publish for real:

twine upload dist/*
# username: __token__, password: a PyPI API token (separate account/token from TestPyPI)

Confirm the public release works with a clean install:

uv tool install glin-ml
glin train some.csv --target y --name smoke_check