Project Knowledge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Root logging level (WARNING, INFO, DEBUG) | WARNING |
| ANALYSIS_BRANCH | No | Branch to fetch for analysis | uat |
| GITLAB_BASE_URL | Yes | GitLab instance base URL (e.g. https://gitlab.example.com) | |
| REFRESH_INTERVAL | No | Periodic refresh interval (e.g. 15m, 1h). No automatic refresh when unset. | |
| GITLAB_GROUP_PATH | Yes | Top-level group path or numeric group ID | |
| GITLAB_VERIFY_SSL | No | Whether to verify SSL certificates for GitLab HTTPS calls | true |
| VISUALIZATION_PORT | No | TCP port for the visualization server | 7345 |
| GITLAB_ACCESS_TOKEN | Yes | GitLab access token with read_api and read_repository scopes | |
| KNOWLEDGE_STORE_PATH | No | Path to the SQLite knowledge store | data/knowledge_store.db |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | Return all in-scope projects with their GitLab project ID and full path. |
| get_project_purposeB | Return the purpose summary for a project identified by its GitLab project ID. |
| get_project_ioB | Return the abstract inputs and abstract outputs for a project identified by its GitLab project ID. |
| get_project_dependenciesB | Return the external service dependencies and database table dependencies for a project identified by its GitLab project ID. |
| get_project_profileB | Return the full Project_Profile for a project identified by its GitLab project ID. |
| list_purpose_conflictsA | Return the list of all project pairs whose purpose summaries indicate a Purpose_Conflict. |
| refresh_all_projectsA | Trigger an Ingestion_Job that refreshes every in-scope project. |
| refresh_projectA | Trigger an Ingestion_Job that refreshes a single project identified by its GitLab project ID. |
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
Each tool has a clear, distinct purpose: retrieving specific project details (dependencies, I/O, profile, purpose), listing projects, listing conflicts, and triggering refreshes. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern: 'get_project_*', 'list_*', 'refresh_*'. The naming is clear and predictable across all tools.
With 8 tools, the set is well-scoped for a project knowledge server. It covers retrieval, listing, conflict detection, and refresh operations without being too many or too few.
The tool surface fully covers the domain: retrieving project knowledge, listing projects, detecting conflicts, and refreshing data. No obvious gaps like missing search or update are expected given the server's purpose.