The all-in-one data stack for agents.
Your data jobs deserve to run on the right tool. Whether you're bringing existing infra, or exploring our open source deployments, oleander empowers your entire data stack to work together as a team.
MCP connector Server URL https://oleander.dev/mcpCopy Login OAuth Skills 7 in the Claude listing
Lake catalog Engine-agnostic oleander lake catalog conventions: catalog.namespace.table naming, hierarchy, and catalog-qualified reads/writes without raw storage paths. Lake query Runs lake SQL through oleander's query router: query_run for reads, query_submit for writes, spark_sql_submit for named Spark jobs. Polars submit Runs Polars queries or scripts on oleander via the CLI, in local or distributed mode, and saves results to the lake catalog. Spark best practices General Apache Spark best practices for scalable, maintainable DataFrame jobs: avoid driver materialization, reduce shuffle, join efficiently, and cache carefully. Spark lake catalog Spark patterns for reading and writing oleander lake catalog tables: spark.table(), append vs overwrite, and avoiding driver-side writes. Spark lineage Preserves connected OpenLineage for oleander Spark jobs by avoiding collect()/toPandas() between read and write, and using env vars for runtime config. Spark submit Submits, monitors, aborts, and configures Spark jobs on oleander via MCP (spark_jobs_submit), the CLI, and the TypeScript SDK. 