mcp-dotpals
Related Servers
Alternatives to mcp-dotpals
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides a workspace-safe, read-only bridge between browser-based AI planning/review and local coding agents, enabling structured plan, execution summary, and review handoffs without granting shell, file write, or Git push access.11MIT
- AlicenseAqualityAmaintenanceLocal code review for people and their coding agents: an agent opens a review of its changes and hands over a link, the person comments on lines, and the agent reads the threads, replies and resolves what it fixed. Reads the git worktree directly, uncommitted work included; nothing leaves the machine.21776 npm18GPL 3.0
- AlicenseAqualityCmaintenanceEnables read-only inspection of local coding-agent sessions across Claude Code, OpenCode, Cursor, and Codex, including running status, topics, todos, and transcripts, without writing or sending messages.4169 npm1MIT
- AlicenseAqualityAmaintenanceEvidence-backed, read-only codebase diagnostics for coding agents: secrets, dependency, RLS, and source-impact audits with a verify loop and PR review verdicts. Never writes files or uses the network by default.426 npmMIT
- AlicenseNot gradedqualityAmaintenanceObservation-only CI/CD validation for AI coding agents. Analyze a change, compare safe test commands, and report evidence without altering required CI.1,694 npmAGPL 3.0
- AlicenseAqualityAmaintenanceRecords and rewinds AI coding agents (Claude Code, Codex, Cursor, Gemini CLI and others) locally. Its tools take a checkpoint, show the session timeline, preview and apply a rewind with a confirm code, list the tests the agent ran and whether the code changed since, write a handoff, verify the hash-chained log, and check a tool call against your guardrails.7Apache 2.0
TDQS
Scored across 8 tools
Most tools are distinguishable by domain facet (test status, activity, risk, handoff), but several overlap heavily: recap vs today both summarize what agents did, and ready_to_merge vs check_my_work both run near-identical reviewer checks (differing mainly in whose session is the default). test_status also overlaps with the test facets embedded in ready_to_merge and check_my_work, so an agent can plausibly misselect among these.
All names use snake_case, which is consistent, but the convention itself is mixed: some are question-style phrases (agents_now, ready_to_merge, check_my_work), some are bare nouns (recap, today), and others are noun_phrases (test_status, risky_steps, handoff_note). Readable but no single predictable verb_noun pattern.
Eight tools is well within a reasonable range for an agent-observability server and each maps to a plausible use case. Slightly heavy given that at least two pairs (recap/today, ready_to_merge/check_my_work) are near-duplicates, but overall the count is sensible.
The surface covers the domain well: per-session and per-project activity, test status, merge readiness, risk detection, handoff, and self-review. Coverage of the coding-agent lifecycle is broad; minor gaps (e.g. no explicit session-listing or time-range customization beyond defaults) are workable.