schedgrid
README.md
# schedgrid
Ask questions of one published dataset without downloading it first. schedgrid is a local forwarding client for the hosted DrawScheduleWorks MCP service: it answers `tools/list` locally from the captured tool definitions and forwards every call to the service, returning the answers exactly as the service sends them back.
The dataset is read-only from this surface. You can learn its columns and provenance, search its cells, look rows up by an exact key, compare several values side by side, compute summary statistics for a numeric column, and rank rows by a numeric column. Nothing is written, cached or stored locally — the package is a pipe to the dataset, not a copy of it.
All 7 captured tools are built; there are no omissions.
## The tools
- **`dataset_columns`** — The columns, which of them are numeric, the row count and the provenance banner. Call this first to learn the schema. No parameters.
- **`dataset_search`** — Rows whose cells contain the query (case-insensitive), up to 50. `query` is required.
- **`dataset_row`** — Rows where a column equals a value exactly (case-insensitive). `column` and `value` are required.
- **`dataset_compare`** — Rows whose column is any of the given values, in the order given — for "X vs Y" questions. `column` and `values` are required.
- **`dataset_stats`** — Count, min, max, mean, median and sum of a numeric column; non-numeric rows are excluded and counted. `column` is required.
- **`dataset_top`** — The highest (or lowest) rows by a numeric column. `column` is required.
- **`dataset_provenance`** — The source, the date it was computed, the licence and the citation. Read this to attribute a figure correctly. No parameters.
## Install and run
As an MCP server via npm:
```bash
npx -y @reneturcios/schedgrid mcp
```
MCP client configuration:
```json
{
"mcpServers": {
"schedgrid": {
"command": "npx",
"args": ["-y", "@reneturcios/schedgrid", "mcp"]
}
}
}
```
As a container:
```bash
docker run -i ghcr.io/cloudcorprecords/schedgrid
docker run --rm ghcr.io/cloudcorprecords/schedgrid dataset_provenance '{}'
```
## CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
```bash
schedgrid dataset_columns '{}'
schedgrid dataset_search '{"query":"atlas"}'
schedgrid dataset_stats '{"column":"score"}'
schedgrid --version
```
Exit codes: `0` when the forwarded call succeeds, `1` when the upstream result is an error, and `2` for usage problems such as an unknown subcommand or a malformed JSON argument.
## Configuration
- `DRAWSCHEDULEWORKS_MCP_URL` — Overrides the upstream endpoint. The default is the pinned hosted endpoint, `https://drawscheduleworks.com/mcp`. (The override variable is a reconstruction added by this rebuild.)
The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with `schedgrid error:`.
## How forwarding works
The first forwarded call opens a session: an `initialize` request (protocol version `2025-03-26`), followed by a `notifications/initialized` notification, then the `tools/call` itself. If the service answers the initialize request with an `Mcp-Session-Id` header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any `isError` flag and any extra fields the service includes.
## Development
```bash
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
```
The test suite checks the served tool list against the captured surface (all 7 tools, deep-equal, in order, titles included, with no `required` key added to the two parameterless tools), exercises the session handshake and its reuse, verifies that no `Authorization` header is ever sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
## License
MIT — see `LICENSE`. Copyright (c) 2026 Rene Turcios.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues