Skip to main content
Glama
Rikinshah787

mcp-dotpals

by Rikinshah787
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-dotpals

No user-submitted related servers found.

    Related Servers

    • suvadu

      AppachiTech
      A
      license
      A
      quality
      A
      maintenance
      Read-only access to your local shell history and AI coding agent sessions: search past commands, recent failures and what fixed them, assess a command's risk, and see what each agent session changed in git.
      4
      22
      123
      MIT

    • Hua PlanRelay

      lmwacn
      A
      license
      A
      quality
      A
      maintenance
      Provides 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.
      11
      MIT

    • GitWarren

      klarluft
      A
      license
      A
      quality
      A
      maintenance
      Local 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.
      17
      43 npm
      18
      GPL 3.0

    • harness-homies

      nikp29
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      4 npm
      1
      MIT

    • codebase-doctor

      subhajitlucky
      A
      license
      A
      quality
      A
      maintenance
      Evidence-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.
      7
      423 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation3/5

    Several tools overlap heavily on reporting agent activity: recap, today, brief, and report_card all summarize what agents did, differing mainly by period or scope. ready_to_merge, check_my_work, and test_status also overlap on test/readiness review. The descriptions clarify defaults and distinctions, but an agent could reasonably misselect for broad questions like 'what did my agents do?'

    Naming Consistency3/5

    All names are lowercase snake_case and readable, but the set mixes single nouns (recap, brief, today), noun phrases (report_card, test_status, handoff_note, risky_steps), and verb phrases (ready_to_merge, check_my_work). There is no consistent verb_noun pattern to predict new or related tool names.

    Tool Count4/5

    10 tools is a reasonable size for an agent-observability server, and most cover distinct artifacts like current activity, risks, tests, handoff, and readiness. However, the four summary/report tools create notable redundancy, slightly inflating the set beyond what the domain strictly needs.

    Completeness4/5

    The surface covers the core observability lifecycle well: live agent status, multiple recaps, readiness checks, test status, risky actions, and handoff notes. A minor gap is the lack of a tool to list past sessions or resolve a session ID older than agents_now's 2-hour window, which limits practical use of session-scoped tools.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources