project-code-intelligence
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PGVECTOR_HOST | No | PostgreSQL host for pgvector (default: localhost) | localhost |
| PGVECTOR_PORT | No | PostgreSQL port for pgvector (default: 5432) | 5432 |
| PGVECTOR_USER | No | PostgreSQL user for pgvector (default: postgres) | postgres |
| PGVECTOR_DATABASE | No | PostgreSQL database for pgvector (default: pgvector) | pgvector |
| PGVECTOR_PASSWORD | No | PostgreSQL password for pgvector (default: empty) | |
| PROJECT_CODE_INTELLIGENCE_PROFILE | No | Fully qualified Python path to a custom code profile | |
| PROJECT_CODE_INTELLIGENCE_ALLOW_REMOTE_EMBEDDING | No | Set to 1 to allow remote embedding endpoints | 0 |
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 |
|---|---|
| code_intel_statusC | Check code intelligence snapshot, file, record, edge, and embedding state. |
| search_code_intel_textC | Search or list code intelligence records with optional PostgreSQL full-text search and exact filters. |
| search_code_intel_semanticC | Embed a query with the configured embedding backend and search embedded code intelligence records. |
| get_code_intel_recordA | Fetch one code intelligence record by numeric ID, including display content. |
| related_code_intelC | Return code intelligence graph edges related to a record id or symbol. |
| search_static_findingsC | Search SARIF/static-analysis findings with exact filters. |
| get_static_findingC | Fetch one SARIF/static-analysis finding with rule, locations, and code-flow steps. |
| get_static_code_flowC | Fetch ordered SARIF/CodeQL code-flow steps for one static-analysis finding. |
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 8 tools
Tools are mostly distinct in purpose: status overview, individual retrieval of records/findings/flow, semantic/text search, and graph relationships. However, 'get_code_intel_record' and 'related_code_intel' both involve records, but descriptions clarify the difference.
Naming mixes patterns: 'get_code_intel_record' vs 'get_static_finding' (different ordering), 'search_code_intel_semantic' vs 'search_static_findings' (inconsistent prefix). 'code_intel_status' and 'related_code_intel' lack verb prefixes, breaking the verb_noun pattern.
With 8 tools, the count is well-scoped for a code intelligence server covering status, retrieval, search, and relationships. Neither sparse nor bloated.
Covers core needs: status, record/finding retrieval, two search modes, and graph edges. Missing explicit listing endpoints, but search can substitute. No clear dead ends for a read-only intelligence server.