Schema | GitLab MCP Server

GitLab MCP Server

Official

Describes the environment variables required to run the server.

Name	Required	Description	Default
`GITLAB_API_URL`	No	Base URL for GitLab API (optional, for self-hosted instances)	https://gitlab.com/api/v4
`GITLAB_PERSONAL_ACCESS_TOKEN`	Yes	Your GitLab personal access token with required permissions (api, read_api, read_repository, write_repository)

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
create_or_update_fileC	Create or update a single file in a GitLab project
search_repositoriesB	Search for GitLab projects
create_repositoryC	Create a new GitLab project
get_file_contentsB	Get the contents of a file or directory from a GitLab project
push_filesC	Push multiple files to a GitLab project in a single commit
create_issueB	Create a new issue in a GitLab project
create_merge_requestB	Create a new merge request in a GitLab project
fork_repositoryB	Fork a GitLab project to your account or specified namespace
create_branchB	Create a new branch in a GitLab project

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/modelcontextprotocol/gitlab'

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