Skip to main content
Glama
Alan-VZ

universal-agent-control-plane

by Alan-VZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to universal-agent-control-plane

No user-submitted related servers found.

    Related Servers

    • skillcp

      lum1n
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing a canonical library of agent skills and MCP servers, syncing them across multiple development harnesses, and adding, importing, or configuring them through MCP tools.
      17 npm
      MIT

    • skillforge

      aniruddhaadak80
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, retrieve, score, compose, and verify reusable agent skills from the SkillForge registry via MCP.
      4 npm
      MIT
    • skillmds by skillmds

      skillmdsofficial

      skillmds
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable agents to search, inspect, lint, and safely install Agent Skills from the skillmd registry mid-conversation.
      2 npm
      34
      MIT

    • SkillRelay

      cfollette18
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to capture observable workflows, distill successful techniques and failure lessons into evidence-linked versioned skills, evaluate and approve them through review gates, and distribute approved instructions and portable resources through MCP for reuse across tasks.
      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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a different concern: orchestration, state read/write, registry lookup/validation/resolution, and skill execution. Even the two registry tools are clearly separated by search versus resolve/validate semantics.

    Naming Consistency4/5

    Most tools follow a domain-prefix_verb pattern (state_get, state_put, registry_search, skill_run, registry_validate, registry_resolve), but orchestrate breaks the pattern by using a bare verb with no prefix. The inconsistency is minor and the names remain readable.

    Tool Count5/5

    Seven tools is a well-scoped size for a control plane server. Each tool covers a distinct function without redundancy, and the count is neither too thin nor too heavy.

    Completeness4/5

    The core surface is fairly complete: state read/write, registry search/validate/resolve, skill execution, and result orchestration are all present. Minor gaps exist, such as no explicit state deletion or registry modification, but agents can work around them with the available tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources