cc-sensei
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CC_SOURCE_ROOT | No | Claude Code source root (default: <project>/claude-code-main/src) | <project>/claude-code-main/src |
| MODULE_NOTES_ROOT | No | Module-analysis directory (default: <project>/claude-code-main/MODULE_NOTES) | <project>/claude-code-main/MODULE_NOTES |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_architectureA | Search the Claude Code architecture knowledge base. Returns relevant module analysis at the requested depth level. Use this to understand how specific features, patterns, or subsystems are implemented. |
| get_moduleA | Get detailed content from a specific module. Can optionally return only a specific section type (responsibility, architecture, decisions, principles, or relations). |
| get_source_codeA | Read actual Claude Code source code files. Use this to see implementation details referenced in module analysis. Supports line-range extraction. Returns at most 500 lines per call. |
| list_modulesA | List all available architecture modules. Returns module IDs, titles, and key concerns for each module. Use this to discover what knowledge is available before querying specific modules. |
| search_patternsA | Search for reusable design patterns and principles extracted from Claude Code's architecture. Returns 'directly-reusable' patterns that you can adapt for your own Agent implementation. Output is paginated: each section is capped (default 800 chars) and total sections capped (default 12). Use module_id to focus, or get_module(section="principles") for the full text of a specific module. |
| trace_concernA | Trace a specific architectural concern across all modules. Shows how one concept (e.g., 'prompt cache', 'error recovery', 'streaming') is handled at different layers of Claude Code's architecture. |
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 6 tools
Each tool has a clearly distinct purpose: listing modules, getting module content, searching architecture knowledge, searching patterns, tracing concerns, and reading source code. No two tools overlap significantly, and descriptions clarify any potential ambiguity.
All tools follow a consistent verb_noun pattern (e.g., get_module, list_modules, trace_concern) with clear, descriptive verbs. No mixing of conventions.
Six tools is well-scoped for an architectural knowledge base, providing essential operations without being overwhelming. Each tool serves a necessary role.
The tool surface covers all major activities: discovering modules (list_modules), retrieving module details (get_module, get_source_code), searching across the knowledge base (query_architecture, trace_concern), and accessing design patterns (search_patterns). No obvious gaps for a read-only reference server.