About GitLab MCP Server Extension for Zed
A Zed extension that brings GitLab project management and file operations into the editor. It supports GitLab.com and self-hosted instances, authenticating with a personal access token.
Key features
- 01GitLab project and file operations
- 02GitLab.com and self-hosted support
- 03Personal access token authentication
Use cases
- 01Manage GitLab projects in Zed
- 02Perform GitLab file operations in Zed
MCP support
The extension integrates a GitLab MCP server with Zed, making project management and file operations available to the client.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEGitLab MCP Server Extension for Zed
This is a Zed extension that integrates the Model Context Protocol (MCP) server for GitLab, enabling project management, file operations, and more within the Zed editor.
Features
- GitLab Integration: Seamless integration with GitLab API for project management and file operations
- Optional API URL: Support for both gitlab.com and self-hosted GitLab instances
- Automatic Authentication: Handles GitLab authentication using personal access tokens
Installation
Navigate to: Zed > Extensions Or use the command palette (macOS, Linux) to search extensions
Configuration
Required Settings
You need to configure the following settings in your settings.json:
{
"context_servers": {
"mcp-server-gitlab": {
"settings": {
"gitlab_personal_access_token": "YOUR_TOKEN"
}
}
}
}
Optional Settings
For self-hosted GitLab instances, you can specify a custom API URL:
{
"context_servers": {
"mcp-server-gitlab": {
"settings": {
"gitlab_personal_access_token": "YOUR_TOKEN",
"gitlab_api_url": "https://your-gitlab-instance.com/api/v4"
}
}
}
}
Agent Mode Configuration
If you're using Zed's agent mode, you need to enable this context server for your assistant:
- Open Zed's Agent settings
- Enable the GitLab MCP server. If you see that the status of the tool is a red dot, make sure you added your gitlab_personal_access_token in settings.json.
- Enable the GitLab MCP Server in the active assistant profile. In the chat section, click on the
Write | Askbutton, then click ontools, then enable the GitLab MCP server.
Personal Access Token
To create a GitLab Personal Access Token:
- Go to GitLab User Settings > Access Tokens
- Select the required scopes:
apifor full API accessread_apifor read-only accessread_repositoryandwrite_repositoryfor repository operations
- Create the token and save it securely
- Add the token to your Zed settings as shown above
Building from Source
- Ensure you have Rust and Cargo installed
- Clone the repository
- Run
cargo build --release
License
Apache-2.0
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.