"Information about New Relic software and services" matching MCP servers:

Enables Claude to function as a full-stack software engineer with comprehensive development capabilities including project creation, database management, frontend/backend development, testing, deployment, and DevOps operations across multiple frameworks and technologies.

Monitor failing GitHub Actions workflows, auto-fix them with OpenCode, and retry the run — driven by a workflow_run webhook, coordinated through an MCP server.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables AI coding tools to scaffold, build, and deploy Node.js or Python apps to Varity with a single command, automatically provisioning databases and backend services.

SSWP MCP — Deterministic software attestation for AI-augmented development. Witness any repo through a 5-gate pipeline, adversarially probe dependencies, and produce self-verifying .sswp.json attestations. Fleet registry across 131 nodes with tamper-proof audit ledger and FTS5 search. Agent-native — one tool call from Hermes, Claude, or Cline.

Deploys and manages projects on Swigs Cloud from any MCP client, turning folders or git repositories into live HTTPS sites in about two minutes.

A Model Context Protocol server that enables AI assistants to interact with Azure DevOps services, allowing users to query work items with plans to support creating/updating items, managing pipelines, handling pull requests, and administering sprints and branch policies.

Autonomous coding pipeline exposed as an MCP server: plan, dispatch, review, and merge software stories through worktree-isolated agents. A frontier model (Claude) handles judgment — planning, review, risk adjudication — while a local model does the implementation, gated by TDD and a merge-time test rerun on the rebased branch.

Aegis keeps Claude Code, Codex CLI and Antigravity on your project's rules via a zero-dependency Model Context Protocol (MCP) server (aegis-mcp), AGENTS.md / CLAUDE.md bootstrap, git pre-commit hooks, and CI governance (aegis check). It serves each agent just-in-time rules for the files it is about to edit, then enforces AST and repository invariants before commit and in pull requests.

Enables Claude to run structured software development pipelines by directing it through sequential phases, validating evidence before advancing, and persisting state in SQLite for resumption across sessions.

Checks whether software dependencies (npm packages, GitHub Actions, MCP servers, Docker images) are alive, dormant, abandoned, archived, or deleted using dated observations from lastseen.dev.

Enables AI agents to enforce a software delivery standard by validating artifacts against declarative rules, providing templates, glossary terms, and pass/fail verdicts with actionable blockers.

Model Context Protocol (MCP) server for Octopilot — enables AI agents to detect, generate, build, and wire up new repositories end-to-end using the Octopilot CI/CD toolchain.

Read-only Playwright CI results for coding agents: tells whether a failing test is new in this PR, already failing on main, or known flaky, with per-test history.

Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.

repo-release-tools mcp-server automates the software release process by managing version bumps, changelog generation, and releases. It streamlines repository maintenance by handling repetitive release tasks directly through your AI assistant.

Enables management of Railway.app infrastructure through natural language, including deploying services from GitHub repos or Docker images, managing environment variables, monitoring deployments, and configuring networking and volumes.

Checks how long ago a package version was published and returns the newest version older than a minimum age (3 days by default), so an agent avoids brand new releases when adding dependencies. Also checks lockfiles across 15 ecosystems; read-only.

Enables agents to deploy software via GitHub Actions only with a signed receipt, providing gated tools to resolve refs, list deployments/environments, and dispatch pipelines for a specific commit.

Enables management of Railway.app infrastructure through natural language, including deploying services, managing environment variables, monitoring deployments, and handling databases and volumes.

Enables AI coding agents to orchestrate the full software development lifecycle on GitHub, including planning, issue creation, code review, security triage, and release readiness checks.

Enables management of Railway.app infrastructure through natural language, allowing users to deploy services, manage environment variables, monitor deployments, and configure projects directly from MCP clients like Claude.

MCP server exposing the Laravel Forge API v2 with curated tools for deploys, logs, env, and services plus universal access to all 273 operations.

Enables management of Railway.app infrastructure through natural language, including deploying services, managing environment variables, monitoring deployments, and controlling project resources.

An MCP server that automates the full software development lifecycle through an AI-driven TDD state machine. It handles everything from task decomposition and test-driven development to integration testing and automated pull request creation.

Gives AI assistants read-only, multi-instance access to build data, analyzing large console logs server-side so the model receives only small, relevant excerpts. A shared team knowledge base of solved problems lets each new investigation start from what the team already knows.

Enables retrieving comprehensive information about GitLab merge requests, including details, commits, diffs, discussions, approvals, and CI/CD status, through natural language.

Enables AI assistants to answer questions about nixpkgs packages using nixkeeper's public data, covering outdated versions, Hydra build status and failures, update-bot attempts, related PRs and issues, CVEs, and what needs attention for a maintainer or team. It runs locally over stdio, reads only public data, and requires no account or token.

Enables MCP-compatible AI agents to deploy applications to Google Cloud Run by providing tools for deploying code, listing services, and managing Google Cloud projects.

A git-native merge gate. mergelock check compares two branches before they meet and reports the conflicts git itself won't tell you about: a function whose signature changed on one branch while the other branch added calls to the old signature, a symbol deleted on one side but still used on the other, the same function written twice.