Skip to main content
Glama
Penqwin

@penqwin/mcp

by Penqwin

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PENQWIN_REPOYesThe repository owner and name to target
PENQWIN_ORG_IDYesThe organization ID associated with the API key
PENQWIN_API_KEYYesMachine-to-machine API key generated from the DB
PENQWIN_API_URLYesThe REST API gateway URL of the eng-doc backend

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_repo_indexA

Returns a compact table-of-contents for the repository 'myorg/myrepo'. Lists all tracked source files with their exported symbol names. ALWAYS call this FIRST before any other tool to understand the repository structure. Use the file paths returned here as input to get_folder_skeleton or get_file_skeleton. Cost: ~10-20 tokens per file — very cheap.

get_folder_skeletonA

Returns compact AST skeletons for all source files under a given folder path prefix. Use this to understand a module or feature area without reading raw source files. Skeletons include: exports, function signatures, type definitions, and doc comments. Cost: ~50 tokens per file — much cheaper than raw source code. Tip: call get_repo_index first to discover valid folder paths.

get_file_skeletonA

Returns the AST skeleton for a single specific source file. The skeleton includes: all exports with signatures, imports, class members, and doc comments. Use this when you need the details of one specific file after narrowing down from get_repo_index. For multiple related files, prefer get_folder_skeleton — it is one round trip.

search_symbolsA

Searches the entire repository for files that export a specific symbol name. Use this to find where a function, class, type, or interface is defined. Returns: file path, language, kind (function/class/type/etc.), signature, and doc comment. Example: search for 'createClient' to find all files that export a function by that name.

get_repo_statsA

Returns aggregate statistics for the repository 'myorg/myrepo'. Includes: total file count and a breakdown by programming language. Use this to understand the tech stack and scale of the codebase at a glance.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect of repository exploration (index, stats, file skeleton, folder skeleton, symbol search) with clear instructions to avoid overlap.

Naming Consistency4/5

Most tools follow the get_* pattern, but search_symbols deviates slightly. Overall pattern is clear and predictable.

Tool Count5/5

Five tools cover the essential needs for repository exploration without being excessive or insufficient.

Completeness5/5

The set covers structure overview, detailed file analysis, and symbol search, meeting common code exploration needs.

Maintenance

ActivityStale
ResponsivenessNo issues