DevProjex MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| root | Yes | Absolute path of the project to expose. In the Glama sandbox this is the DevProjex source checkout itself; a hosted instance cannot see your machine, install DevProjex locally to work on your own code. | /app |
| hide_private_data | No | Mask local user name in paths |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List the project roots this server is allowed to read and their saved local profiles. |
| get_treeA | Return the effective project tree after built-in, gitignore, profile, and optional agent glob filters. |
| analyzeA | Measure a redacted project selection and list its largest text files by estimated tokens. |
| pack_contextA | Build an exact redacted DevProjex context export. A stored pack id remains valid until this server process exits; after restart, call pack_context again. |
| read_packA | Read a 1-based line range from a pack created by this server session. |
| search_projectA | Search already-redacted project text with a timeout-bounded .NET regular expression. |
| get_fileA | Read redacted text from one effective project file using an optional 1-based line range. |
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 7 tools
Each tool targets a distinct operation: listing projects, viewing trees, reading files, building/reading packs, regex searching, and analyzing sizes. read_pack and get_file are similar in mechanics but clearly separated by pack vs. individual file scope.
Most names follow a clear verb_noun pattern (list_projects, get_tree, pack_context, read_pack, search_project, get_file). The single outlier is 'analyze', which would be more consistent as something like analyze_project.
Seven tools is well-scoped for a project context and redaction server. Each tool has a clear role with no obvious redundancy or bloat.
The set covers the main workflow: discover projects, inspect tree/files, search, build a pack, and read pack contents. Minor gaps exist, such as no pack-specific search or profile management, but agents can work around them.