GitLab Documentation MCP Server vs Core
A side-by-side look at the GitLab Documentation MCP Server and Core MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GitLab Documentation MCP Server for version control work over a hosted endpoint; choose Core for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GitLab Documentation MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_docs, get_doc, search_and_fetch.
Choose Core when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITHUB_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 49/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View GitLab Documentation MCP Server | View Core |
Tools & capabilities
GitLab Documentation MCP Server tools 3
search_docsget_docsearch_and_fetch
Core tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
GitLab Documentation MCP Server
{
"mcpServers": {
"gitlab-documentation-mcp-server": {
"url": "http://127.0.0.1:8000/mcp"
}
}
}
Core
{
"mcpServers": {
"oss-scout-core": {
"command": "npx",
"args": [
"-y",
"@oss-scout/core"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
GitLab Documentation MCP Server is categorized under Version Control and uses a remote HTTP/SSE transport. Core belongs to Version Control and uses a local stdio subprocess. Pick GitLab Documentation MCP Server for version control work and Core for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
GitLab Documentation MCP Server has no declared pricing — check the project's own site. Core has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gitlab-documentation-mcp-server and oss-scout-core as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitLab Documentation MCP Server has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 1 GitHub stars. Core has 53/100 (Good) with 1 views, 0 installs and 2 GitHub stars.