Turn GitLab into MCP tools
Give your AI agent GitLab tools. Writ turns your GitLab workflows into authenticated MCP tools your agent can call, taking real actions on your own account.
{
"mcpServers": {
"writ-gitlab": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer wt_8f2c...a91" }
}
}
} No GitLab MCP server yet? Build one in minutes
Record the GitLab task once, or describe it to an AI session, and Writ turns it into an MCP tool your agent can call, taking real actions on your own GitLab account.
- 1Record a GitLab action once
Open the recorder and open a project on GitLab in a real browser. Writ captures the steps, login and 2FA included, into a workflow.
- 2Publish it as an MCP tool
One click exposes the workflow as an MCP tool with a typed input schema, alongside a REST endpoint. Your agent picks it by its description.
- 3Call it from any MCP client
Point Claude Desktop, Claude Code, Cursor, or any MCP client at your Writ server. The GitLab tool acts on your own account and returns structured output.
Browse supported MCP clients, see what's possible on workflows, or search for another site. Free to start. See pricing.
GitLab has no MCP server
Read-only website-to-MCP tools can summarize a GitLab page, but they can't do anything on it. Writ turns the GitLab workflows you build into MCP tools your agent calls to take real actions (search, extract, submit), authenticated, on your own GitLab account.
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
GitLab tools your agent can call
Each tool is a real GitLab workflow with a typed input schema and structured output. Your agent picks the right one by its description.
gitlab.get_projectReturn stars, open issues, and latest release for a project.Example tool schema
{
"name": "gitlab.get_project",
"description": "Return stars, open issues, and latest release for a project.",
"input_schema": {
"type": "object",
"properties": {
"query": { "type": "string", "description": "What to look up on GitLab." }
},
"required": ["query"]
}
} Add the server to any MCP client
Copy the config into your client and authenticate with a wt_ key. Tools appear automatically.
{
"mcpServers": {
"writ-gitlab": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer wt_8f2c...a91" }
}
}
} {
"mcpServers": {
"writ-gitlab": {
"url": "https://api.usewrit.app/mcp/your-workspace",
"headers": { "Authorization": "Bearer csk_3a90...f4d" }
}
}
} Per-client setup. Step-by-step config for each client lives on the per-client pages: Claude Desktop, Claude Code, Cursor, Windsurf.
Your agent acts on your own GitLab account
Writ signs into your own GitLab account through a Persona with 2FA for UI-only actions, or reads public projects with no login.
Use Writ on your own GitLab account and on public projects you have the right to access. Respect its Terms of Service.
Other ways to work with GitLab
GitLab MCP questions
Is there an official GitLab MCP server?
Are there ready-made GitLab MCP tools I can install?
How is this different from a read-only website-to-MCP tool?
Does it work with GitLab login and 2FA?
Which MCP clients can use these GitLab tools?
Is it allowed to use GitLab this way?
Give your agent GitLab tools
Build a workflow, publish it as an MCP tool, and call it from any MCP client. Get started free.