Klavis AI 🌟

Created By
alexgolemelectricoa year ago
Klavis AI (YC X25): Open Source, easy to use MCPs on Slack, Discord and Web
Overview

What is Klavis AI?

Klavis AI is an open-source project that provides easy-to-use Multi-Channel Protocols (MCPs) for Slack, Discord, and the Web, enabling seamless integration of AI into communication platforms.

How to use Klavis AI?

To use Klavis AI, clone the repository from GitHub, install the necessary dependencies, and configure it with your Slack or Discord token. You can then run the application and start sending messages through the configured channels.

Key features of Klavis AI?

  • Open Source: Fully customizable and community-driven.
  • Multi-Channel Support: Deployable on Slack, Discord, and Web.
  • User-Friendly: Accessible for both novice and experienced developers.
  • Community Driven: Engage with a growing community of contributors.

Use cases of Klavis AI?

  1. Integrating AI chatbots into Slack for customer support.
  2. Automating responses in Discord communities.
  3. Enhancing communication in team collaboration tools.

FAQ from Klavis AI?

  • Is Klavis AI free to use?

Yes! Klavis AI is completely open-source and free to use.

  • What platforms does Klavis AI support?

Klavis AI supports Slack, Discord, and Web platforms.

  • How can I contribute to Klavis AI?

You can contribute by forking the repository, making changes, and submitting a pull request.

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

4 hours ago
Gpt Scrambler

a day ago