OpsContext
Related Servers
Alternatives to OpsContext
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables authorized AI coding agents to securely access development machines, repositories, terminals, and processes through a policy-enforced, audited control plane.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables remote AI agents to read, patch, and (opt-in) execute commands in a local workspace, with all actions approved locally and fully audited.1MIT
- AlicenseCqualityAmaintenanceSecure agent coding runtime for local Git repos with policy enforcement, RBAC, sessions, approval workflow, and sandboxed writes, optionally connectable to ChatGPT via Secure MCP Tunnel.86MIT
- FlicenseNot gradedqualityCmaintenanceSecure local development platform that exposes controlled developer capabilities (FS, Git, search, command execution) to AI assistants via MCP with deny-by-default security and audit logging.-
- AlicenseNot gradedqualityBmaintenanceEnables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.306 npm1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.3Apache 2.0
TDQS
Scored across 22 tools
Tools cluster into clear domains (sessions, learnings, knowledge sources, project audit, monitoring) and most have a single obvious purpose. Minor overlap exists between run_audit and score_project, and between end_session and drift_status, but the descriptions are specific enough to prevent serious misselection.
Most tools follow a snake_case verb_noun pattern (list_sources, save_session, delete_learning, score_project), making the set predictable. A few names break the pattern—audit_verify, agent_cost, drift_status, activation_status—but these are still readable and not chaotic.
At 22 tools, the surface is on the heavy side and spans many distinct domains: knowledge, sessions, learnings, project audit, compliance, and licensing. The breadth is defensible, but the count lands in the 16-25 range that feels heavy for an agent to navigate.
Sessions and learnings have full create/read/update/delete coverage, and knowledge sources support list/read/search/reindex. Minor gaps exist—no direct tool for adding or removing knowledge sources and no remediation application for audit findings—but agents can work around them via files and reindexing.