skel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKEL_MCP_ROOT | No | Sets the project root directory for the server. The project root is resolved through SKEL_MCP_ROOT, Claude Code's CLAUDE_PROJECT_DIR, or the launcher's working directory, in that order. | |
| CLAUDE_PROJECT_DIR | No | Claude Code supplies the project directory through CLAUDE_PROJECT_DIR. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_contextA | Batch AST reads. outline: signatures/names. symbol: code with imports/types, or explicit returns only. lines: literal match with contextLines. diff: changes/full scoped by file/symbol. Share a top-level file. Use sources:true for file/symbol labels. Continue with cursor or maxTokens:null. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no inter-tool ambiguity to speak of. However, get_context internally multiplexes four distinct modes (outline, symbol, lines, diff) plus cursor/token options, which places the disambiguation burden on the description rather than the tool surface.
A single verb_noun name (get_context) is inherently consistent and clearly signals a read operation. No naming conflicts or mixed conventions are possible with one tool.
One tool for the whole server is thin, even though it is a multi-mode mega-tool that internally covers several read operations. It is borderline: workable for read-only AST context, but it concentrates all capability into a single overloaded entry point.
Read coverage looks solid for the domain (outline, symbol body, literal line matching, diff, pagination), but there are no write operations and no non-literal/regex or symbol-name search mode. Agents can work around this but some retrieval intents will be awkward.