A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
4 โ ยท alkemi-ai/alkemi-mcp ยท read from the repository page ยท (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list ยท type: MCP server
Harvest history
first seen 2026-10-09 ยท last seen 2026-10-16 ยท seen 32ร ยท listed by 7 sources
Score
score 703 ยท 4 โ ยท 7 sources ยท mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository alkemi-ai/alkemi-mcp๏ผfirst catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
Integrate your Alkemi Data, connected to Snowflake, Google BigQuery, DataBricks and other sources, with your MCP Client. This is a STDIO wrapper for the Streamable HTTP MCP Endpoint: Get your free API key at datalab.alkemi.ai Alkemi.ai Querying databases requires knowledge about the schema of the tables and may require examples of the kinds of queries that can answer specific questions. Otherwise, you may be getting the wrong answers. Maintaining all that information in every agent or MCP Client that queries your database is a challenge and doesn't scale to teams looking to share data. The Alkemi MCP Server uses Alkemi to store the database metadata, generate proper queries and actually query the database so you can share your MCP Server with teammates and everyone will have the same ability to query with quality. Installation To add OpenAI to Claude Desktop, add the server config: On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json Env Vars - MCP_NAME: The name of the MCP Server. This is optional. If you configure multiple, this is required so they do not have the same names in your MCP Client.. - BEARER_TOKEN: The Bearer token for the Streamable HTTP MCP Server. This is required for the STDIO MCP Integration. - PRODUCT_ID: The ID of the Product if you want to narrow scope to just a single product. This is optional. Configuration You can use it via npx in your Claude Desktop configuration like this: Or, if you clone the repo, you can build and use in your Claude Desktop configuration like this: If you want to specify a specific product that the MCP Server should use, you can specify the PRODUCT_ID environment variable. And with setting the MCP_NAME, you can configure multiple. Development Install dependencies: Build the server: For development with auto-rebuild: Debugging Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script: