Schema | ci-triage-mcp

ci-triage-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

Features and capabilities supported by this server

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
get_pr_checksA	List all CI checks for a GitHub PR with conclusion + URL. Input: {repo: "owner/repo", prNumber: number}. Returns aggregated check rollup.
get_failed_jobsA	List only failed jobs for a workflow run. Input: {repo: "owner/repo", runId: number}. Returns jobs with conclusion=failure: name, databaseId, url.
get_job_logs_tailA	Fetch tail of a failed job log. Input: {repo: "owner/repo", jobId: number, lines?: number=80}. Returns last N lines of the job log (cleaned of ANSI + timestamp prefixes).
grep_job_logsA	Grep a job log for lines matching a regex (case-insensitive). Returns matching lines with 2 lines context before/after. Use when failure is mid-log (E2E tests, build errors) rather than at the tail. Input: {repo, jobId, pattern: string, maxMatches?: number=50}.
summarize_pr_failureA	End-to-end triage: find failed checks on a PR, tail each failed job log, extract error/fail/first-failing-test lines. Input: {repo, prNumber}. Returns per-failed-job summary with likely root cause.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aamar-shahzad/ci-triage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server