MCP Server reference
Reference for the Keboola MCP Server — available tools, restricting tool access with HTTP headers, and advanced setup options.
Reference for the Keboola MCP Server. To connect a client, see the how-to.
Available tools
Section titled “Available tools”Keboola’s MCP Server comes with a rich set of tools your AI client (like Claude or Cursor) can use to interact with your data environment — just by asking in plain language. Don’t worry about remembering command names — your AI client handles that. Just describe what you want to do.
- Components & Transformations – Create, edit, and launch them with natural language.
- Storage – Browse, edit, and document buckets, tables, and columns.
- SQL – Run and manage SQL queries.
- Jobs – Start, monitor, and debug execution flows.
- Documentation – Search official Keboola docs from within your AI chat.
Restricting tool access
Section titled “Restricting tool access”When using the remote MCP server, you may want to limit which tools are available to AI agents. This is useful for:
- AI agent restrictions: Limiting what actions an AI agent (like Devin or Cursor) can perform in your project
- Compliance and security: Enforcing data governance policies by restricting write operations
- Customer-specific access: Creating tailored access profiles for different use cases
The MCP server supports three HTTP headers for tool authorization:
| Header | Purpose |
|---|---|
X-Allowed-Tools | Only allow specific tools (comma-separated list) |
X-Disallowed-Tools | Block specific tools (comma-separated list) |
X-Read-Only-Mode | Restrict to read-only tools only (true/1/yes) |
These headers are set by the client (e.g., your AI agent integration or custom MCP client) when making HTTP requests to the MCP server. Refer to your MCP client’s documentation for how to configure custom HTTP headers.
For example, setting X-Read-Only-Mode: true allows agents to query and explore data but prevents them from creating or modifying configurations.
For detailed technical documentation including the full list of read-only tools and header combination behavior, see the Developer Documentation.
Advanced setup options
Section titled “Advanced setup options”These methods are for developers or specific use cases (e.g., testing, contributing to the MCP server). For CLI control, dev environments, or contributing to the MCP Server, check out the MCP GitHub repo.