Skip to content

feat(environments): expose Environments and Deployments (Free)Β #443

@polaz

Description

@polaz

πŸ‘ React to this issue if you need this feature β€” helps us prioritise.

Problem

Environments + Deployments are the source of truth for "what version of X is running where". Useful for incident triage, deployment audit, manual env stops. Two competing MCP servers cover this; we don't.

Investigation done (current state)

Verified against src/entities/:

  • ❌ grep -ri 'deployment' src/entities/ returns 0 hits
  • ❌ No entity environments/ or deployments/
  • ❌ environment hits exist (170) but all in registry-manager.ts/handlers.ts referring to runtime env, not GitLab Environments

Re-verify before coding:

grep -rIni 'gitlab.*environment\|/environments' src/entities/
ls src/entities/ | grep -iE 'env|deploy'

Acceptance criteria

  • New entity src/entities/environments/ with:
    • browse_environments actions: list, get, list_deployments (within env)
    • manage_environment actions: create, update, stop, delete
  • Optional: pair with new browse_deployments / manage_deployment (manual deployment status update)
  • Integration test using existing test project + creating a manual deployment

GitLab API

Estimate

1d

Context

Found during GitLab 18β†’19 API landscape analysis.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature, new MCP tool, new capability

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions