GitLab Self-Managed
GitLab Self-Managed · Developer tools
A self-managed GitLab: projects, merge requests, issues and pipelines
The client pastes their personal access token from GitLab Self-Managed's settings. We store it encrypted.
Tested against GitLab Self-Managed's live API.
Building with GitLab Self-Managed? The docs have setup steps and code for every tool.
Open the GitLab Self-Managed docsTools
Your agent calls any endpoint of GitLab Self-Managed's API with the request tool, with the client's access attached.
Base URL for request
https://{site}/api/v4
request
HTTPS ANY /v1/clients/{clientId}/gitlab-self-managed/{path}
Any endpoint of GitLab Self-Managed's own API, with the client's access attached.
- servicestringrequired
- This service: gitlab-self-managed
- methodstringrequired
- GET, POST, PUT, PATCH or DELETE
- pathstringrequired
- The path under https://{site}/api/v4
- queryobjectoptional
- Query parameters
- bodyobjectoptional
- A JSON body
Over MCP every tool also takes client_id, from list_clients. Over HTTPS send it as clientId to https://api.operate.as/v1.
What the client approves
- Use the GitLab Self-Managed key you paste, with only the access you gave that key
Get started
Send your next client one link
Add a client, select the services, copy the link. You'll get an email the moment their access is ready. Start free, no card required. Paid plans are one flat monthly price, and a busy month never takes your agents offline.