mcpField
G
GitLab MCP Server Extension for Zed

GitLab MCP Server Extension for Zed

Local
github.com/akbxrVersion Control17Updated 45w ago

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

  1. 01GitLab project and file operations
  2. 02GitLab.com and self-hosted support
  3. 03Personal access token authentication

Use cases

  1. 01Manage GitLab projects in Zed
  2. 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.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

GitLab 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:

  1. Open Zed's Agent settings
  2. 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.
  3. Enable the GitLab MCP Server in the active assistant profile. In the chat section, click on the Write | Ask button, then click on tools, then enable the GitLab MCP server.
Personal Access Token

To create a GitLab Personal Access Token:

  1. Go to GitLab User Settings > Access Tokens
  2. Select the required scopes:
    • api for full API access
    • read_api for read-only access
    • read_repository and write_repository for repository operations
  3. Create the token and save it securely
  4. Add the token to your Zed settings as shown above
Building from Source
  1. Ensure you have Rust and Cargo installed
  2. Clone the repository
  3. Run cargo build --release

License

Apache-2.0

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

Comments

Markdown supported

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.