Skip to main content
Glama
kangwa

Penny

by kangwa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Penny

No user-submitted related servers found.

    Related Servers

    • coding-os

      kouroshez
      A
      license
      B
      quality
      A
      maintenance
      MCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.
      87
      6
      Apache 2.0

    • io.github.ymxlx/polis-protocol

      ymxlx
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server provides a local-first control plane for coding agents, enabling task routing, contract management, and shared learning across multiple AI vendors via markdown files.
      5
      MIT

    • cc-agent

      Gonzih
      A
      license
      A
      quality
      D
      maintenance
      MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
      47
      187 npm
      2
      Apache 2.0

    • claude-bridge-mcp

      millanrp25-dot
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets ChatGPT or any MCP client securely delegate coding tasks to a local Claude Code instance, with git checkpointing, approval gates, and structured results. Supports code review, test running, and rollback via simple tool calls.
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool addresses a distinct step in the execution workflow: environment readiness, plan validation, submission, status retrieval, cancellation, and reporting. There is no overlap or ambiguity between tool purposes.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (validate_plan, submit_plan, get_run, cancel_run, get_report). The exception is 'doctor', which is a single verb, but its purpose is clear and the deviation is minor.

    Tool Count5/5

    Six tools provide a focused yet complete coverage of the run lifecycle without unnecessary redundancy. The count feels well-scoped for the server's stated purpose.

    Completeness5/5

    The toolset covers environment setup, plan validation, run submission, status monitoring, cancellation, and report retrieval—all essential operations for executing and managing repo runs. No critical gaps are apparent.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources