Rhombus MCP Server

Created By
RhombusSystemsa year ago
Overview

what is Rhombus MCP Server?

Rhombus MCP Server is an implementation that integrates the Rhombus API to provide tools for chatbots, enabling developers to enhance their applications with advanced conversational capabilities.

how to use Rhombus MCP Server?

To use the Rhombus MCP Server, you need to obtain a Rhombus API key, configure your environment, and set up the server using either Docker or NPX commands as specified in the documentation.

key features of Rhombus MCP Server?

  • Integration with the Rhombus API for chatbot functionalities.
  • Support for Docker and NPX for easy deployment.
  • Configuration options for customizing server behavior.

use cases of Rhombus MCP Server?

  1. Building intelligent chatbots that can interact with users in real-time.
  2. Enhancing existing applications with conversational interfaces.
  3. Testing and deploying chatbot tools in a local development environment.

FAQ from Rhombus MCP Server?

  • How do I get a Rhombus API key?

You can sign up for a Rhombus account and create an API key in the API Key Settings section.

  • Can I use Rhombus MCP Server with Docker?

Yes! You can run the server using Docker by following the provided configuration steps.

  • What should I do if I encounter issues?

Refer to the troubleshooting guide in the documentation or contact support at api@rhombus.com.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RhombusSystems
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago