claude-bot-bridge
Related Servers
Alternatives to claude-bot-bridge
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceLets 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.Apache 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 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 gradedqualityAmaintenanceEnables 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.Apache 2.0- AlicenseAqualityCmaintenanceOpen-source MCP server that gives AI agents access to 100+ web applications through the user's authenticated browser session. No API keys, no screenshots, no DOM scraping — talks directly to web app internal APIs via a Chrome extension. Supports Slack, Discord, GitHub, Jira, Notion, Reddit, X, and 100+ more services with ~2,000 tools. Works with Claude Code, Cursor, Windsurf, and any MCP client.42994MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents such as Codex and Claude Code to exchange durable, locally stored messages through shared MCP tools for listing enrolled recipients, sending and replying to messages, reading pending inbox items, acknowledging receipt, and checking message status. Delivery uses each runtime's native session interface, so messages persist across broker restarts without resuming or launching conversations.AGPL 3.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.