GitDailies MCP Server tools reference
The GitDailies MCP Server exposes the tools below. You don’t need to call them yourself: your AI assistant chooses tools and fills in their parameters from your question. This page explains what each one can do, so you know what to ask for.
All tools are read-only, and only report on repos that your organization follows in GitDailies.
Trend metrics
Trend tools return metrics over a time period, split into time buckets (day, week,
month, or quarter). Buckets are aligned to calendar boundaries in UTC: weeks start on Monday,
months on the 1st, and so on. The requested period is widened to whole buckets.
A bucket that hasn’t finished yet (for example, the current week) is still returned, marked
partial, so your agent can compare it fairly with complete buckets.
| Tool | Returns | Metrics docs |
|---|---|---|
get_pr_trends | PR lifetime, coding time, pickup time, review time, time awaiting merge, PR size, and counts of opened, merged, closed, and merged-without-approval PRs | PR trends |
get_review_trends | Review request time, and counts of submitted reviews (approved, changes requested, commented) | PR reviews |
get_dora_trends | Deployment frequency, lead time for change, change failure rate, and incident time (MTTR) | DORA metrics |
Filters and aggregations
The trend tools accept the same options as the Metrics API. Your agent can:
- Filter by repo, base branch, team, user, or label, exclude bots and draft PRs, and ignore small PRs (by lines changed).
- Restrict results to a project, by its name or ID. Only the project’s repos are included, and if the project covers only some teams, only their activity is counted.
- Split results by repo, team, user, or label, to compare them side by side.
- Exclude weekends from durations, in your own time zone.
DORA trends support filtering and splitting by repo, and restricting to a project (a project’s teams don’t affect DORA metrics).
Drill-down tools
Drill-down tools list the individual items behind a single trend data point. They let your agent explain why a metric moved, for example by listing the PRs with the longest pickup times in the week that pickup time spiked.
| Tool | Lists |
|---|---|
get_pr_trend_observations | The PRs behind a get_pr_trends metric |
get_review_trend_observations | The reviews behind a get_review_trends metric |
get_dora_trend_observations | The deploys, PRs, or incidents behind a get_dora_trends metric |
Results are sorted by value (largest first) by default, or by time for count metrics, and are paged in batches of up to 100. Drill-downs take the same filters, including the project, as the trend call they drill into.
Open PR status
| Tool | Returns |
|---|---|
get_pr_status | A snapshot of currently open PRs: how many there are, and how long they’ve been open, waiting for review, or waiting to merge. It can list the individual PRs, too. |
It supports the same filters and splits as get_pr_trends, including restricting to a project. See
PR status.
Project tools
Project tools describe your organization’s GitDailies Projects. A project covers a set of the repos that your organization follows (and optionally only the activity of some teams), and can have its own alerts and scheduled report.
| Tool | Returns |
|---|---|
list_projects | Your organization’s projects, with their IDs |
get_project | A project’s details: the repos and teams it covers, its owner and admins, when its scheduled report runs and where it’s sent (email, Slack, or Telegram), and the definitions of its alerts |
get_project_triggered_alerts | A project’s alerts that triggered in the last 48 hours (up to 7 days), with the events that triggered them. Only events in project repos that you can access on GitHub are included. |
Your agent can also pass a project’s name or ID to any of the metric tools above, so you can ask about a project’s PR trends, review trends, DORA metrics, or open PRs. A project name is matched case-insensitively, and your agent uses the ID if two projects share a name.
Personal tools
Personal tools describe you: the GitHub user who authorized the connection. They power the same views as your Personal Summaries.
| Tool | Returns |
|---|---|
get_my_open_prs | Your open PRs, including drafts, oldest first |
get_my_review_requests | Open PRs where your review is still outstanding, whether it was requested from you or from one of your teams, oldest first |
get_my_merged_prs | Your PRs merged in the last 7 days (up to 30) |
get_my_submitted_reviews | Reviews you submitted in the last 7 days (up to 30), with their PRs |
get_my_triggered_alerts | Your personal alerts that triggered in the last 48 hours (up to 7 days), with the events that triggered them. Team and project alerts aren’t included. |
Connection info
| Tool | Returns |
|---|---|
get_connection_info | The GitHub organization or user that this connection is bound to, its endpoint, its plan, and whether that plan includes MCP access |