Kyomi

Created By
Jason Adams3 months ago
AI data intelligence platform that brings your data warehouse, dashboards, monitoring, and accumulated business knowledge into any MCP client. Connects to BigQuery, Snowflake, PostgreSQL, MySQL, ClickHouse, Redshift, Databricks, SQL Server, and Azure Synapse.
Overview

Kyomi MCP Server

Kyomi brings your data warehouse, dashboards, monitoring, and accumulated business knowledge into any MCP client.

Get Started

  1. Sign up for a free account at app.kyomi.ai
  2. Connect a datasource (or use the demo database included with every account)
  3. Add the MCP server to your client:

What You Get

  • Query any datasource — BigQuery, Snowflake, PostgreSQL, MySQL, ClickHouse, Redshift, Databricks, SQL Server, Azure Synapse
  • Semantic catalog search — "find customer revenue tables" across all connected datasources
  • Dashboards — create, search, and manage dashboards from your IDE
  • Watches — set up automated monitoring and alerts in plain English
  • Knowledge base — save and retrieve metric definitions, business rules, and table knowledge
  • Website analytics — provision tracking, query traffic data, set up alerts

How It Works

Kyomi learns your business context over time — metric definitions, table relationships, business rules. That accumulated intelligence follows you into Claude Code, Cursor, or any MCP client. Same knowledge, same context, wherever you work.

Free tier includes MCP access, a demo database, AI budget, and up to 5 dashboards.

Server Config

{
  "mcpServers": {
    "kyomi": {
      "type": "http",
      "url": "https://app.kyomi.ai/mcp"
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Jason Adams
Star
-
Language
-
License
-
Category

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