Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.us-east4.gcp.keboola.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"keboola": {
"command": "uvx",
"args": [
"keboola-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add --transport http keboola https://mcp.us-east4.gcp.keboola.com/mcpclaude mcp add keboola -- uvx keboola-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"keboola": {
"url": "https://mcp.us-east4.gcp.keboola.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"keboola": {
"command": "uvx",
"args": [
"keboola-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"keboola": {
"type": "http",
"url": "https://mcp.us-east4.gcp.keboola.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"keboola": {
"type": "stdio",
"command": "uvx",
"args": [
"keboola-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.us-east4.gcp.keboola.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain keboola.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 396 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (1.116.1) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect your AI agents, MCP clients (Cursor, Claude, Windsurf, VS Code ...) and other AI assistants to Keboola. Expose data, transformations, SQL queries, and job triggers—no glue code required. Deliver the right data to agents when and where they need it.
Keboola MCP Server is an open-source bridge between your Keboola project and modern AI tools. It turns Keboola features—like storage access, SQL transformations, and job triggers—into callable tools for Claude, Cursor, CrewAI, LangChain, Amazon Q, and more.
With the AI Agent and MCP Server, you can:
The easiest way to use Keboola MCP Server is through our Remote MCP Server. This hosted solution eliminates the need for local setup, configuration, or installation.
Our remote server is hosted on every multi-tenant Keboola stack and supports OAuth authentication. You can connect to it from any AI assistant that supports remote Streamable HTTP connection and OAuth authentication.
MCP Server tabhttps://mcp. .keboola.com/mcpclaude mcp add --transport http keboola (see below for details)Claude Code is a command-line interface tool that allows you to interact with Claude using your terminal. You can install the Keboola MCP Server integration using a simple command.
Installation:
Run the following command in your terminal, replacing with your Keboola region:
claude mcp add --transport http keboola https://mcp.<YOUR_REGION>.keboola.com/mcp
Region-specific commands:
| Region | Installation Command |
|---|---|
| US Virginia AWS | claude mcp add --transport http keboola https://mcp.keboola.com/mcp |
| US Virginia GCP | claude mcp add --transport http keboola https://mcp.us-east4.gcp.keboola.com/mcp |
| EU Frankfurt AWS | claude mcp add --transport http keboola https://mcp.eu-central-1.keboola.com/mcp |
| EU Ireland Azure | claude mcp add --transport http keboola https://mcp.north-europe.azure.keboola.com/mcp |
| EU Frankfurt GCP | claude mcp add --transport http keboola https://mcp.europe-west3.gcp.keboola.com/mcp |
Usage:
Once installed, you can use the Keboola MCP Server in Claude Code by typing /mcp in your conversation and selecting the Keboola tools you want to use.
Authentication:
When you first use the Keboola MCP Server in Claude Code, a browser window will open prompting you to:
After authentication, you can start using Keboola tools directly from Claude Code. Project selection happens afterward, in the conversation — just ask Claude which Keboola project(s) to use.
For detailed setup instructions and region-specific URLs, see our Remote Server Setup documentation.
You can work safely in Keboola development branches without affecting your production data. The remotely hosted MCP Servers respect the KBC_BRANCH_ID parameter and will scope all operations to the specified branch. You can find the development branch ID in the URL when navigating to the development branch in the UI, for example: https://connection.us-east4.gcp.keboola.com/admin/projects/PROJECT_ID/branch/BRANCH_ID/dashboard. The branch ID must be included in each request using the header X-Branch-Id: , otherwise the MCP Server uses production branch as default. This should be managed by the AI client or the environment handling the server connection.
When using HTTP-based transports (Streamable HTTP), you can control which tools are available to clients using HTTP headers. This is useful for restricting AI agent capabilities or enforcing compliance policies.
| Header | Description | Example |
|---|---|---|
X-Allowed-Tools | Comma-separated list of allowed tools | get_configs,get_buckets,query_data |
X-Disallowed-Tools | Comma-separated list of tools to exclude | create_config,run_job |
X-Read-Only-Mode | Restrict to read-only tools only | true, 1, or yes |
Filters apply in order: allowed → read-only intersection → disallowed exclusion. Empty headers = no restriction.
Read-only tools are those annotated with readOnlyHint=True. These tools only retrieve information without making any changes to your Keboola project. For the current list of read-only tools, see the TOOLS.md file which is an auto-generated snapshot of the actual tool set.
X-Read-Only-Mode: true
| Header | Description | Example |
|---|---|---|
X-Deferred-Tools | Comma-separated list of tools to list with _meta["anthropic/alwaysLoad"] = false | run_sync_action,get_flow_schema |
Claude Code / Claude Agent SDK clients that register the server with alwaysLoad: true keep these tools deferred behind tool search instead of loading their definitions up front. The header only changes the tools/list metadata — it does not hide or authorize tools. Empty header or unknown tool names = no change.
For detailed documentation, see developers.keboola.com/integrate/mcp/#tool-authorization-and-access-control.
Row- and column-level policies are Keboola Metastore objects (rls-policy, cls-policy), written through the Metastore API (the kbagent rls / kbagent cls commands are not in any kbagent release yet). This server neither reads nor applies them. In a project that has the row-level-security feature it creates its workspace (the mcp-workspace- configuration of the keboola.mcp-server-tool component) with the Connection login type governed. A governed workspace has no credentials: only the Query Service can read it, and the Query Service filters every query_data result by the policies of the project. There is no rewriting in this server and no fallback: what the Query Service refuses, query_data returns as an error.
governed for the project's backend: a stack that does not refuses the create, and then every tool that needs the workspace fails (there is no fallback to an ordinary workspace). Enforcement on BigQuery is not verified end to end on a production stack. An older ordinary MCP workspace is not deleted: it is skipped as soon as the feature is on. With the feature on, a workspace_schema or X-Workspace-Id pin is accepted only for a governed workspace (an ordinary one would read around the policies), so a pin to the old workspace, or to a data app's own ordinary workspace, is refused; delete the old one.rls-policy nor a cls-policy covers is refused for an administrator (the agent sees Row-level security does not allow this query) and reads as no rows for an ordinary reader such as a data app end user (a "*" rule opens a table to every identified reader). A cls-policy alone opens its table: all rows, only its columns, for the readers it names; any other reader is refused. A statement that reads no table (SELECT 1) runs.IDENTIFIER(), TABLE() outside FROM, an AI function (AI_*, BigQuery AI.*), TO_FILE, READ_CSV / READ_PARQUET, SECRET, a session-context function (CURRENT_USER, CURRENT_ROLE, CURRENT_STATEMENT, ...), NEXTVAL, $x or @@x, a control character, or an unquoted name with a non-ASCII character or $$, or when it is over 32 KiB, 200 CTEs or 300 table references. CURRENT_DATE, CURRENT_TIME and CURRENT_TIMESTAMP stay allowed (as of Query Service 1.25 and policy engine 0.1.8). A 503 Row-level security could not be applied to this workspace means nothing ran because the policies could not be applied; it can be transient. A failed governed statement returns The statement failed. Its error text is not shown for a workspace with row-level security.kbc_at_ / kbc_pat_, including the child PAT of a multi-project scope, sent with X-KBC-ProjectId) or an administrator's own master Storage token. Any other token (an integration, a data app, Kai) names no end user, has no verified identity and reads nothing from a governed table. The administrator's subject is keboola| and the identity carries no groups, so group rules never match.KID: :project- :workspace- (a workspace of the default branch; a branch workspace also has branch- before project). The stack id is the one the Query Service is configureOnly the beginning is shown; read the rest in the repo