Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Free
Nothing to run from here
GitLab Workflow is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
Creates GitLab issues from requirements and submits merge requests from existing issues, plus atomic GitLab API tools for issue-driven development.
Quickstart
# 1 — run it from where its publisher ships it
npx -y @chntif/mcp-gitlab-workflow
# 2 — ask your agent something
> Creates GitLab issues from requirements and submits merge requests from existing issues, plus atomic GitLab API tools for issue-driven
GitLab Workflow is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
CHAll 1 server
@chntif1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts GitLab Workflow as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add gitlab-workflow-mcp -- npx -y @chntif/mcp-gitlab-workflowReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use when requirement text should only create a GitLab issue and stop there. Do not combine this with workflow_requirement_to_delivery for the same user request. If the issue is already created, continue with workflow_issue_to_delivery instead of calling this tool again.
Takes no parameters.
Example callreturns →
Use when only local issue log markdown should be appended. This tool does not create MR or commit.
Takes no parameters.
Example callreturns →
Two-step MR review workflow. Step 1: call with prepare_review_context=true to fetch review_prompt + diffs for LLM review. Step 2: let the LLM inspect that context, then call again with review_comment_body to post the final review comment (optional approval).
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Use when local repository should fetch/pull and switch to a target branch. Local git operations only.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get current authenticated GitLab user (/user).
Takes no parameters.
Example callreturns →
List labels of a GitLab project (/projects/:id/labels).
Takes no parameters.
Example callreturns →
Create a project label (/projects/:id/labels).
Takes no parameters.
Example callreturns →
Update a project label (/projects/:id/labels).
Takes no parameters.
Example callreturns →
Delete a project label (/projects/:id/labels/:label_id).
Takes no parameters.
Example callreturns →
Create an issue with GitLab REST API /projects/:id/issues.
Takes no parameters.
Example callreturns →
Get merge request detail (/projects/:id/merge_requests/:mr_iid).
Takes no parameters.
Example callreturns →
Get merge request notes/comments (/projects/:id/merge_requests/:mr_iid/notes).
Takes no parameters.
Example callreturns →
Get one issue by project_id + issue_iid.
Takes no parameters.
Example callreturns →
Upload binary file to project markdown uploads and return markdown/url metadata.
Takes no parameters.
Example callreturns →
Extract image references from issue description/notes. When include_base64=true, download each image, return base64 metadata, and attach MCP image content blocks so the model can inspect the image itself.
Takes no parameters.
Example callreturns →
Get issue notes/comments by project_id + issue_iid.
Takes no parameters.
Example callreturns →
Create issue note/comment. Supports direct body or auto-generation from MR changed files (by MR IID or source branch).
Takes no parameters.
Example callreturns →
Create repository branch by GitLab REST API.
Takes no parameters.
Example callreturns →
Get repository file by GitLab REST API /repository/files/:file_path.
Takes no parameters.
Example callreturns →
Create one commit with multiple file actions via GitLab commits API.
Takes no parameters.
Example callreturns →
Create merge request by GitLab REST API /projects/:id/merge_requests.
Takes no parameters.
Example callreturns →
Create merge-request note/comment.
Takes no parameters.
Example callreturns →
Get merge request changes/diff metadata.
Takes no parameters.
Example callreturns →
Approve merge request by GitLab approval API.
Takes no parameters.
Example callreturns →
Remove approval from merge request.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. GitLab Workflow costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 93 / 100
Release 0.1.2 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest01d17220eca645bc4f029edb8b5b8c97b707b5ddb957c79a0c05396be396d71b
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (28 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| workflow_requirement_to_issue | no tags | |
| workflow_issue_log_append | no tags | |
| workflow_review_mr_post_comment | untrusted-input | |
| workflow_prepare_delivery_workspace | no tags | |
| workflow_sync_local_branch | untrusted-input | |
| workflow_issue_to_delivery | no tags | |
| workflow_requirement_to_delivery | external-sink | |
| gitlab_get_current_user | no tags | |
| gitlab_list_labels | no tags | |
| gitlab_create_label | no tags | |
| gitlab_update_label | no tags | |
| gitlab_delete_label | no tags | |
| gitlab_create_issue | external-sink | |
| gitlab_get_merge_request | no tags | |
| gitlab_get_mr_notes | no tags | |
| gitlab_get_issue | no tags | |
| gitlab_upload_project_file | no tags | |
| gitlab_get_issue_images | untrusted-input | |
| gitlab_get_issue_notes | no tags | |
| gitlab_add_issue_comment | external-sink | |
| gitlab_create_branch | no tags | |
| gitlab_get_file | no tags | |
| gitlab_commit_files | no tags | |
| gitlab_create_merge_request | no tags | |
| gitlab_create_mr_note | no tags | |
| gitlab_get_mr_changes | no tags | |
| gitlab_approve_mr | no tags | |
| gitlab_unapprove_mr | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest01d17220eca645bc
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.1.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.1.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against GitLab Workflow in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.