MCP API Bridge Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_sheet_appendD | 產生使用 Google Sheets API 新增一列資料的程式碼範例 |
| google_sheet_getC | 產生使用 Google Sheets API 讀取所有資料的程式碼範例 |
| google_sheet_updateB | 產生使用 Google Sheets API 更新指定列資料的程式碼範例 |
| google_sheet_deleteB | 產生使用 Google Sheets API 刪除指定列資料的程式碼範例 |
| google_sheet_saveB | 產生使用 Google Sheets API 覆蓋整張試算表的程式碼範例 |
| azure_ai_chatB | 產生使用 Azure AI (GPT-4o-mini) 的程式碼範例 |
| mqtt_device_createB | 建立 MQTT IoT 裝置連線 |
| mqtt_publishC | 發布 MQTT 訊息 |
| mqtt_publish_syncB | 同步發布 MQTT 訊息並等待回應 |
| mqtt_register_handlerC | 註冊 MQTT 訊息處理器 |
| mqtt_subscribeC | 訂閱 MQTT 主題 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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).
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.
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.
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.