claude-bot-bridge
Related Servers
Alternatives to claude-bot-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to brief self-hosted GrokBot bots through their webhook routines and then collect their replies in the same thread, with tools for waiting on replies, checking the inbox, and reading conversations. It includes a self-hosted dashboard for registering bots, managing encrypted webhook keys and tokens, and connecting Claude apps over OAuth or API tokens.1MIT

Hwip MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceLets an agent ask the user a question that lands on their phone and returns the reply inside the same tool call, plus send one-way notifications, clipboard text, files, and channel broadcasts. Works with Claude Code, Cursor, Windsurf, Gemini CLI, and any MCP client.237 npmApache 2.0- FlicenseAqualityDmaintenanceUniversal HTTP client tool for LLM agents. Enables Claude and other MCP-compatible agents to perform GET, POST, PUT, DELETE, and other HTTP requests to any URL, including localhost and internal network addresses.2-
- AlicenseNot gradedqualityBmaintenanceA local hub that lets you chat with Claude, Gemini, OpenAI or Ollama while exposing Python-written connector tools (filesystem, web, system, sqlite, plugins) to the dashboard, Claude Desktop and any MCP client over HTTP or stdio. Every outbound webhook, Discord, Slack, email or push action waits for Approve/Deny, prompt templates are published as MCP prompts, and all JSON-RPC traffic is visible in a live inspector.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to send prompts to signed-in ChatGPT and Gemini browser tabs and retrieve streamed replies as MCP tools without API keys. It also supports listing tabs, reading the latest response, scraping conversations, and checking connection health.MIT

capofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP hosts such as Claude, Cursor, and VS Code to discover a company's front door, ask it questions, and check replies through three tools.1Apache 2.0
TDQS
Scored across 7 tools
Most tools have clearly distinct roles, but send_message/broadcast_message and get_replies/wait_for_reply overlap in adjacent areas. Descriptions explicitly differentiate them, so an agent can usually select correctly, though the reply-reading pair still requires care.
All tool names follow a consistent snake_case verb_noun pattern: list_bots, send_message, get_replies, broadcast_message, wait_for_reply, relay_conversation, stop_relay. No mixed conventions or vague verbs.
Seven tools are well-scoped for a bot messaging bridge: discovery, single-send, broadcast, reply reading, waiting, multi-turn relay, and stopping a relay. Each tool has a clear operational purpose.
The surface covers the core lifecycle: discover bots, send, broadcast, read replies, wait for replies, run multi-turn relays, and stop relays. Minor gaps exist around thread/history management and explicit relay status inspection, but these are workable around.