Skip to main content
Glama
109,587 tools. Last updated 2026-04-18 00:58
  • Get pull request metrics including cycle time (time from first commit to merge), throughput (PRs merged per week), review health (time to first review, reviewer distribution), and PR size trends. Use this to assess code review efficiency and identify bottlenecks in your delivery pipeline. Read-only.
    Connector
  • List currently open pull requests with their age in hours, size (additions + deletions), and reviewer assignments. Use this to identify stale or large PRs that may be blocking the team. Optionally filter to high-risk PRs only (large, old, or no reviewers). Read-only.
    Connector
  • TOOL for retrieving current user's owned resources and work items across the Cortex workspace. FLEXIBLE REQUEST STRUCTURE: The request accepts an object with optional fields for each resource type: - myEntitiesRequest: Fetch entities (services, resources, domains) owned by the user - myTeamsRequest: Fetch teams the user belongs to - myScorecardsRequest: Fetch scorecards associated with user's entities - myOpenPRsRequest: Fetch user's open pull requests across all Git repositories - myRequestedReviewsRequest: Fetch PRs where user is requested as a reviewer - myWorkItemsRequest: Fetch work items (Jira, Linear, Azure DevOps) assigned to the user Set one or more fields to fetch multiple resource types in a single call. All results are combined into a single response array with mixed item types. RESPONSE STRUCTURE: Returns a single array of items where each item has an 'itemType' field indicating its type: - 'entity': Catalog entities (services, resources, domains) - 'team': Teams the user belongs to - 'scorecard': Scorecards for user's entities - 'pull_request': Open pull requests authored by the user - 'review_request': Pull requests where user is requested as reviewer - 'work_item': Work items (issues/tickets) assigned to the user EXAMPLES: 1. Fetch only services: {"myEntitiesRequest": {"entityTypes": ["service"]}} 2. Fetch teams and their entities: {"myTeamsRequest": {"includeMembers": true}, "myEntitiesRequest": {}} 3. Get all work (PRs, reviews, Jira tickets): {"myOpenPRsRequest": {}, "myRequestedReviewsRequest": {}, "myWorkItemsRequest": {}} 4. Search entities with filters: {"myEntitiesRequest": {"query": "payment", "ownershipSource": "DIRECT", "entityTypes": ["service", "resource"]}}
    Connector
  • Code review council. Senior Engineer, Security Reviewer, and Performance Analyst analyze your code and a moderator synthesizes their findings.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Energy data from EIA: electricity, fuel prices, and renewables

  • The Jam MCP server provides AI tools with instant bug context without manual prompting, enabling a streamlined workflow from bug identification to ticket creation and pull request generation without switching between tools.