glasz-mcp
Fetches glasz-style spec files (product.md, tech.md, test-plan.md, and specs/INDEX.md) from GitHub repositories, allowing LLMs to answer questions about features, stories, and acceptance criteria without cloning the repo.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@glasz-mcp Show me the acceptance criteria for the login feature."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
glasz-mcp
A read-only Model Context Protocol server that
fetches glasz-style spec files (the product.md / tech.md / test-plan.md
trio + the derived specs/INDEX.md) from GitHub repositories and hands them to
an LLM client, so the model can answer questions about features, stories, and AC
status without the user cloning the repo or pasting files.
It is intentionally a thin window onto the same source data that glasz the app
reads — no writes, no parsing on the server (the LLM interprets the trio,
guided by the server instructions block).
Status — v1-core
This release implements the v1-core scope:
Story | What |
S1 | Install via |
S4 |
|
S5 |
|
S6 |
|
Deferred to v1.x: S2 (OAuth device-flow login — currently a stub) and
S3 (list_repos discovery — not registered).
Related MCP server: Gitingest-MCP
Install
Add this to your MCP client config (Claude Desktop / Claude Code / Cursor):
{
"command": "npx",
"args": ["-y", "github:quintegro/glasz-mcp"],
"env": { "GITHUB_REPO": "owner/name" }
}GITHUB_REPO is optional — when set, tools default to it if repo is omitted.
Authentication
Public repositories are readable without a token. For private repos, set
GITHUB_TOKEN in the client config env, or place a token at
~/.glasz-mcp/auth.json (mode 0600):
{ "access_token": "ghp_…", "token_type": "bearer", "scope": "repo", "login": "you", "created_at": "2026-06-19T00:00:00Z" }The OAuth device-flow login command is deferred to v1.x.
Tools
get_index({ repo? })— returns the raw markdown ofspecs/INDEX.md.get_feature({ repo?, slug })— returns the trio forspecs/features/<slug>/.
Development
pnpm install # also runs `prepare` → build
pnpm run build # tsc → dist/
pnpm test # unit + integration (vitest)
node bin/glasz-mcp.js # start the server on stdiodist/ is committed to git (not .gitignored) because npx git-installs do
not run build scripts — the compiled output must exist on the default branch.
Available Tools
2 toolsget_featureA
Call this for any feature-specific question. Returns the trio of markdown files (product.md, tech.md, test-plan.md) for one feature folder under specs/features//. Each file body is preceded by a "file: …, ref: …" header so you can cite the source. If any file is missing it is reported as missing rather than failing the whole call.
Inputs: slug (required), repo.
get_indexA
Call this first for any cross-feature question about a project (what is blocked, what shipped, status overview). Returns the raw markdown of specs/INDEX.md for the chosen repository. specs/INDEX.md is a derived rollup, not authoritative on its own — for detail on a specific feature, follow up with get_feature.
Inputs: repo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
get_index and get_feature have clearly distinct purposes: one provides a project-wide overview rollup, the other drills into a single feature's details. There is no overlap or ambiguity between them.
Both tools follow the same 'get_' verb + noun pattern (get_index, get_feature), making the naming scheme perfectly consistent and predictable.
With only two tools, the server feels minimal, but this is appropriate for its narrow scope of reading spec markdown files. It is borderline on the thin side but still reasonable.
The server covers the core needs for accessing spec documentation: an index for cross-feature questions and a feature-specific detail view. A minor gap is that there is no explicit listing of all feature slugs, though the index may indirectly provide that.
Maintenance
Related MCP Connectors
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Ask any GitHub repository a question. Get source-backed answers.
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
Access the GitHub API, enabling file operations, repository management, search functionality, and…
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, and Cursor to quickly extract information about GitHub repositories, including repository summaries, project directory structures, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract information about GitHub repositories, including repository summaries, project directory structures, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to quickly extract information about GitHub repositories, including repository summaries, project directory structures, and file contents.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude Desktop, Cline, Cursor, and Windsurf to quickly extract information about GitHub repositories, including repository summaries, project directory structure, and file content.-