GitLab Documentation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsB | Search indexed GitLab documentation and return matching paths and titles. |
| get_docA | Fetch the full markdown content of a single documentation page by path. |
| search_and_fetchA | Search documentation and return full markdown for each hit in one call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| list_repos | Repository keys present in the documentation index. |
TDQS
Scored across 3 tools
search_docs and get_doc are clearly distinct, with one returning metadata and the other full content. search_and_fetch overlaps with both by combining them, but its purpose as a convenience method is clear enough to avoid real confusion.
search_docs and get_doc follow a consistent verb_noun pattern. search_and_fetch breaks the pattern slightly by combining two verbs with 'and', but the overall naming style remains predictable and readable.
Three tools is appropriate for a documentation-focused server: one to search, one to retrieve a single document, and one combined operation. Each tool has a distinct, useful purpose with no redundancy.
The core documentation workflow of searching and fetching content is fully covered. A minor gap is the lack of browsing or listing documentation paths without a search query, but agents can work around this using search_docs.