Skip to main content
Glama
BenjaminJ

enterprise-mcp-gateway

Related Servers

Alternatives to enterprise-mcp-gateway

  • A
    license
    A
    quality
    A
    maintenance
    Self-hosted MCP gateway that registers upstream MCP servers and fronts them behind one governed Streamable HTTP endpoint: per-tool access control by caller API key, guardrails over tool arguments and results, rate limits, and usage logs. The same Rust gateway also proxies LLM and A2A agent traffic.
    4
    1
    157
    Apache 2.0

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A secure MCP gateway for enterprise AI tool execution, enabling governed invocation of business tools with authentication, RBAC, audit logging, PII redaction, and async processing.
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Universal MCP router and gateway that bridges LLM agents to OpenAPI, GraphQL, and AWS Lambda services with ISO/IEC 42001 AI governance, RBAC, PII redaction, semantic tool routing, and a web dashboard.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    MCP gateway adding per-tool RBAC, tenant isolation, audit export, and PII redaction to any server.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    ToolMesh is an Apache-2.0, self-hosted MCP gateway written in Go that sits between AI agents and backend systems. It enforces a fail-closed pipeline on every tool call, including per-tool and per-user authorization, server-side credential injection, structured audit logging, and output policies. APIs are declared in YAML with DADL, turning REST endpoints into MCP tools without writing a custom MCP
    6
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    A universal MCP server for registering internal, external, and OpenAPI-based APIs as MCP tools. It exposes them to MCP clients via Streamable HTTP and provides admin portal, RBAC/session auth, credential injection, and audit logging.
    Academic Free v1.1

TDQS

A4.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct resource and action: customer search, customer detail, billing history, ticket listing, and ticket creation. The usage guidelines explicitly reinforce these boundaries, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent camelCase verb_noun pattern: list/get/create plus the target resource. There is no mixing of conventions or vague, ambiguous verbs.

Tool Count5/5

Five tools is a well-scoped set for a focused customer and support gateway. Each tool has a clear purpose and none are redundant or extraneous.

Completeness3/5

Read coverage for customers, billing, and tickets is solid, and ticket creation exists. However, there are notable lifecycle gaps: no way to update or resolve support tickets, and no customer create/update/delete operations, which creates dead ends in common workflows.

Maintenance

ActivityMaintained
ResponsivenessNo issues