Skip to main content
Glama
edlovesjava

mcp-api-bridge

by edlovesjava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-api-bridge

No user-submitted related servers found.

    Related Servers

    • Amplify Data API MCP Server

      dbsmith7491
      F
      license
      Not graded
      quality
      D
      maintenance
      This MCP server enables users to interact with AWS Amplify Gen2 application data through natural language, allowing AI assistants like Claude to perform operations on Amplify data models using conversational language instead of complex code.
      4
      -

    • MCP4Amazon

      Jeremy-33456
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables large language models to directly access and analyze Amazon product information, including product details, variants, and reviews.
      -

    • Maverick MCP Server

      VigneshR1812
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that enables Amazon Q CLI users to create, query, and manage Maverick sites through natural language commands.
      -

    • NLSQL MCP Server

      tushar-badhwar
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that exposes natural language to SQL functionality, allowing any MCP-compatible client to convert plain English questions into SQL queries for database interaction using AI.
      3
      MIT

    • Discovery Engine MCP Server

      ag2-mcp-servers
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables natural language interaction with Google's Discovery Engine API, allowing users to search, recommend, and manage data through conversational interfaces.
      -
    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.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: list_catalogs exposes metadata, catalog_search executes structured searches, catalog_get_item fetches a single item, understand_query only plans from natural language, and smart_search both plans and searches. The descriptions explicitly contrast the NL tools and the structured-search tool, eliminating ambiguity.

    Naming Consistency3/5

    Tool names mix conventions: list_catalogs and understand_query are verb-first, while catalog_search and catalog_get_item are noun-first, and smart_search is an adjective-noun compound. The inconsistency is noticeable but not chaotic, with a 'catalog_' prefix for search/get actions providing some order.

    Tool Count5/5

    Five tools is a well-scoped size for a catalog search bridge: metadata discovery, structured search, item retrieval, NL interpretation, and NL search. Each tool earns its place with no redundant coverage, making the set feel appropriately lean.

    Completeness5/5

    The surface covers the full query lifecycle: discover catalogs, run structured searches, retrieve individual items, and process natural language either as a plan or as a plan-plus-search. As a read-only bridge, missing create/update/delete operations are not gaps; no dead ends remain for the stated purpose.

    Resources