Server facts
penqwin-mcp
Project
- Author
- sarinmsari
- Repository
- github.com/sarinmsari/penqwin-mcp
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- context router
- cut llm cost
- reduce llm token
Overview
Codebase navigation in penqwin-mcp uses structural outlines to give LLM agents context without supplying complete source files. The get_repo_index tool maps repository files to their exported names, providing paths for more focused inspection. From there, get_folder_skeleton covers a directory prefix, while get_file_skeleton examines an individual file. These views expose elements such as imports, exports, signatures, types, class members, parameters, and documentation comments. This supports exploration at repository, folder, and file scope while keeping the context centered on code structure.
For targeted lookup, search_symbols finds files exporting a named symbol and returns details including its location, language, kind, signature, and documentation comment. The get_repo_stats tool adds file totals and a language breakdown for a broader view of the repository. The server communicates over stdio and has integration instructions for Cursor, Claude Desktop, and Antigravity. Operation requires Node.js 18 or later, an active eng-doc backend, and an API key from that platform. Environment variables supply the key, organization identifier, target repository, and backend API address; clients can launch the package through npx or use a locally compiled build.
penqwin-mcp setup notes
- penqwin-mcp records stdio only; confirm a network transport upstream before planning remote access.
- penqwin-mcp has no recorded license; confirm reuse terms in its repository.