Skip to main content
Glama
marty5499

MCP API Bridge Server

by marty5499
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP API Bridge Server

No user-submitted related servers found.

    Related Servers

    • mcp-google-sheets

      xing5
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that integrates with Google Drive and Google Sheets, enabling users to create, read, update, and manage spreadsheets through natural language commands.
      23,612 PyPI
      998
      MIT

    • MCP Google Suite

      adexltd
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that provides seamless integration with Google Workspace, allowing operations with Google Drive, Docs, and Sheets through secure OAuth2 authentication.
      8
      107 PyPI
      3
      MIT

    • Microsoft 365 MCP Server

      Softeria
      A
      license
      C
      quality
      A
      maintenance
      A Model Context Protocol server that enables interaction with Microsoft 365 services (Excel, Calendar, Mail, OneDrive, Teams, etc.) through the Graph API, allowing AI assistants to manage Microsoft 365 resources via natural language.
      188
      20,519 npm
      968
      MIT

    • Excel MCP Server

      SuperPyonchiX
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to freely operate Excel spreadsheets, providing tools for workbook creation, cell manipulation, formatting, formula handling, and data export.
      11
      95 npm
      ISC
    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

    B3.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each group of tools (Azure AI, Google Sheets, MQTT) targets a distinct domain with no overlap. Within each domain, all operations are clearly differentiated by their descriptions (e.g., mqtt_publish vs mqtt_publish_sync, google_sheet_get vs google_sheet_append).

    Naming Consistency5/5

    All tools follow a consistent pattern of service prefix (azure_ai_, google_sheet_, mqtt_) followed by verb or verb_noun (e.g., chat, append, create_device). Naming is entirely snake_case and predictable.

    Tool Count5/5

    With 11 tools across three domains, the count is well-scoped. Each domain has a reasonable number of tools (1 for Azure AI, 5 for Google Sheets, 5 for MQTT) that collectively cover the server's purpose as an API bridge without being excessive.

    Completeness5/5

    For Google Sheets, CRUD operations (get, append, update, delete, save) are covered. For MQTT, essential operations (device create, publish, subscribe, handler registration) are present. Azure AI chat is a single tool but fulfills its stated purpose of generating code examples. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources