Skip to main content
Glama
marcomq

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
      A
      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
      163
      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).
      12
      AGPL 3.0

    • MCP GraphQL Server Multi

      Denisijcu
      A
      license
      A
      quality
      B
      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
      5 npm
      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

    • AnythingMCP

      Jaiaaryan
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns any REST/OpenAPI, SOAP, GraphQL, OData, SQL, MongoDB or existing MCP system into MCP tools for Claude, ChatGPT and Copilot without writing an MCP server, shipping 474 ready-made connectors with runtime tool registration, field filtering and role-based access control.
      AGPL 3.0
    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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (start/stop/wait routes, publish, describe, generate_cli_command). However list_routes, route_status, and bridge_status all overlap on reporting route health/throughput, differing mainly in scope (this server vs. all processes, one vs. all routes), which could cause misselection.

    Naming Consistency3/5

    Conventions are mixed: verb_noun appears in list_routes, start_route, stop_route, wait_route, generate_cli_command, while noun_verb forms appear in route_status, route_messages, server_info, bridge_status, plus bare verbs like publish and describe. It's still readable but not a single predictable pattern.

    Tool Count5/5

    11 tools is well-scoped for a message-bridge server: route lifecycle, message inspection, publishing, and introspection each earn their place without bloat or redundancy.

    Completeness4/5

    Route lifecycle is well covered (start, stop, wait, status, message capture, list, CLI generation) plus publish, describe, and identity info. Minor gaps exist, e.g. no explicit route teardown/purge beyond stop_route, but core workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources