Skip to main content
Glama
213,351 tools. Last updated 2026-06-19 15:39

"Information about Git, a version control system" matching MCP tools:

  • Get a journey by ID. Pass version=draft to retrieve the working draft, or version=vN for a historical version. Defaults to published.
    Connector
  • Fetch one accessible verifier version (``scope=user`` only). ``verifier_id`` accepts verifier UUID string or accessible user-scope name when the caller has owner or tune access. Platform ``system:...`` aliases and system verifier UUIDs are never returned (NotFound): system rows are run-only and their internal config never surfaces through list, get, deploy, or revoke. Defaults to the current version; pass ``version`` to pin. Returns the full deploy-time payload (``criterion``, ``input_contract``, ``input_fields``, ``few_shot_examples``, ``judge_model_config``, ``reasoning_field_description``) plus ``config_hash`` (canonical-JSON SHA-256 over the config) so callers can detect drift across versions. Requires owner or tune access; an unauthorized or revoked verifier surfaces as NotFound. Platform-managed verifiers are run-only and never returned here.
    Connector
  • Create or append a version on a user-owned semantic verifier. A semantic verifier is a single judgment ("does this output satisfy this criterion?") evaluated by an LLM judge. Verifiers are private and owner-scoped. Workflows reference them by ``verifier_id`` (or ``verifier_id@version``). You cannot deploy a **new** verifier whose ``name`` matches an active platform ``scope=system`` verifier: those definitions are server-owned, never listed or fetched, and only executable through ``run_verifier``. Versioning: the first deploy with a given ``name`` creates the verifier at version 1. Re-deploying the same ``name`` appends a new version and requires ``expected_version_token`` from the latest known version (returned by deploy/list/get). A new verifier must omit the token; an existing one without a token returns Conflict. Input contracts: - ``text``: ``input_fields`` required, ``media_url`` rejected. - ``text_image``: ``input_fields`` plus ``media_url`` required at run time. - ``image``: ``input_fields`` empty, only ``media_url`` at run time. Few-shot examples (3 to 10 typical) calibrate the judge; each example must match the contract (text-only inputs, text+image, or image-only). Returns: ``{verifier_id, name, current_version, version, version_token, status, input_contract, config_hash}``. Persist ``version_token`` for the next re-deploy.
    Connector
  • List the OpenFEMA datasets this pack knows about, with their entity name, current version, and a description. Also documents the OData filter syntax and response shape. Call this first to discover what query_dataset can target.
    Connector
  • Find vulnerabilities affecting a package — optionally narrowed to a specific version, or alternatively by git commit hash. Pass package_name + ecosystem (npm / PyPI / Maven / NuGet / RubyGems / crates.io / Packagist / Hex / Pub / Go / Debian / Alpine / Ubuntu / Linux). Returns shaped vuln list with severity_level, affected_summary (introduced→fixed ranges), aliases, references, advisory_url. Use for "is lodash 4.17.4 safe", "what hits requests<2.20", "every CVE for log4j".
    Connector
  • Permanently and immediately erase a single non-current workflow version. This is permanent: the version row, all its attached files, and any content that is no longer referenced by any surviving version or published template version are removed from the live system at once. There is no recovery path. Use ``archive_workflow`` if you want a reversible alternative for the whole workflow. Encrypted backups age out within the platform's standard retention window (up to three months), so the data is not instantly erased from all systems everywhere, but it is no longer accessible through any product surface after this call. The current (live) version cannot be erased with this call. Use ``delete_workflow`` to permanently remove the entire workflow including its current version. Version numbers remain monotonic with a gap where the erased version was. Surviving versions are not renumbered. Owner only. Pointing at another user's workflow raises NotFound.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.

  • Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.

  • DESTRUCTIVE: Restore an app to a previous version using git reset --hard. This permanently overwrites all current files with the state from the specified commit — any changes made after that commit will be lost and CANNOT be recovered. You MUST confirm with the user before calling this tool. Use list_versions to show the user available versions first.
    Connector
  • Patch a single chart in an existing dashboard by chart ID. Provide only the chart fields to change. Set a field to null to remove it. Use overwrite=true to skip version conflict checks, or provide the current dashboard version for optimistic concurrency control.
    Connector
  • Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.
    Connector
  • Permanently and immediately erase a single template version. This is permanent: the version row, all its attached files, all version verification records, and any content no longer referenced by any surviving version or workflow version are removed from the live system at once. There is no recovery path. Use ``archive_template`` if you want a reversible alternative for the whole template. Encrypted backups age out within the platform's standard retention window (up to three months), so the data is not instantly erased from all systems everywhere, but it is no longer accessible through any product surface after this call. Serving gate: the version must first be unpublished (``unpublish_template_version``) before it can be erased. A still-published version cannot be permanently deleted because it is currently being served to readers. Unpublish it first, then call this operation. To remove the entire template including all its versions, use ``delete_template`` instead. Version numbers remain monotonic with a gap where the erased version was. Surviving versions are not renumbered. Owner only. Pointing at another user's template raises NotFound.
    Connector
  • Update an existing dashboard by UID. Provide the full dashboard JSON document. Use overwrite=true to skip version conflict checks, or provide the current version number for optimistic concurrency control.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Get the deployment and version history (git commits) for a project. Shows all schema changes with commit SHA, timestamp, and message. USE CASES: Review what changed between deployments, find the last working version before issues started, get commit SHA for rollback_project.
    Connector
  • Return a focused write-up of the three DRS modeling primitives: Constraint (rate-limiter), Buffer (accumulated state), Interrupt (stoppage). Use this when the user asks specifically about modeling primitives or how to spell a system in DRS. Deterministic text.
    Connector
  • Fetch one user-owned image generator at head or a pinned version. ``generator_id`` accepts a UUID string. Platform ``system:...`` tier aliases and system generator UUIDs are not returned here (NotFound): system generators are run-only and their internal config never surfaces through list, get, deploy, or revoke. Defaults to the current version; pass ``version`` to pin. Returns the full deploy-time payload (``provider``, ``model``, ``generation_contract``, ``default_params``) plus ``config_hash`` (SHA-256 over the config) so callers can detect drift across versions. Requires ownership; a cross-user or revoked generator surfaces as NotFound.
    Connector
  • IMPORTANT: Always use this tool FIRST before working with Vaadin. Returns a comprehensive primer document with current (2025+) information about modern Vaadin development. This addresses common AI misconceptions about Vaadin and provides up-to-date information about Java vs React development models, project structure, components, and best practices. Essential reading to avoid outdated assumptions. For legacy versions (7, 8, 14), returns guidance on version-specific resources.
    Connector
  • Create or append a version on a user-owned image generator. An image generator is a named, versioned configuration that routes image generation calls to a specific model. Generators are private and owner-scoped. Workflows reference them by UUID or ``uuid@version``. You cannot deploy a new generator whose ``name`` matches an active platform ``scope=system`` generator (those are tier-level configs that are run-only and not listed or fetched). Versioning: the first deploy with a given ``name`` creates the generator at version 1. Re-deploying the same ``name`` appends a new version and requires ``expected_version_token`` from the latest known version (returned by deploy/list/get). A new generator must omit the token; an existing one without a token returns Conflict. Deploy-time validation: the ``model`` is checked against the pricing layer. A model that does not resolve to a known image endpoint with an authoritative price is rejected before any row is written. Returns: ``{generator_id, name, description, current_version, version, version_token, status, scope, provider, model, generation_contract, config_hash, created_at}``. Persist ``version_token`` for the next re-deploy.
    Connector
  • Create a draft version by reverting to a previous version's config. Copies components, config, and pricing from the target version. If a draft already exists, updates it in-place (single-draft rule). Use `stackversions` first to find available version numbers. REQUIRES: session_id from convoopen response (format: sess_v2_...), version (target version number).
    Connector
  • List files and directories in any public git repo. Supports fuzzy file search (query parameter), language/path filtering, and depth control. Combine query with path_filter to search within a directory subset. Use to explore project layout, find files by name, or browse specific directories. Results capped at 1000 files; response includes total_files, files_shown, and truncated fields. Use language or path_filter to narrow large repos. Dependency/build directories excluded by default.
    Connector
  • Get the name, organization, country, and description for an Autonomous System number. Lightweight version of as_whois.
    Connector