Skip to main content
Glama
Sign In
Universal MCP Bridge & Proxy

Universal MCP Bridge & Proxy

by francaroscillidev-gif
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Universal MCP Bridge & Proxy

No user-submitted related servers found.

    Related Servers

    • Omni-MCP

      FuadTesfaye
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to turn any API, CLI, database, website, SDK, or codebase into a production-ready MCP server with secure, dynamically discoverable capabilities.
      MIT

    • relay-mcp

      yujoonko1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to expose any dev tool as a safe, audited MCP server with permission tiers, audit logging, and automatic argument validation.
      MIT

    • mcp-toolkit

      aseydaaksakal
      A
      license
      A
      quality
      C
      maintenance
      Exposes internal databases, HTTP APIs, and files to LLM agents over MCP, with auto-generated schemas, access controls, rate limiting, redaction, and audit logging.
      3
      MIT

    • yamcp

      adamgalmor
      A
      license
      Not graded
      quality
      D
      maintenance
      Convert any OpenAPI spec into a secure MCP server with scoped auth, per-tool allow/deny policies, rate limiting, and a redacted audit trail.
      10 npm
      MIT

    • Argent

      moawhi
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns existing backend APIs (OpenAPI) and SQL databases (PostgreSQL, MariaDB, ClickHouse) into hosted MCP servers for AI clients, with built-in dashboards, forms, and credential encryption.
      5,309 npm
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    C2.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a clearly different operation: pet lookup by status vs. by ID, text analysis, system health, DB schema inspection, DB query, and curl execution. The only mild overlap is findPetsByStatus vs getPetById, but list-vs-get semantics distinguish them. The bigger problem is thematic incoherence, not tool-to-tool confusion.

    Naming Consistency2/5

    The set mixes camelCase (findPetsByStatus, getPetById) with snake_case (run_text_analyzer, db_sample_schema, exec_curl) and uses inconsistent verb styles (find/get/run/exec). Names are individually readable but the conventions change from tool to tool.

    Tool Count4/5

    Seven tools is a reasonable count in isolation and none feels redundant. However, they are an unrelated grab-bag rather than a scoped surface, so the count is fine but the composition is arbitrary.

    Completeness2/5

    There is no coherent domain to cover: pet tools lack create/update/delete, the DB exposes only read-only sample/query with no schema mutation, and text/sys/curl are one-off utilities. As a 'universal bridge' the surface is a random sampling with major lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources