MCP server
- Access
- Read-only
- Who sets it up
- Org admin issues the credential
- Where
- Admin → MCP
The DevGlimpse MCP server lets an AI assistant read your delivery metrics in context. You can ask Claude Code or Codex questions such as “which team has the slowest review latency this month?” and get an answer from your own data. It is read-only. An assistant cannot change anything in DevGlimpse.
Connect an assistant
An org admin creates the credential.
- Go to Admin → MCP.
- Under MCP credentials, enter a Credential name, such as the person or tool it is for.
- Pick the Access level (see below).
- Click Create credential.
- Copy the credential now. It is shown once and cannot be retrieved. Then click I’ve saved it.
Under Configure your assistants, pick the Claude Code or Codex tab. The page fills in your credential and shows what to run:
- Claude Code: one command to run in a terminal. It adds DevGlimpse for you in every project and keeps the credential out of your repositories. Keep the file it writes private and never commit it.
- Codex: a small block for the Codex settings file, plus one line for your shell profile that holds the credential, so the secret stays out of the file.
Create one credential per person or tool, so you can revoke each on its own.
Choose an access level
- Acts as me answers with your role and visibility, like your own sign-in. If your role can see individual numbers, the assistant can too.
- Workspace (aggregates only) reads team and group totals only and names nobody. The tools that cover individuals are not offered to it.
What the assistant can ask
The server offers a fixed set of tools:
| Tool | What it returns |
|---|---|
| Team metrics | Commits, PRs opened and merged, reviews, average cycle time and review latency, and AI-assisted PRs merged, per team or custom group over a date range. |
| PR workflow | Where merged PRs spend their time: first commit to open, open to first review, first review to merge, merge to deploy, plus cycle time and lead time. |
| Metric anomalies | Days when a daily metric left its normal range. |
| Contributor metrics | The same delivery totals per person, for the people your role may see. Not offered to aggregate-only credentials. |
| Pull requests | Pull requests opened in a date range, newest first, with repository, title, state, author, timestamps and size. You can filter by state and ask for up to 100. Not offered to aggregate-only credentials. |
Date ranges are in UTC and can cover at most 366 days. Team and group results respect your minimum group size. Individual results respect visibility scopes, and use pseudonyms when pseudonymous mode applies.
Read-only guarantees
- Every tool is a fixed read. There is no way for an assistant to pass a query, a table name or another workspace’s id.
- Each call runs under the credential’s workspace, role and visibility, checked on every request. If you change a setting, the next call follows it.
- A revoked credential, or a member who is no longer active, is refused.
- If your workspace has an IP allowlist, requests from outside it are refused.
- Requests are limited to 120 per minute per client IP and 120 per minute per credential.
Revoke a credential
On Admin → MCP, click Revoke on the credential. Assistants still using it are turned away straight away. Creating and revoking credentials is recorded in the audit log.