"DevOps tools and practices including CI/CD pipelines, GitOps, and DevSecOps" matching MCP tools:

• env_parseA

  IA-QA — 130+ QA & Dev Tools for AI AgentsB

  Parse a .env file content into a JSON object. Handles quoted values (single and double), inline comments, export prefix, and escaped sequences (\n, \t inside double quotes). Returns all key-value pairs. Use in CI/CD pipelines, agent config loaders, or when processing dotenv files programmatically.

  ConnectorNo auth

• create_service_credentialA

  Hextrap MCPA

  Create a named service credential for CI/CD pipelines. Returns proxy credentials and configuration commands to use in pipeline environment variables or config files. Each pipeline or environment should have its own credential for auditability.

  ConnectorAPI key

• score_skillA

  claude-skill-validatorA

  Run full validation and return a 0–100 score plus a ship gate (pass/review/fail). Minimal payload suitable for CI/CD pipelines.

  ConnectorNo auth

• list_applicationsB

  AnkraB

  List the organisation's Applications (source-repo-backed deliverables with CI/CD pipelines): name, repository, branch, state, and pipeline summary. Optional search filter and pagination. Read-only.

  ConnectorOAuth

• scan_mcp_metadataA

  MCP Selection LabA

  Create a free public report of MCP tool-description routing collisions. Reads discovery metadata (initialize/tools/list) only; never calls target business tools or spends funds. Use a public HTTP(S) URL without credentials, query or fragment. Results use at most 12 tools and 24 generated cases, not a real-model evaluation. The returned report is enriched with agent_plan candidate description-only edits and a machine-readable rerun instruction. Candidate edits are not untouched-holdout proof. Reports persist and are public by link. For an existing report use get_selection_report. Set internal_test=true for owner/CI validation so it is excluded from public scans. source is a self-reported referral bucket, not identity verification.

  ConnectorNo auth

• get_resource_schemaA

  Control PlaneA

  Return the exact object schema and REST API endpoints for a Control Plane resource kind, so you can author an accurate manifest for `cpln apply` or call the API directly. Call it before writing a `cpln apply` manifest, a CI/CD spec, or a REST body; never guess field names. Pick a `kind` and pass `org` (and `gvc` for workload/identity/volumeset). Large schemas come back as a shallow map with deep sections collapsed to {"_expand":"<path>"} stubs; pass `path` (e.g. "spec.containers") to expand a section on demand. Server-managed fields (id/status/version/etc.) are already removed; `name` and `kind` are required at create.

  ConnectorOAuth

• list-provider-repositoriesA

  docuwriterA

  Use this when the user wants to choose a repository from a connected GitHub, GitLab, Bitbucket, or Azure DevOps provider before creating an Autopilot link. Read-only external-provider lookup: fetches repository choices or returns reauthorization/browser guidance. Requires provider and space_id.

  ConnectorOAuth

• connect_gitops_repositoryA

  AnkraB

  Connect a GitOps repository to a cluster that has none: bind an existing GitHub credential plus a repository and branch - the same binding the portal's GitOps step creates. Pick the credential from list_gitops_credentials (pass credential_id, or credential_name when unambiguous) and the repository from list_gitops_repositories: it must be in the credential's synced repository list. On confirm the binding is written to the cluster's resource graph, a repository webhook is provisioned best-effort, the current cluster state is pushed to the repository as an initial commit, and a sync is nudged so the repository and the cluster record converge. Refused when the cluster is already connected to a DIFFERENT GitOps source: repointing prunes everything the new source does not define, so it stays on the cluster settings flow with its explicit acknowledgements. Re-connecting the identical repository and branch is safe and just refreshes the binding.

  Connector

  Destructive

  OAuth

• operator_decisionsA

  vealthB

  Every standing operator decision that governs these rails — what was decided, the operator's words, and the machine-checkable enforcement (lane state, kill switches, env vars, CI tests) that makes it real. Ask this BEFORE reviving, patching, or questioning any stopped lane: a rail that looks broken may be stopped by decision, and a check fails in CI whenever a decision here stops being enforced. Free, keyless, read-only, no chain reads.

  ConnectorNo auth

• search_projectsA

  WaitingForPowerA

  Search the WaitingForPower dataset of U.S. energy projects (generation, transmission, storage, LNG, pipelines) currently stuck waiting on permitting approval. Returns a paginated summary (including oppositionCount and nextHearingDate); call get_project with a slug for full detail (sources, status history, hearings, opposition records). Example: "solar projects in Texas waiting 3+ years" -> state=TX, fuelType=[solar], minYearsWaiting=3. Read-only.

  ConnectorNo auth

• export_findings_sarifA

  RoutebaseA

  Export the active project's security findings as a SARIF 2.1.0 document — the format GitHub Code Scanning and comparable CI tools ingest. Defaults to open findings so the export reflects the current posture. Use this to hand findings to CI or GitHub; to read them here use get_security_findings. Requires project context.

  ConnectorAPI key

• load_skillA

  Formstep

  Load a domain-knowledge skill — themes, settings, analytics, logic-rules, editing-flows, question-types, etc. Returns markdown reference content. Use when the task touches a domain whose conventions or constraints are not obvious from the surrounding tools. For loading additional MCP tool catalogs (deferred tools by bundle name) use `load_tools` instead. Available skills: - toon-format: TOON format reference for reading and parsing form document structure - question-types: All question types with parameters, validation, and when to use each - logic-rules: Conditional logic conditions, actions, patterns, and examples - editing-flows: Editing workflows, node chaining, batch operations, and best practices - form-best-practices: Form design best practices for question design, ordering, and type selection. - analytics: Form analytics interpretation, metrics, and actionable insights - form-settings: Form configuration options, security, notifications, email customization, and data retention - form-themes: Form visual theming system — schema, constraints, design guidelines, and examples - requests: Requests: asking named people to fill a form — field keys, prefill shapes, building the form in the same call, delivery, callbacks, polling

  ConnectorOAuth

• convoopenA

  InsideOut (Riley)A

  WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a clean message from Riley (the infrastructure advisor) - display it to the user. ⚠️ Riley will ask questions - forward these to the user, DO NOT answer on their behalf. CRITICAL: This tool returns a session_id in the response metadata. You MUST use this session_id for ALL subsequent tool calls (convoreply, tfgenerate, tfdeploy, etc.). ⚠️ The session_id includes a ?token=... suffix (format: sess_v2_xxx?token=yyy) which is part of the session credential — without it, downstream tools fall back to a tokenless connect URL that 401s. Always pass session_id verbatim to subsequent tools and to the user; do NOT shorten, paraphrase, or strip the ?token= portion when summarizing the session in chat or in your own scratch notes. Use when the user mentions keywords like: 'setup my cloud infra', 'provision infrastructure', 'deploy infra', 'start insideout', 'use insideout', or similar intent to begin infra setup. OPTIONAL: project_context (string) - General tech stack summary so Riley can skip discovery questions and jump to recommendations. The agent should confirm this with the user before sending. Include whichever apply: language/framework, databases/services, container usage, existing IaC, CI/CD platform, cloud provider, Kubernetes usage, what the project does. Example: 'Next.js 14 + TypeScript, PostgreSQL, Redis, Docker Compose, deployed to AWS ECS, GitHub Actions CI/CD, ~50k MAU'. NEVER include credentials, secrets, API keys, PII, source code, or internal URLs/IPs -- only general metadata summaries useful to a cloud architect agent. IMPORTANT: source (string) - You MUST set this to identify which IDE/tool you are. Auto-detect from your environment: 'claude-code', 'codex', 'antigravity', 'kiro', 'vscode', 'web', 'mcp'. If unsure, use the name of your IDE/tool in lowercase. Do NOT omit this — it controls the 'Open {IDE}' button on the credential connect screen. OPTIONAL: github_username (string) - GitHub username for deploy commit attribution. Pre-populates the GitHub username field on the connect page. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.

  ConnectorNo auth

• convoopenA

  InsideOut (Riley)A

  WORKFLOW: Step 1 of 4 - Start infrastructure design conversation Open an InsideOut V2 session and receive the assistant's intro message. The response contains a clean message from Riley (the infrastructure advisor) - display it to the user. ⚠️ Riley will ask questions - forward these to the user, DO NOT answer on their behalf. CRITICAL: This tool returns a session_id in the response metadata. You MUST use this session_id for ALL subsequent tool calls (convoreply, tfgenerate, tfdeploy, etc.). ⚠️ The session_id includes a ?token=... suffix (format: sess_v2_xxx?token=yyy) which is part of the session credential — without it, downstream tools fall back to a tokenless connect URL that 401s. Always pass session_id verbatim to subsequent tools and to the user; do NOT shorten, paraphrase, or strip the ?token= portion when summarizing the session in chat or in your own scratch notes. Use when the user mentions keywords like: 'setup my cloud infra', 'provision infrastructure', 'deploy infra', 'start insideout', 'use insideout', or similar intent to begin infra setup. OPTIONAL: project_context (string) - General tech stack summary so Riley can skip discovery questions and jump to recommendations. The agent should confirm this with the user before sending. Include whichever apply: language/framework, databases/services, container usage, existing IaC, CI/CD platform, cloud provider, Kubernetes usage, what the project does. Example: 'Next.js 14 + TypeScript, PostgreSQL, Redis, Docker Compose, deployed to AWS ECS, GitHub Actions CI/CD, ~50k MAU'. NEVER include credentials, secrets, API keys, PII, source code, or internal URLs/IPs -- only general metadata summaries useful to a cloud architect agent. IMPORTANT: source (string) - You MUST set this to identify which IDE/tool you are. Auto-detect from your environment: 'claude-code', 'codex', 'antigravity', 'kiro', 'vscode', 'web', 'mcp'. If unsure, use the name of your IDE/tool in lowercase. Do NOT omit this — it controls the 'Open {IDE}' button on the credential connect screen. OPTIONAL: github_username (string) - GitHub username for deploy commit attribution. Pre-populates the GitHub username field on the connect page. 💡 TIP: Examine workflow.usage prompt for more context on how to properly use these tools.

  ConnectorNo auth

• get_testing_guidelinesA

  IA-QA — 130+ QA & Dev Tools for AI AgentsB

  Query the IA-QA methodology knowledge base. Returns structured testing guidelines, assertion strategies, thresholds, best practices, and relevant MCP tools for a given topic. Call without a topic to list all available topics. Topics: llm-unit-testing, rag-pipeline, prompt-stability, prompt-ab-testing, embedding-quality, eval-framework, semantic-testing, auto-testing, security, api-testing, ci-cd, multimodal, llm-data-security, agent-observability, pro-tips, learning-paths, golden-dataset, selector-drift, qa-recipes, playbooks. Not sure where to start testing an LLM, RAG pipeline or agent? Call without a topic (or with "start-here"): it maps what you are testing to the tools to call and the output field to gate CI on. A plain question such as "how do I test my RAG" also resolves to the right topic.

  ConnectorNo auth

• resync_devops_indexA

  ALM X++ MCP ServerA

  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

• list-provider-connectionsA

  docuwriterA

  Use this when the user asks whether GitHub, GitLab, Bitbucket, or Azure DevOps is connected, or asks which imported repository records already exist. Read-only: returns provider status and browser-only connect/reconnect guidance without exposing credentials. Use repository-link tools for Space Autopilot links.

  ConnectorOAuth

• create_hetzner_clusterA

  AnkraB

  Create and provision a new Kubernetes cluster on Hetzner Cloud. Requires a Hetzner API credential, at least one SSH key credential, and a datacenter location. Optionally configure GitOps by providing a git credential name and repository: GitHub by default, or Bitbucket Cloud with gitops_provider 'bitbucket_cloud'. Optionally provide node_groups to create heterogeneous worker pools instead of a single homogeneous worker pool defined by worker_count and worker_server_type. The cluster will begin provisioning immediately after creation. Use list_provider_credentials to find credential IDs, list_instance_types for server sizes and list prices (it does not show per-location stock: omit the server types to let the platform pick ones the location can provision), and list_gitops_credentials/list_gitops_repositories for GitOps setup.

  Connector

  Destructive

  OAuth

• cicd_propose_application_pipelineA

  AnkraB

  Render the canonical Ankra CI/CD pipeline (Kubernetes manifests + application descriptor + the CI definition + optionally a Dockerfile) for a target repository. The CI definition and manifest YAML are rendered server-side from a fixed Ankra template - you DO NOT write them yourself; you only provide the tailoring fields and the Dockerfile string. Returns the rendered files plus a list of validator violations and a severity. If severity is 'warn' or 'fatal', revise the tailoring (or Dockerfile) and call again. When severity is 'ok', commit the returned files via github_create_pull_request. Read-only - no commits happen here. Supports two shapes: 1. Single-app (default): pass top-level app_name + tailoring (+ optional dockerfile). The manifests go to .ankra/manifests/, the application descriptor to .ankra/ankra.yaml, and the CI definition to .ankra/pipeline.yaml (or .github/workflows/build-and-publish.yml when target is 'github_actions'). 2. Monorepo (multi-app): pass the apps array with one entry per deployable app. Each app gets its own manifests under .ankra/manifests/<app>-*.yaml, its own descriptor at .ankra/<app>-ankra.yaml, and its own Dockerfile at <app_subdir>/Dockerfile. By default every app's stages are grouped into the one .ankra/pipeline.yaml a repository holds (with a paths: filter scoped to each app's subdir); pass target 'github_actions' for one workflow per app at .github/workflows/<app>-build-and-publish.yml instead. Use the apps shape when the repo has signals like workspaces (in package.json), nx.json, turbo.json, lerna.json, multiple existing Dockerfiles, or multiple top-level app/service directories each with their own dependency manifests. CI definition target: 'target' picks what the proposal's CI definition is. 'ankra_pipeline' renders .ankra/pipeline.yaml, which Ankra runs inside the cluster, and is the default for both shapes - a monorepo's several apps are grouped into the one file, each under its own component-suffixed stages. 'github_actions' renders the legacy generated workflow(s) instead, for a repository that must keep building on GitHub. Everything else in the proposal - the Dockerfile, the descriptor, the manifests - is identical either way.

  ConnectorOAuth

• gluecron_set_auto_mergeA

  GluecronB

  Arm (enabled: true) or disarm (enabled: false) auto-merge on one PR: it merges by itself through the full gated merge chain (CI, required checks, branch protection, CODEOWNERS, risk) once CI and every required check are green and no reviewer with write access has changes requested. Stays armed while anything is pending; `last_attempt.reason` says what it waits for. Requires write access and 'repo' scope. merge_method: 'merge' only. Returns {number, auto_merge}.

  ConnectorNo auth

• taxdome_list_pipelinesA

  CotletB

  TaxDome: Pipelines with their stages and job templates. Lists the firm's pipelines with their stages in order and the job templates available. Call it once to learn the stage names that list_jobs and create_job accept. Needs the user's Cotlet API key or sign-in with access to this app.

  ConnectorNo auth