google_sheet_appendLABSCO SUMMARY
Two of the three integrations hand you code, not results.
Reading the tool names, you would expect google_sheet_get to return rows; it returns a code sample that would return rows. Only the MQTT half performs the action. That is a legitimate design for a teaching bridge — the repository is clearly aimed at IoT coursework, with a shared broker and a fixed set of endpoints — but it changes what you should connect it for.
What it is
A Node server that bundles three unrelated integrations behind one connection. The distinction that matters: the MQTT tools genuinely connect devices, publish and subscribe, while the Google Sheets and Azure AI tools return code examples showing how to call those APIs rather than calling them. The changelog records that as a deliberate change in 1.0.2.
What you get
- MQTT, which acts:
mqtt_device_createregisters a device,mqtt_publishandmqtt_publish_syncsend messages with a QoS level,mqtt_subscribelistens on a topic,mqtt_register_handlerattaches handler code to an action - Google Sheets, which generates code:
google_sheet_append,google_sheet_get,google_sheet_update,google_sheet_delete,google_sheet_saveeach return a working example for that operation - Azure AI, which generates code:
azure_ai_chatreturns a sample for calling Azure AI, in either synchronous or streaming form - Synchronous publish with a
timeout, so a request/response exchange over MQTT is one call - The broker and its credentials are baked into the server rather than configured
Requirements
Node.js 18.0.0 or higher. Install globally straight from the repository with npm install -g https://github.com/marty5499/mcp-api-bridge.git, then set the command to mcp-api-bridge in your client config — no environment variables. Package mcp-api-bridge, version 1.0.2. The MQTT broker, the Sheets base URL and the Azure WebSocket endpoint are fixed in the server and point at the author's hosted services.
Setup effort
One command — npm install -g https://github.com/marty5499/mcp-api-bridge.git
USE CASES
01
Wiring two devices together over MQTT
Create both devices, register a handler on the receiver, and publish from the sender — all from the conversation.
02
Getting a reply back from a device
Use the synchronous publish with a timeout instead of publishing and then polling for a response.
03
Watching a topic pattern
Subscribe with a wildcard and a QoS level to see what a fleet is emitting.
04
Learning how to call the Sheets or Azure endpoints
Ask for the operation you want and read back a code sample you can adapt, rather than a result.
11 tools
Listed in project docs. Your client may show a different list.
google_sheet_getgoogle_sheet_updategoogle_sheet_deletegoogle_sheet_saveazure_ai_chatmqtt_device_createmqtt_publishmqtt_publish_syncmqtt_register_handlermqtt_subscribeBEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- mcp-api-bridge on PATH
- Node.js 18.0.0 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g https://github.com/marty5499/mcp-api-bridge.gitMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"api-bridge": {
"command": "mcp-api-bridge",
"env": {}
}
}
}
