Alkemi Mcp

Created By
alkemi-ai7 months ago
Integrate your Alkemi Data, connected to Snowflake, Google BigQuery, DataBricks and other sources, with your MCP Client.
Overview

what is Alkemi MCP?

Alkemi MCP is a server that integrates your Alkemi Data with various data sources like Snowflake, Google BigQuery, and DataBricks, allowing seamless data querying and sharing.

how to use Alkemi MCP?

To use Alkemi MCP, you need to configure it in your Claude Desktop by adding the server configuration and setting the necessary environment variables. You can also run it using npx or by building it from the source.

key features of Alkemi MCP?

  • Integration with multiple data sources (Snowflake, BigQuery, DataBricks)
  • Easy configuration for querying databases
  • Ability to share data querying capabilities among team members

use cases of Alkemi MCP?

  1. Querying large datasets from Snowflake and BigQuery.
  2. Collaborating on data analysis projects with team members.
  3. Automating data retrieval processes for applications.

FAQ from Alkemi MCP?

  • What data sources does Alkemi MCP support?

Alkemi MCP supports Snowflake, Google BigQuery, DataBricks, and more.

  • Is there a cost to use Alkemi MCP?

You can get a free API key to use Alkemi MCP.

  • How do I configure multiple MCP Servers?

You can specify the MCP_NAME environment variable to differentiate between multiple servers.

Server Config

{
  "mcpServers": {
    "alkemi": {
      "command": "npx",
      "args": [
        "@alkemiai/alkemi-mcp"
      ],
      "env": {
        "BEARER_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
alkemi-ai
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)

a day ago