ContextBridge
Related Servers
Alternatives to ContextBridge
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceA policy-aware MCP server for GitHub and GitHub Actions that enables safe AI-assisted infrastructure workflows—inspecting repositories, preparing branches and pull requests, and constrained remote mutations behind explicit preview-bound approval tokens.18MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to perform scoped, policy-enforced GitHub operations with allowlisted repositories and tools, protected branches, approval gates, dry runs, secret redaction, and a tamper-evident audit log.MIT
- FlicenseNot gradedqualityDmaintenanceA self-hosted GitHub MCP server with per-repository guardrails for AI agents, enabling fine-grained access control and audit trails.-
- AlicenseNot gradedqualityBmaintenanceTurns any AI coding agent or MCP client into a governed DevOps engineer by exposing policy-enforced tools for Kubernetes, Docker, Jira, Git/PR, CI/CD, AWS, Terraform, and incident response, with approvals, audit logging, secret redaction, and rollback enforced outside the model.13 PyPI6Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server that provides a security gateway for AI agents, enforcing allow/confirm/deny policies on tool calls and requiring human approval for risky operations, with full audit logging.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with GitHub issues, pull requests, and Actions workflows through MCP tools.-
TDQS
Scored across 27 tools
Tools separate cleanly into read-only GitHub queries, mutation requests, approval actions, and telemetry. A few telemetry tools (get_audit_summary vs get_evaluation_summary) could be confused, but descriptions clarify their distinct sources. No two tools appear to do the same operation.
Most tools follow verb_noun snake_case (list_repositories, create_issue, get_workflow_runs). Two exceptions: server_info and health lack verbs, and github_connection_status is a noun phrase. Consistency is strong overall but not perfect.
27 tools is above the comfortable range. The count is inflated by four telemetry tools that could arguably be combined. However, the server covers multiple subdomains (GitHub reads, mutation requests, approval execution, system health), so the count is defensible albeit heavy.
Read-only GitHub coverage is broad (repos, issues, PRs, commits, code, workflows, file contents). Mutation coverage is limited to issues (create, comment, label, close, reopen) with no PR mutations or issue editing. The human-approval workflow is well-defined, but the lack of broader write operations creates noticeable gaps for a GitHub-oriented server.