Skip to main content
Glama

Related Servers

Alternatives to Dialogflow MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients like Claude, Cursor or custom LLM apps to interpret customer messages through a Dialogflow ES agent, look up a food menu, place atomic orders and track them against a PostgreSQL backend, all via standard MCP tool calls over stdio or Streamable HTTP/SSE. Ships with Bearer-token auth plus a separate admin role, DNS-rebinding protection and server-side credential handling so database and Google credentials never leave the server.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables secure, natural language access to private Cloud SQL PostgreSQL data for catering CRM management, exposing database CRUD operations as MCP tools via Cloud Run.
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude and other MCP clients to safely query PostgreSQL data and perform limited order-status updates through scoped bearer tokens, read-only transactions, row caps, and an audit log.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Node/Express + PostgreSQL MCP server that exposes database-backed tools (list_cases, get_case, add_note) to AI clients, secured with bearer-token authentication.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing bakery recipe technical sheets with Postgres. Enables AI agents to search, create, update, approve, and compare recipe versions through secure tools.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables an MCP client to read live order data for a DailyMeals account and submit form data with confirmations, protected by bearer-token authentication and idempotent writes.
      -

    TDQS

    A3.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong one or confusing overlapping purposes. Its scope (send a message to a Dialogflow CX agent and receive a reply) is unambiguous.

    Naming Consistency4/5

    The single name, detect_intent, follows a clean snake_case verb_noun convention with a clear domain term. With only one tool there is no broader pattern to confirm consistency against, which keeps it just short of a 5.

    Tool Count3/5

    One tool is borderline thin for a server branded as a general Dialogflow MCP server, since nothing else about the platform is exposed. It is defensible if the intended scope is strictly runtime conversation, but it feels under-scoped for the name.

    Completeness2/5

    The single call covers the conversational turn, but there is no way to discover agents, manage sessions beyond passing a session_id back, or reset/end a conversation. An agent can only use this if the agent ID and session context are supplied entirely out of band, creating dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues