glasz-mcp
Related Servers
Alternatives to glasz-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceEnables AI models to access GitHub repository contents as context, with features to fetch entire repositories, specific file contents, and repository structures for use in AI interactions.348 npm2MIT
- FlicenseBqualityDmaintenanceEnables analysis and querying of Git repository content (both public and private) through a unified tool that provides repository summaries, file structures, and full content optimized for LLM consumption.1-
- AlicenseAqualityCmaintenanceConnects LLMs and AI agents directly to GitHub repositories, enabling repository inspection, file and tree exploration, code search, commit history, issues, pull requests, and releases for both public and private repos.13MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repositories, including fetching repository details, searching, and retrieving README content.256 npm2ISC
- FlicenseNot gradedqualityCmaintenanceEnables AI models to fetch GitHub repository information, read file contents, and search local documentation.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze GitHub repository structures and read file contents with features like directory traversal, file type analysis, syntax highlighting, and code pattern detection. Supports both public and private repositories through GitHub API integration.7 npmApache 2.0
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.