GitLab with OHarness
- 连接器
- 开发者工具
Issues, merge requests and pipelines on GitLab.com. OHarness works with GitLab out of the box — sign in once in your browser and its tools are in every session.
本页正文为英文。它解释的术语是人们用英文检索的术语，而译过的术语已经是另一个术语。
What you get
| MCP connector | Remote, over streamable HTTP at https://gitlab.com/api/v4/mcp. |
| Published by | GitLab |
How it signs in
Through your browser, the first time a session uses it. The server answers with a sign-in challenge, OHarness discovers GitLab’s authorization server and registers itself there on the spot, and the tokens land in ~/.oharness/auth.json, readable only by you. Nothing to paste, and nothing stored by us.
Try it
Once GitLab is connected, a first prompt to see it work:
Use GitLab to look into the bug in this branch and propose a fix with a test.
Adding it
- Download OHarness for the Mac, or install the CLI anywhere Node runs.
- In the composer, open the + menu and find GitLab under Connectors.
- Pick it and sign in when the browser opens. Its tools are available from the next turn.
Links
Common questions
Does OHarness work with GitLab?
Yes. GitLab ships in OHarness as an MCP connector, so it is in the menu on first launch with nothing to look up.
How does the GitLab connector sign in?
Through your browser. The first request is answered with a sign-in challenge, OHarness registers itself with GitLab's authorization server on the spot, and the tokens are kept on your machine in auth.json, readable only by you. There is no key to paste.
Is OHarness affiliated with GitLab?
No. OHarness works with GitLab through its public MCP server; GitLab and its logo belong to GitLab.
More in developer tools
Chrome DevTools · Code simplifier · Context7 · DeepWiki · Feature development · Frontend design
GitLab and its logo belong to GitLab. Listed because OHarness works with it, not because GitLab endorses OHarness.
Use GitLab from OHarness
The same GitLab tools in every session, whichever of the model providers is underneath.