How to Use the Chatbot Widget

Created By
schmitecha year ago
Pluggable web chat widget to interact with ORBIT MCP server.
Overview

What is the Chatbot Widget?

The Chatbot Widget is a pluggable web chat interface designed to interact seamlessly with the ORBIT MCP server, allowing users to integrate a chatbot into their websites easily.

How to use the Chatbot Widget?

To use the Chatbot Widget, include the widget files in your HTML, initialize it with your API details, and customize it according to your needs.

Key features of the Chatbot Widget?

  • Easy integration with a simple script tag.
  • Customizable themes and welcome messages.
  • Support for suggested questions to enhance user interaction.
  • Session management for personalized conversations.

Use cases of the Chatbot Widget?

  1. Providing customer support through automated responses.
  2. Engaging users with interactive chat experiences on websites.
  3. Collecting user feedback and inquiries in real-time.

FAQ from the Chatbot Widget?

  • Can I customize the appearance of the widget?

    Yes! The widget supports extensive theme customization options.

  • Is the widget easy to integrate?

    Absolutely! You can integrate it with just a few lines of code.

  • What do I need to get started?

    You need an API endpoint and an API key to initialize the widget.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
schmitech
Star
0
Language
TypeScript
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)

a day ago