Skip to main content
Glama
674,927 tools. Updated 2026-10-19 00:22

"A platform for Git-based version control and DevOps tools" matching MCP tools:

  • [~] PRIORITY TRIGGER: Use this tool when user mentions 'PR', 'Pull Request', 'list PRs', 'show PRs', 'active PRs', 'mes PR', 'liste des PR', 'pull requests ouverts', 'what PRs are open', 'PRs by [author]', 'PRs targeting [branch]'. NEVER call search_d365_code for PR listing requests. List Pull Requests in an Azure DevOps Git repository. If `repositoryId` is unknown, omit it and all repositories will be listed first. Filters: status (Active/Completed/Abandoned/All), author display name, target branch. Returns: PR ID, title, author, source->target branch, review status, linked work items, creation date. Use `ado_analyze_pr_impact` with a PR ID to get full D365 code impact analysis. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Code: Read scope).
    ConnectorNo auth
  • Liveness check for the Agent Watch API. Returns ok, service name, and version. Call this first to verify connectivity before using other tools.
    ConnectorNo auth
  • AZURE DEVOPS ONLY -- Query Work Items (Bugs, Tasks, FDDs, User Stories, CRs) in Azure DevOps. [~] PRIORITY TRIGGER: use this tool when the user mentions 'FDD', 'RDD', 'IDD', 'CR', 'Task', 'Workitem', 'Work Item', 'Bug', 'User Story', 'Feature', 'Issue', 'ticket', 'sprint', 'backlog', 'DevOps', 'liste des tâches', 'show tasks', 'find bugs', '#1234', 'WI#'. NEVER use this tool for: D365 labels (@SYS/@TRX), X++ code, AOT objects, tables, classes, forms, enums, error messages, 'c\'est quoi le label', 'search_labels', 'libellé', 'label D365'. For labels -> use search_labels. For D365 code -> use search_d365_code or get_object_details. Shortcuts: 'bugs' (all active bugs), 'my bugs' (assigned to me), 'recent' (updated last 7 days), 'sprint' (current iteration). Or pass any WIQL SELECT statement or a free-text title search. Use '*' with filters only. Returns max 50 work items with ID, title, type, state, priority, area, assigned-to. Requires DEVOPS_ORG_URL + DEVOPS_PAT env vars.
    ConnectorNo auth
  • Publish a NEW version of YOUR OWN published agent built here (instructions, skills and actions) for review. Pass the agent slug + a semver bump (patch|minor|major). You can fully EDIT the new version: system_prompt + example_prompts, AND (for an agent built here) the whole capability surface — pass `tools` (and optional `credential_slots` / `guardrails`) to add/remove/edit tools + action bindings + credential slots, and optional `price_type`/`price_cents` to change the price. Any capability change re-runs the same security scan + author-time auth_ref↔host check. `changelog` is optional when you edit tools (auto-drafted from the diff); otherwise pass 10–500 chars. The new version goes to admin review; your LIVE version keeps serving until it is approved (never auto-unpublished). A price change applies immediately (not retroactive). Owner-only. (Code-bundle agents re-version through the code wizard, not here.) An ACTION agent whose findagent.json lives in a GitHub repo you can write to should NOT take its tool array through this field path: call findagent_new_version (or findagent_repull) with `repo` instead, so the tools are read server side and never re-typed by a model. This field path stays for edits with no repo.
    ConnectorOAuth
  • Read what is published: the files of a website, app, or agent's active release. Without path it lists them; with path it returns one file's text. Pass release, a version from list_releases, to read an earlier release instead; publishing its files again rolls back. Read before you change something someone else built, so your publish carries their work forward rather than replacing it with yours. Binary files are listed and not returned. Pass git: true instead, when you can run git with network access, to get a read-only Git URL for the release's commit with the commands to clone it. Prefer it to reading files one at a time. The URL expires in an hour and cannot push; do not share or log it. git cannot be combined with path. Requires connecting a Valet account.
    ConnectorNo auth
  • Perform a Linux package vulnerability audit using SecDB. ## What this tool does Analyzes the installed packages of a Linux system-identified by OS and OS version-and returns vulnerability information plus a Markdown summary. The audit results are based exclusively on the package list provided by the user. ## When to use this tool Use this tool when the user wants to determine: - whether installed packages contain known vulnerabilities - whether a host, VM, container, or base image is affected by security advisories - which packages require patching or upgrading If the user does not know the valid values for `os` or `version`, first call the `linux_os` tool to retrieve the exact supported combinations. ## Inputs - **os**: Linux distribution identifier supported by SecDB (use `linux_os` to obtain allowed values). - **version**: OS version or codename corresponding to the selected distribution. - **packages**: list of installed packages, **one per line**, generated using the appropriate system command: ### For RPM-based distributions (RHEL, CentOS, Rocky, Alma, SUSE) rpm -qa --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' ### For DEB-based distributions (Ubuntu, Debian) dpkg-query -W -f='${Package} ${Version} ${Architecture}\n' ### For Alpine Linux apk list -I The raw output of these commands can be passed directly as the `packages` input (one package per line). ... python3 3.12.3-0ubuntu2.1 amd64 systemd 255.4-1ubuntu8.10 amd64 tmux 3.4-1ubuntu0.1 amd64 ... ## Outputs - **report**: structured objects describing the advisories affecting the audited packages. - **summary**: Markdown summary including total vulnerabilities, severity breakdown, and key findings. ## LLM usage guidelines - Never guess whether a package is vulnerable-always call this tool for Linux audits. - If `os` or `version` is unclear or missing, call `linux_os` and ask the user to choose a valid combination. - Normalize the package list to “one entry per line” if the user provides unstructured output. - The `summary` is already Markdown and can be shown directly. - Use `report` when deeper technical analysis is required.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    F
    maintenance
    Enables AI agents to analyze local Git repositories with commit logs, diffs, blame, statistics, and branch analysis using native git commands without requiring a GitHub API.
    29 npm
    MIT

Matching MCP Connectors

  • Decision Layer for AI Agents — 58+ tools, Advisor, MCP. Free key: POST /v1/register {}.

  • Latest versions, LTS windows, and EOL dates for 300+ products. Fresh ground truth for stale models.

  • Get detail for a CoreClaw worker. WHEN TO USE: Use before running a worker to inspect version, README, and parameters. 中文触发: 当用户要在 CoreClaw 中查询、运行、重跑、停止、导出或查看对应 worker/run/task 数据时使用。 WHEN NOT TO USE: Do not use public web search or code search for private CoreClaw platform data. Do not call excluded internal worker-version or internal-detail APIs. RETURNS: JSON with worker name, username, version, readme, and parameters. WORKFLOW: Follow with get_worker_input_schema and then run_worker.
    ConnectorNo auth
  • Get git access to an EXISTING artifact, for local development with a real git client. Use this when you HAVE a working shell with git and outbound network access AND the job suits a local checkout — a large refactor, running or testing the project, branches, or history rewriting. For ordinary reading and editing of an artifact’s files, prefer artifact-explore and artifact-edit: they need no shell, no git and no network of your own, and they change the same repository. An artifact is a real git repository. Pass the sessionId — the id of an existing artifact (e.g. the last path segment of a .../chat/<sessionId> URL, like "mr25vsjppVtbMx") — and this returns a gitRemoteUrl plus the authenticated principal’s commitAuthor. After cloning, apply the returned `git config user.name` and `user.email` instructions before committing; then edit files, commit, and `git push` — pushing updates the live artifact. The gitRemoteUrl holds a short-lived access token scoped to this one artifact (read-only or read-write, depending on your access). Tokens CANNOT be renewed: on a "token expired" git error, call this tool again for a fresh gitRemoteUrl and run `git remote set-url origin <new gitRemoteUrl>`, then retry. If a git command instead fails because the host cannot resolve or reach the server (DNS, proxy or firewall errors), do NOT retry it — that environment has no route to the git remote, so use artifact-edit instead. Treat the gitRemoteUrl as a secret. To rename an artifact or change its visibility, use artifact-update_metadata.
    ConnectorOAuth
  • Return MCP server liveness: version, origin, tool count, and catalog size. Use for hosted inspector probes (Glama / Smithery) or before diagnosing tool failures. Do not use for business outcomes — call vc_* tools or pay(slug=...) instead. No auth required. No side effects. Returns JSON {ok, service, version, origin, tools, catalog_resources}.
    ConnectorNo auth
  • Read-only. Return the status of one deploy: queued, building, ready, active, failed, superseded or skipped (a git push not published because of a limit or billing), plus the site url, build_mode (static or build) and, when available, recommendations (site checks: advice, not errors). Poll it after deploy_files or deploy_site until the status is active or failed; for the version history of a site use list_deploys, for build errors get_logs.
    ConnectorOAuth
  • Everything about one control by its slug: what it does, its control type, license and repository, the current release's properties, and download links for its solutions. Use it once search or list_components has given you a slug; use get_doc_page for installation and configuration instructions, which this does not return. An unknown slug, or a version the control never released, returns an error naming the tool to call instead. include_versions and include_related each cost an extra query, so leave them off unless you need the release history or similar controls.
    ConnectorNo auth
  • The most recent releases across every control on PCFHub, newest first: which control, which version, whether it is a prerelease, and when it shipped. Use it for what has changed hub-wide; for one control's own history call get_component with include_versions instead. Bounded by limit, at most 50, and not paged — there is no cursor, so it cannot walk back beyond the newest 50.
    ConnectorNo auth
  • Returns JSON with the GodPrompt content version, MCP server version, repository, bundled file sizes and purposes, and task-type/protocol catalog. Use it to verify which GodPrompt content/server version a client is connected to; use the content retrieval tools when you need the actual workflow text.
    ConnectorNo auth
  • Report this server's version, target PinBridge API and enabled capabilities. Use when a client connects for the first time, or when a call fails unexpectedly, to confirm the server is reachable and whether write tools are on. For the workspace's plan and quota use get_billing_status. Returns server version, pinbridge_base_url, transport and whether write tools are enabled. Needs no PinBridge scope.
    ConnectorAPI key
  • Generate and save AI analytics insights for workspace_id, optionally limited to platforms. regenerate=true forces a fresh analysis even when insights already exist. Default is free rule-based insights; opt in with coach: true for AI patterns across the period (optional date_from, date_to up to 90 days, platform); coach costs 12 credits, and with too little data it falls back to rule-based with a coachUnavailable reason and no charge. aidelly_get_analytics_insights reads saved insights without generating new ones. Retry-safe: a repeat call with the same idempotency_key returns the original result and is not charged again. Coach runs are limited to 5 a minute per API key.
    ConnectorNo auth
  • List GTM container version headers (newest first). Version headers include version_id, name, archived flag and entity counts. The Tag Manager API returns no creation or publish time and no author for a version, and does not mark which versions were published; get_gtm_version returns a version's notes and get_gtm_version_diff what changed between two versions. Tag Manager API: https://developers.google.com/tag-platform/tag-manager/api/v2
    ConnectorAPI key
  • Snapshot the project's current working tree as a named git version (the platform's version history). Call this BEFORE large or risky rewrites so the change can be rolled back or reviewed later; pass a short human-readable title (and an optional longer body) describing what this version captures. Returns the new commit_sha. Creating a version also discards any pending review change that has not been merged yet (the snapshot becomes the source of truth). Read-only sessions cannot call this.
    ConnectorAPI key
  • Search the official Redpanda documentation and return the most relevant sections from it for a user query. Each returned section includes the url and its actual content in markdown. Use this tool for all queries that require Redpanda knowledge. Results are ordered by relevance, with the most relevant result returned first. If you know the user's deployment platform, pass "platform" so results from the other platform's docs are excluded. Note that "platform" filters the sections already retrieved rather than re-running the search, so it can return substantially fewer sections: on a broker-level question where most matches come from the other platform's docs, it can cut a 15-section response to 1 or 2. Omit "platform" if you would rather have more context and judge platform relevance yourself from each section's url. If you know which Redpanda version the user runs, pass "version" (use 'current' for the latest release; its release number is also accepted). Unlike "platform", "version" is applied during retrieval, so it does not shrink the result set: it stops the same page being returned once per indexed version, which is otherwise most of the response. Version-neutral docs (Cloud, Connect, Agentic Data Plane, API reference) are always included. Omitting "version" searches the latest release.
    ConnectorOAuth
  • Make an HTTP API call with manual escrow protection. Full control over verification and timelock parameters. For most payments, use safe_pay instead — it auto-configures protection based on seller trust. Use x402_protected_call when you need: - Custom JSON Schema verification (not just "valid JSON + 2xx") - Hash-lock verification (exact response match) - Specific timelock durations - To override safe_pay's trust-based amount limits
    ConnectorNo auth
  • Get detail for a specific CoreClaw worker run by run_id. WHEN TO USE: Use when the user gives a run id or wants status/cost/detail for a specific run. 中文触发: 当用户要在 CoreClaw 中查询、运行、重跑、停止、导出或查看对应 worker/run/task 数据时使用。 WHEN NOT TO USE: Do not use public web search or code search for private CoreClaw platform data. Do not call excluded internal worker-version or internal-detail APIs. RETURNS: JSON with run status, worker, version, timestamps, usage, traffic, error, and result count. WORKFLOW: Follow with results, logs, export, rerun, or abort tools for the same run_id.
    ConnectorNo auth
  • WHEN: the user wants to force a full re-download and re-index of their Azure DevOps custom model. Triggers: 'resync', 'reindex', 'force sync', 'rebuild index', 'my model is stale', 'update index', 'mon index est vieux', 'rafraîchir l\'index', 'relancer l\'indexation'. Useful when the server's built-in PAT does not have access to the target DevOps organisation (e.g. a different Azure DevOps org or tenant). Pass a `pat` parameter to override the server PAT for this resync. The eviction + download runs in the background; returns status immediately. After calling, wait ~60 s then call `healthcheck` or any search tool to confirm the index is ready.
    Connector
    Destructive
    No auth