ContextPro
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXTPRO_DAEMON | No | Set to true to opt in to shared indexing/compiler work via the contextpro daemon. | false |
| CONTEXTPRO_TOOL_PROFILE | No | Tool profile exposed by the server. Allowed values: lean, workflow, core, full. Defaults to workflow. | workflow |
| CONTEXTPRO_CONNECTED_CONTEXT | No | Set to true to enable experimental connected retrieval that combines ranked source, one-hop imports/callers and relevant tests. | false |
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
} |
| logging | {} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_toolsA | Discover or enable experts and return their schemas. If the client cannot refresh its catalog, call runs a supported read/index tool; never source edits. |
| artifact_readA | Load a previously generated context artifact by ID so agents can reuse earlier task packets, repo maps, and decisions without regenerating them. |
| exact_referencesA | Find who calls or references a symbol. TS/JS compiler bindings exclude same-named unrelated symbols; results label calls/imports and give per-file call totals before limits. Check scope, ambiguity and warnings. Python is heuristic; imported SCIP freshness is unverified. |
| skeletonA | Get detailed function signatures, class methods, and type definitions of a specific file WITHOUT reading the full body. Shows the API surface and line ranges. Signatures are normalized summaries, not exact edit anchors; use context(targets:[{file,start,end}]) for source text before editing. |
| searchA | Search the codebase by MEANING. Modes: 'file' searches file headers/symbols, 'identifier' searches function/class definitions with call chains, 'hybrid' (default) runs both and returns combined results. Uses embeddings for semantic matching plus keyword overlap scoring. For an exact known symbol name in a language with a real language server available (e.g. via an LSP-backed MCP like Serena), prefer that for go-to-definition — this tool is best for meaning-based / fuzzy discovery across the whole repo. |
| grepA | Fast literal or regex string search across the project's indexed file set. Use this for log-message lookups, config-key searches, error-message tracing, or any time you know the exact characters you want to find. Use 'search' instead for semantic intent queries. Skips binary files; respects .gitignore via the indexed walker. |
| blast_radiusA | Find textual usage candidates with counts by kind. Use kind:call for call-containing lines. Includes same-name symbols; use exact_references for binding-resolved TS/JS rename checks. |
| reindexA | Re-walk, re-parse, and re-index project files into the database. Detects changed files via content hash and only re-processes what changed. Eagerly populates file and identifier embeddings unless no_embed=true or CONTEXTPRO_REINDEX_NO_EMBED is set. Use after git pull, branch switch, or external edits. Builds the import graph for related/test_map tools. |
| statusA | Project overview dashboard. Returns file counts, index state, memory graph stats, git branch, uncommitted changes, and recent commits. One call for complete situational awareness at the start of a session. |
| efficiency_reportA | Report ContextPro's persistent, auditable context-compression estimates by tool. History stores numeric metrics only—never prompts, source code, response bodies, or file paths. Token savings are estimates, not billing data. |
| explainA | Extract a specific function/class body with its dependencies, without reading the entire file. Provide symbol name to get its code + called functions. Provide file path for a structural overview. |
| task_packA | Assemble the minimum useful working set for a task: ranked files, nearby tests, recent diffs, memory, and risks. |
| validate_scopeA | After edit_scope, recommend the most relevant validation checks and commands. Pass files when you already know what changed; they take precedence over task inference. |
| memory_record_taskA | Persist useful task outcomes with linked files, assumptions, evidence, and open risks for future sessions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| contextpro_instructions |
TDQS
Scored across 14 tools
Most tools have distinct roles, and potentially overlapping pairs such as search/grep, exact_references/blast_radius, and skeleton/explain are explicitly differentiated in their descriptions. A few boundaries remain soft, especially between structural overview tools and usage-analysis tools, but an agent can generally choose correctly.
All names use snake_case, which keeps them readable, but the naming patterns are mixed: some are single verbs (search, grep, explain), some are nouns (skeleton, status, task_pack), some are verb_noun (discover_tools, validate_scope), and one is noun_verb_noun (memory_record_task). The set is understandable but not predictably patterned.
With 14 tools, the server is within a well-scoped range for a code-context and indexing assistant. Each tool appears to serve a specific workflow, and the count is neither thin nor excessive.
The core code-context workflows are covered: discovery, search, references, structural explanation, reindexing, status, task packing, and memory recording. However, validate_scope references an edit_scope step that is not present, and artifact/memory surfaces are incomplete because there is no obvious way to list artifacts or query memory records directly.