Theme
AI Resources
ktx
ktx is a local context layer for data agents, built to help AI coding and agent tools query SQL warehouses with reusable metric definitions, warehouse context, wiki knowledge, and MCP or CLI access.
The current docs frame ktx around warehouse metadata, semantic definitions, business wiki content, reviewable project files, context-source ingestion, agent setup, CLI administration, and MCP tools for supported agent clients. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
Context infrastructure for data agents
ktx is positioned as a layer that helps agents find and reuse warehouse context instead of starting from scratch on every data question, with local project files for semantic sources, wiki notes, and generated context.
Why it stands out
Warehouse context plus agent-facing tools
The README highlights SQL warehouse support, dbt and semantic-layer ingestion, wiki or Notion-style business context, contradiction flags, CLI commands, and MCP tools for agent execution.
Availability
GitHub repo, npm package, and docs
The public materials include a GitHub repository, npm install path, quickstart commands, CLI reference, agent setup docs, MCP startup notes, project-layout guidance, and development instructions.
Why it matters
What makes it useful
ktx gives data agents reviewable warehouse context before they answer. Metrics, joins, semantic-layer entities, wiki knowledge, local project files, CLI search, and MCP tools become reusable context rather than one-off prompt material.
What to know
Where it fits
Read it as part of the agent infrastructure layer rather than the model layer. It is most relevant for readers comparing how agents can work with warehouses, semantic layers, company knowledge, local project context, and MCP-accessible tools.
Notable points
What stands out
ktx builds semantic-layer YAML and wiki Markdown from warehouses and connected context sources. Teams can review those files in git, while local runtime state and secrets remain separate, then expose approved context through CLI commands or MCP tools.
Before using
What to review
Which warehouse, semantic-layer, wiki, and business-context sources the project will be allowed to read.
Which LLM or embedding provider is configured, since the README says provider-bound data depends on the user's chosen setup.
Which generated YAML and Markdown belong in version control, and which local runtime files, telemetry, secrets, and company data must remain private.
Whether the team already has approved metric definitions or data-governance rules that ktx should follow rather than replace.
Reader fit
Who may find it relevant
Data teams exploring how AI agents can query warehouses without inventing metric logic each time.
Builders comparing MCP tools, CLI context search, semantic-layer ingestion, and wiki-backed agent context.
Teams using agents such as Codex, Claude Code, Cursor, or OpenCode around analytics projects.
Less relevant for readers who do not use a SQL warehouse or only need a one-off notebook query.
Editorial note
Why LifeHubber lists it
ktx brings shared metric definitions, joinable-column context, company knowledge, CLI search, and MCP access into one local layer. Data teams can review that context instead of rebuilding warehouse logic for every question.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
What to explore next
Keep data-agent context current and traceable.
ktx gives agents warehouse definitions and business context before they answer. These next steps cover changing source data and the wider ingestion, retrieval, and citation path around AI context.
More in AI Agents
Keep browsing this category
Explore more AI agent projects.
RAGFlow
infiniflow/ragflow
A self-hostable RAG and agent-context platform whose v0.27 line adds Knowledge Compilation, Agentic RAG thinking modes, document and data-source connectors, citations, APIs, and agent workflows.
UX/UI Agent Skills
plugin87/ux-ui-agent-skills
A Claude-focused project kit that connects design tokens, component specifications, accessibility guidance, visual-taste references, UX writing, framework adapters, runnable skills, validation gates, rendered critique, and a product starter.
Claude Code Game Studios
Donchitos/Claude-Code-Game-Studios
A multi-agent game-development studio system for Claude Code, organized around specialized agents, workflow skills, hooks, rules, and templates.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
