> For the complete documentation index, see [llms.txt](https://docs.stepsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stepsecurity.io/administration/admin-console/resources/gitlab-servers.md).

# Gitlab Servers

The GitLab Servers page lists every GitLab instance connected to StepSecurity, including both `gitlab.com` and self-hosted GitLab servers.

{% hint style="info" %}
StepSecurity's GitLab integration currently supports self-hosted GitLab runners. For the full scope of supported capabilities, see the [GitLab documentation](https://docs.stepsecurity.io/gitlab/).
{% endhint %}

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FRz3uM1MVdbo9G8PwSaHr%2FScreenshot%202026-05-08%20at%2012.30.37.png?alt=media&amp;token=4f3930de-0e5e-4488-9cb1-7cf782b54dfe" alt=""><figcaption></figcaption></figure>

### What you can do here

* **View connected GitLab instances:** The table lists every GitLab server registered with StepSecurity, identified by name. The `cloud-instance` entry represents `gitlab.com`.
* **View projects on a server:** Click **Projects** on any row to see the GitLab projects StepSecurity has discovered on that server.
* **Check agent status:** Click **Agent status** on any row to see the connection status of the StepSecurity agent for that server, including whether the agent is currently reporting telemetry.

### Adding a GitLab server

GitLab servers are connected to StepSecurity by deploying the StepSecurity agent on a self-hosted GitLab runner. Once the agent is running and authenticated, the server appears in this list automatically.

For the full agent installation walkthrough, see the [GitLab documentation](/gitlab/settings/self-hosted-runners.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stepsecurity.io/administration/admin-console/resources/gitlab-servers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.