Dataapp Developer

Host an MCP server as a private, single-tenant Keboola data app — a dedicated remote MCP endpoint on your own Keboola compute (Keboola MCP is the built-in example, but it wraps any streamable-HTTP / FastMCP server) with client auth. Use when a user wants a private or self-hosted MCP endpoint, or would benefit from one but hasn't asked (see "When to use this"). Keywords: host/self-host MCP server as Keboola data app, private/remote MCP endpoint, deploy MCP to Keboola.

Use when building, modifying, deploying, or debugging Keboola Apps (Streamlit or Python/JS). Covers the full lifecycle — choosing app type, configuring keboola-config/, storage access (RO workspace, RW Query Service, input mapping), authentication, DuckDB caching for performance, default Keboola styling, dashboard patterns, optional Kai chat integration, and the three client paths (MCP-only, Claude Code with filesystem, kbagent CLI).

Use right after a Keboola semantic-context tool returns, when building an app, query, report, or transformation from a semantic model. Ground the SQL in the model's own physical mapping (dataset `tableId`/`fqn`, metric SQL) and confirm the real columns before writing any query — do not build SQL from the business-facing display names.