GitLab Forum MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITLAB_FORUM_API_KEY | No | Your GitLab forum API key (required for write operations) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discourse_select_siteA | Validate and select a Discourse site for subsequent tool calls. |
| discourse_searchC | Search site content. |
| discourse_read_topicC | Read a topic metadata and first N posts. |
| discourse_read_postC | Read a specific post. |
| discourse_list_categoriesB | List categories visible to the current auth context. |
| discourse_list_tagsC | List tags (if enabled). |
| discourse_get_userC | Get basic user info. |
| discourse_filter_topicsA | Filter topics with a concise query language: use key:value tokens separated by spaces; category/categories for categories (comma = OR, '=category' = without subcats, '-' prefix = exclude), tag/tags (comma = OR, '+' = AND) and tag_group; status:(open|closed|archived|listed|unlisted|public) and personal in:(bookmarked|watching|tracking|muted|pinned); dates: created/activity/latest-post-(before|after) with YYYY-MM-DD or N (days); numeric: likes[-op]-(min|max), posts-(min|max), posters-(min|max), views-(min|max); order: activity|created|latest-post|likes|likes-op|posters|title|views|category with optional -asc; free text terms are matched full-text. Results are permission-aware. |
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 clearly distinct purpose with no overlap: filtering topics, getting user info, listing categories/tags, reading posts/topics, searching content, and selecting a site. The descriptions reinforce these distinct roles, making misselection unlikely.
All tools follow a consistent 'discourse_verb_noun' pattern (e.g., discourse_filter_topics, discourse_get_user, discourse_list_categories). This predictable naming scheme enhances readability and usability across the set.
With 8 tools, this server is well-scoped for interacting with a GitLab forum (Discourse instance). Each tool serves a specific, non-redundant function, covering core operations like reading, listing, filtering, and searching without being overly sparse or bloated.
The toolset provides strong coverage for reading and querying forum data, including topics, posts, users, categories, and tags. A minor gap exists in write operations (e.g., creating or replying to posts), but agents can still perform most common read-only workflows effectively.