MCP has no tool to list or manage pipeline schedules

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue

Problem

Agents can't see a project's pipeline schedules through the GitLab MCP server: which ones exist, when they run, who owns them, and whether they're active. Questions like "which scheduled jobs does this project run, and who owns them?" need the API or CLI instead.

This also shows up outside dogfooding: production usage from 2026-08-06 to 10-04 includes an agent calling a nonexistent list_pipeline_schedules tool (1 user). #632438 deliberately didn't alias it to list_pipelines, because schedules are a different resource from pipeline runs.

Proposal

1. Add list_pipeline_schedules for a project, returning each schedule's description, ref, cron expression and time zone, next run time, active state and owner.
2. Consider a save_pipeline_schedule to create, update, activate or deactivate a schedule, following the save_* pattern.

Open questions for engineering

• Whether managing schedules should be in scope, or reading them only.
• Which permission level each operation needs.

If you need this, add a 👍 to help prioritize it.