Skip to main content
Glama
lzyruc

enterprise-agent-mcp

by lzyruc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to enterprise-agent-mcp

No user-submitted related servers found.

    Related Servers

    • hermes-mcp-gateway

      rmax-ai
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables governed remote execution of Hermes Agent tasks over MCP with client authentication, RBAC, audit logging, and human-in-the-loop approvals.
      -

    • enterprise-mcp

      dbett4
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.
      MIT

    • mcp-policy-gateway

      jcorrego
      A
      license
      A
      quality
      C
      maintenance
      Enables policy-governed MCP interactions with deterministic authorization, tenant isolation, minimized PII exposure, and human approval gates for sensitive mutations, while producing structured audit events.
      3
      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

    C2.9/5.0

    Scored across 4 tools

    Disambiguation3/5

    search_enterprise_policy and search_enterprise_docs both perform hybrid retrieval over enterprise content and differ only by content type (policies vs handbooks/runbooks), which an agent could easily confuse. The run/decide pair is clearly distinct, but the two search tools create meaningful overlap.

    Naming Consistency5/5

    All four tools use consistent snake_case verb_noun structure with a shared 'enterprise' infix (search_enterprise_policy, search_enterprise_docs, run_enterprise_agent, decide_enterprise_approval), making the pattern highly predictable.

    Tool Count3/5

    Four tools is on the thin side for a governed-agent workflow, and since the two search tools largely overlap, the effective surface is even smaller. It is not egregiously sparse but feels borderline for the stated scope.

    Completeness3/5

    The run/approve lifecycle is covered, but there is no tool to list or fetch pending approvals, so an agent receiving an approval id has no way to discover or inspect outstanding approval requests. Retrieval also lacks any get-by-id or fetch operation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources