Schema | gitlab-mcp

gitlab-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`GITLAB_API_TOKEN`	Yes	Your GitLab personal access token with api or read_api scope
`GITLAB_PROJECT_ID`	Yes	The GitLab project ID (numeric)
`GITLAB_INSTANCE_URL`	Yes	The GitLab instance URL (e.g., https://gitlab.com or self-hosted)

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
get_merge_requestC	Get basic information about a merge request
get_merge_request_commitsA	Get all commits in a merge request
get_merge_request_diffsA	Get all file changes and diffs in a merge request
get_merge_request_discussionsA	Get all discussions and comments on a merge request
get_merge_request_approvalsB	Get approval status and information for a merge request
get_merge_request_pipelinesA	Get CI/CD pipeline information for a merge request
get_merge_request_fullB	Get complete information about a merge request (all data in one call)

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PMelch/gitlab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server