mcp-bridge
Related Servers
Alternatives to mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables cloud AI agents to access tools from local STDIO MCP servers through a single authenticated, remotely reachable Streamable HTTP endpoint, optionally tunnelled via ngrok. It discovers and namespaces tools across multiple configured servers, with bearer-token auth, per-tool approval prompts, and call tracing.4MIT
- FlicenseAqualityCmaintenanceExposes Justworx devices to AI agents as MCP tools and resources, backed by the public Developer API. Supports local stdio and hosted remote OAuth operation for controlling device IO, rules, and viewing live state.6-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and interact with iOS apps through a local MCP gateway, converting remote Streamable HTTP MCP endpoints into stdio tools. Provides dynamic device discovery, tool schema introspection, and deterministic tool calling for app analysis.-
- AlicenseNot gradedqualityCmaintenanceEnables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.2MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control an ESP32 board's relays, GPIO pins and analog sensors over a small HTTP API on the local network, with no cloud service in the middle.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to drive a remote Linux machine over the LAN through a single TCP connection, exposing tools for shell commands, jobs, interactive PTYs, file read/write/search/transfer, process and service management, networking, packages, and power control, with optional multi-host switching. Operates without SSH or any Linux-side installation beyond one stdlib-only Python daemon, using a state-free binary protocol.MIT
TDQS
Scored across 18 tools
Most tools map cleanly to a resource+action (script, gpio, sensor, config, agent), but there are a few soft overlaps: mcp_gpio_scan versus mcp_gpio_read with 'all', and mcp_config_write versus mcp_config_load both mutate configuration. Descriptions do distinguish them (scan includes pin metadata/type/pull/reversed, load replaces whole config with a backup), so an agent can resolve the boundary, but the pairs are close enough to occasionally misselect.
Every tool follows the same mcp_<resource>_<verb> snake_case pattern: script_list/read/write/run, gpio_scan/read/write/config/watched, sensor_config/read, config_read/write/load, agent_restart/upgrade/logs. No camelCase or verb-style deviations anywhere.
18 tools is on the upper end but the server genuinely spans several sub-domains (scripts, GPIO, sensors, global config, agent lifecycle), and each tool covers a distinct operation. It's slightly heavy but no tool looks superfluous.
Coverage is strong: scripts have list/read/write/delete/run, GPIO has scan/read/write/config/watched with removal via config, sensors have config/read with delete, config has read/write/load/reset, and agent has list/restart/upgrade/logs. The notable gap is agent management — there is no tool to add or remove an agent entry, even though the server manages an agents-config.json.