Docfork MCP vs GitLab Documentation MCP Server
A side-by-side look at the Docfork MCP and GitLab Documentation MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Docfork MCP for version control work as a local process; choose GitLab Documentation MCP Server for version control over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Docfork MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 31/100 · Emerging | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 484 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Docfork MCP | View GitLab Documentation MCP Server |
Tools & capabilities
Docfork MCP tools
No tool names declared yet. Check the project README from the listing page.
GitLab Documentation MCP Server tools 3
search_docsget_docsearch_and_fetch
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.
Docfork MCP
{
"mcpServers": {
"docfork-mcp-2": {
"command": "npx",
"args": [
"-y",
"dgrep"
]
}
}
}
GitLab Documentation MCP Server
{
"mcpServers": {
"gitlab-documentation-mcp-server": {
"url": "http://127.0.0.1:8000/mcp"
}
}
}
Frequently asked questions
Docfork MCP is categorized under Version Control and uses a local stdio subprocess. GitLab Documentation MCP Server belongs to Version Control and uses a remote HTTP/SSE transport. Pick Docfork MCP for version control work and GitLab Documentation MCP Server 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.
Docfork MCP has no declared pricing — check the project's own site. GitLab Documentation MCP Server 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 docfork-mcp-2 and gitlab-documentation-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Docfork MCP has a quality signal of 31/100 (Emerging) with 2 views, 0 installs and 484 GitHub stars. GitLab Documentation MCP Server has 49/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.