Docfork MCP vs Gitlab Docs
A side-by-side look at the Docfork MCP and Gitlab Docs 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 Docs 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 Docfork MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
Choose Gitlab Docs when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
searchGitLabDocs, getDocPage, listDocSections.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 31/100 · Emerging | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 484 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Docfork MCP | View Gitlab Docs |
Tools & capabilities
Docfork MCP tools
No tool names declared yet. Check the project README from the listing page.
Gitlab Docs tools 3
searchGitLabDocsSearch across 2,900+ GitLab documentation pages with intelligent ranking.getDocPageRetrieve the complete content of a specific documentation page.listDocSectionsBrowse available documentation sections and their structure.
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 Docs
{
"mcpServers": {
"gitlab-docs": {
"command": "npx",
"args": [
"-y",
"gitlab-docs-mcp"
]
}
}
}
Frequently asked questions
Docfork MCP is categorized under Version Control and uses a local stdio subprocess. Gitlab Docs belongs to Version Control and uses a local stdio subprocess. Pick Docfork MCP for version control work and Gitlab Docs 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 Docs is listed as free. Auth: no auth required. 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-docs 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 Docs has 57/100 (Good) with 3 views, 0 installs and 3 GitHub stars.