Skip to main content
Glama
climashscape

Proma Manager MCP Server

by climashscape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Proma Manager MCP Server

No user-submitted related servers found.

    Related Servers

    • librechat-mcp

      Ricky-Hao
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables administration of LibreChat through MCP, providing tools to manage Skills, Agents, scheduled tasks, Prompt library, and visibility/permissions. It also offers a generic API request tool for interacting with upstream endpoints.
      MIT

    • hermes-gpt

      DeployFaith
      A
      license
      C
      quality
      D
      maintenance
      MCP sidecar for Hermes Agent exposing operator tools (cron, skills, config, workspace) with tiered read-only/operator/owner modes and dry-run by default for safe local development.
      43
      1
      MIT

    • Aegis

      nithyajangam
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables governing tenant-aware MCP tools with policy enforcement, scoped access, human approval workflows, and tamper-evident audit logging.
      -

    • enterprise-agent-mcp

      lzyruc
      F
      license
      C
      quality
      C
      maintenance
      Enables stdio-capable MCP clients to run governed enterprise operations tasks, including policy/runbook retrieval and ticket and user lookups or writes. High-risk actions are held for human approval and role-based access is enforced server-side, so clients cannot bypass governance.
      4
      1
      -

    • dsh-mcp-admin

      EnZzzzzz
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes DeepSeek Harness skill and agent preset management as an MCP server, letting remote agents read, create, update, and delete skills/presets over HTTP with audit logging. It enables a production-to-review-to-modification workflow without SSH.
      -
    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.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Each tool targets a distinct aspect: sync pushes, bootstrap fixes provenance, info queries a single skill, mcp_check handles MCP configs, group_list/group_set manage group metadata, list/delete_session handle sessions, diff compares versions, and check scans overall status. There is minor potential confusion between 'check' and 'mcp_check' but their descriptions clearly separate skills vs MCP configs.

    Naming Consistency2/5

    Tool naming is inconsistent: some are single verbs (sync, bootstrap, check, diff), some are verb_noun (list_sessions, delete_session), some are noun_verb (group_list, group_set, mcp_check), and 'info' is a noun. This mix of conventions makes the API surface less predictable.

    Tool Count5/5

    10 tools is well within the ideal 3-15 range for a management server. Each tool covers a necessary function without bloat, and the count feels proportional to the server's scope.

    Completeness5/5

    The tool set covers the full lifecycle for the server's purpose: skill sync (sync, diff, check), provenance management (bootstrap, info), group management (group_list, group_set), MCP config consistency (mcp_check), and session operations (list_sessions, delete_session). No obvious dead ends or missing critical operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources