The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
MCP Server
Model Context Protocol (MCP) Server for the Keboola Platform
Install
$
uvx keboola_mcp_server login --api-url "$KBC_STORAGE_API_URL"Claude Code
claude mcp add mcp-server -- uvx keboola_mcp_server login --api-url "$KBC_STORAGE_API_URL"Cursor / Claude Desktop (mcp.json)
{
"mcpServers": {
"mcp-server": {
"command": "uvx",
"args": [
"keboola_mcp_server",
"login",
"--api-url",
"\"$KBC_STORAGE_API_URL\""
]
}
}
}Install command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Keboola MCP Server
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.
Overview
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.
Features
With the AI Agent and MCP Server, you can:
- Storage: Query tables directly and manage table or bucket descriptions
- Components: Create, List and inspect extractors, writers, data apps, and transformation configurations
- SQL: Create SQL transformations with natural language
- Jobs: Run components and transformations, and retrieve job execution details
- Flows: Build and manage workflow pipelines using Conditional Flows and Orchestrator Flows.
- Data Apps: Create, deploy and manage Keboola Streamlit Data Apps displaying your queries over storage data.
- Metadata: Search, read, and update project documentation and object metadata using natural language
- Dev Branches: Work safely in development branches outside of production, where all operations are scoped to the selected branch.
🚀 Quick Start: Remote MCP Server (Easiest Way)
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.
What is the Remote MCP Server?
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.
How to Connect
- Get your remote server URL: Navigate to your Keboola Project Settings →
MCP Servertab - Copy the server URL: It will look like
https://mcp.<YOUR_REGION>.keboola.com/mcp - Configure your AI assistant: Paste the URL into your AI assistant's MCP settings
- Authenticate: You'll be prompted to log in with your Keboola account. Which project(s) to work on is chosen afterwards, in the conversation (e.g. "list my Keboola projects" / "use project X")
Supported Clients
Cursor: Use the "Install In Cursor" button in your project's MCP Server settings or click this button
Claude Desktop: Add the integration via Settings → Integrations
Claude Code: Install using
claude mcp add --transport http keboola <URL>(see below for details)Windsurf: Configure with the remote server URL
Make: Configure with the remote server URL
Other MCP clients: Configure with the remote server URL
Claude Code Setup
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 <YOUR_REGION> with your Keboola region:
Similar plugs
Reverse engineer anything with agents, from app behavior down to native binaries.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…
