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 install 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 |
|---|---|---|
getPRTrends | 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 |
getReviewTrends | Review request time, and counts of submitted reviews (approved, changes requested, commented) | PR reviews |
getDORATrends | 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).
- 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.
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 |
|---|---|
getPRTrendObservations | The PRs behind a getPRTrends metric |
getReviewTrendObservations | The reviews behind a getReviewTrends metric |
getDORATrendObservations | The deploys, PRs, or incidents behind a getDORATrends 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.
Open PR status
| Tool | Returns |
|---|---|
getPRStatus | 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 getPRTrends. See
PR status.
Personal tools
Personal tools describe you: the GitHub user who authorized the connection. They power the same views as your Personal Summaries.
| Tool | Returns |
|---|---|
getMyOpenPRs | Your open PRs, including drafts, oldest first |
getMyReviewRequests | Open PRs where your review is still outstanding, whether it was requested from you or from one of your teams, oldest first |
getMyMergedPRs | Your PRs merged in the last 7 days (up to 30) |
getMySubmittedReviews | Reviews you submitted in the last 7 days (up to 30), with their PRs |
getMyTriggeredAlerts | 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 |
|---|---|
getConnectionInfo | The GitHub organization or user that this connection is bound to, its endpoint, its plan, and whether that plan includes MCP access |