Repository navigation
v0.2.0 — best-practice refactor
Refactor pass aligning the server with the MCP server best practices checklist.
Highlights
- Tool annotations on every tool — `readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`. MCP clients can classify operations and ask for confirmation only where it matters (merge, delete, cancel, update-with-variables).
- Dual response format — every read tool now accepts `response_format='markdown'` (default, compact) or `'json'` (full raw structure).
- Actionable error messages — `errors.handle()` converts `GitlabAuthenticationError`, 404/403, rate-limits, config errors into messages that tell the agent what to do next (check `GITLAB_TOKEN` scope, verify project path, etc.) instead of raw tracebacks.
- Pydantic input validation — all args use `typing.Annotated` + `pydantic.Field` with `description`, `min_length`/`max_length`, `ge`/`le`, `Literal[...]` for enums. JSON Schema auto-generated for MCP clients.
- Markdown formatters for pipelines, jobs, schedules, branches, tags, MRs, MR changes, repo tree, file content, diff, project info.
- Server name bumped from `'gitlab'` to `'gitlab_ci_mcp'` to match `{service}_mcp` convention.
Compatibility
- Python `>=3.10` (unchanged)
- Config env vars unchanged: `GITLAB_URL`, `GITLAB_TOKEN`, `GITLAB_PROJECT_PATH`, `GITLAB_SSL_VERIFY`, `GITLAB_NO_PROXY_DOMAINS`
- All tool names unchanged, only new optional `response_format` parameter on read tools
Install
```bash
uvx --from gitlab-ci-mcp gitlab-ci-mcp
or
pipx install gitlab-ci-mcp
```