This project provides an MCP (Model Control Protocol) server that integrates GitLab merge request analysis with Confluence documentation. It allows
If you already use MRConfluenceLinker, the mrconfluencelinker mcp server is the piece that lets your assistant work with it directly. This project provides an MCP (Model Control Protocol) server that integrates GitLab merge request analysis with Confluence documentation. It allows you to fetch merge request details, analyze code changes, and store the results in.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Parameters — - project_id: The GitLab project IDmr_id — The merge request ID to analyzeSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: GITLAB_URL, GITLAB_TOKEN, GITLAB_PROJECT_ID, CONFLUENCE_URL, CONFLUENCE_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MRConfluenceLinker's toolset — Parameters, mr_id — is a fair guide to whether it matches your workflow. It is maintained by CodeByWaqas; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Parameters | - project_id: The GitLab project ID |
| mr_id | The merge request ID to analyze |
or
### Setup with Claude Desktop
```json
# claude_desktop_config.json
# Can find location through:
# Claude -> Settings -> Developer -> Edit Config
{
"mcpServers": {
"MRConfluenceLinker-mcp-server": {
"command": "uv",
"args": [
"--directory",
"/<Absolute-path-to-folder>/MRConfluenceLinker-mcp-server/src/MRConfluenceLinker-mcp-server",
"run",
"server.py"
]
}
}
}
2. The server will listen for commands through stdin/stdout. You can interact with it using prompts like:Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GITLAB_URL | Endpoint or connection string the server talks to. | Yes |
| GITLAB_TOKEN | Credential the server authenticates with. | Yes |
| GITLAB_PROJECT_ID | Configuration value read at startup. | Optional |
| CONFLUENCE_URL | Endpoint or connection string the server talks to. | Yes |
| CONFLUENCE_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.