glasz-mcp
Fetches glasz-style spec files (product.md, tech.md, test-plan.md, and INDEX.md) from GitHub repositories, enabling LLMs to answer questions about features, stories, and acceptance criteria without cloning or pasting files.
README
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 npx -y github:quintegro/glasz-mcp (compiled dist/ is committed) |
| S4 | get_index — fetch specs/INDEX.md |
| S5 | get_feature — fetch a feature's trio |
| S6 | instructions schema legend taught at initialize |
Deferred to v1.x: S2 (OAuth device-flow login — currently a stub) and
S3 (list_repos discovery — not registered).
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 stdio
dist/ is committed to git (not .gitignored) because npx git-installs do
not run build scripts — the compiled output must exist on the default branch.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.