Skip to main content
Glama
Sign In
mq-bridge

mq-bridge

by marcomq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Related Servers

Alternatives to mq-bridge

No user-submitted related servers found.

    Related Servers

    • Faucet

      faucetdb
      A
      license
      A
      quality
      B
      maintenance
      Turn PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite or Snowflake into MCP tools and a REST API, with API keys and per-table role-based access.
      8
      171
      MIT

    • Datris MCP Server

      datris
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server with 32 tools for ETL ingestion, AI-generated data quality rules, AI transformations, vector search, and natural-language SQL. Works across Postgres, MongoDB, Kafka, S3/MinIO, HashiCorp Vault, and five vector stores (Qdrant, Weaviate, Milvus, Chroma, pgvector).
      13
      Apache 2.0

    • MCP GraphQL Server Multi

      Denisijcu
      A
      license
      A
      quality
      C
      maintenance
      Enables querying and mutating data across multiple sources (CSV, Google Sheets, SQLite, PostgreSQL, MySQL, MongoDB, Oracle) through a dynamic GraphQL API, with flexible filtering, batching, persisted queries, and dynamic source switching.
      8
      4 npm
      MIT

    • jsonloupe

      priyanshuN
      A
      license
      A
      quality
      B
      maintenance
      Lets an agent query JSON files too large for its context: JSONPath with aggregation pipes, schema, field profiles, samples, identity-keyed diff, CSV and spreadsheet export, and checks that gate a file. Int64 IDs and decimals keep their exact digits, and zstd, Base64-Zstd and PostgreSQL bytea payloads open directly.
      4
      12
      238 npm
      2
      MIT

    • Express REST API and MCP

      bettychavez
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients such as Claude, ChatGPT, and Cursor to discover and act on generated CRUD services over HTTP through tools like create, update, list, and delete, plus read-only resources for listing and fetching records by ID, with no extra glue code.
      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

    A4.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools are clearly separated and the descriptions actively cross-reference each other (bridge_status vs list_routes vs route_status, wait_route vs polling, generate_cli_command vs start_route). The one real overlap is that route_status called without a `name` returns the same all-routes summary as list_routes, and the cluster of status/health tools (server_info, bridge_status, list_routes, route_status, wait_route) takes careful reading to sort out.

    Naming Consistency4/5

    A predictable scheme runs through almost everything: verb_noun for actions (start_route, stop_route, list_routes, wait_route, generate_cli_command) and noun_status/noun_messages for read-only reporters. The only deviations are the bare verbs `describe` and `publish`, plus `server_info`, which don't fit either pattern cleanly but are still readable.

    Tool Count5/5

    Eleven tools is squarely in the well-scoped range, and each maps to a distinct step in the job lifecycle: discover schemas, generate a command, start/wait/stop a route, read status and captured messages, plus machine-level and build identity. Nothing looks like filler.

    Completeness4/5

    The route lifecycle is fully covered — schema discovery via describe, optional command generation, start, wait, status, message capture, and stop — plus ad-hoc publish and cross-process visibility via bridge_status. Minor gaps remain: there is no ad-hoc single-message consume/poll (you must stand up a route with capture_last), no pause/resume, and stopping routes belonging to other processes is explicitly impossible by design.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources