Ever watched an AI agent confidently generate a wrong answer because it queried the wrong dataset? If you're building data or analytics agents, you've probably faced this: agents lack context, memory, and a semantic layer to understand your data. That's where ktx comes in.
ktx is an executable context layer for data and analytics agents. It provides skills, memory, and a semantic layer so that Claude Code, Codex, or any AI agent can query your data accurately through the Model Context Protocol (MCP). Think of it as a smart bridge between your agent and your data – one that remembers past queries, understands business terms, and executes precisely.
What problem does it solve?
- Context-free queries: Agents often lack awareness of table schemas, relationships, or business definitions. ktx adds a semantic layer that maps business terms to actual data structures.
- Short-term memory: Without memory, agents repeat mistakes or forget user preferences. ktx retains context across sessions.
- Skill gaps: Agents don't know which SQL dialect or API to use. ktx provides pre-built skills for common data tasks.
How to use it
Getting started is straightforward:
# Install ktx (example – check docs for exact command)
npx ktx init
# Connect your data source
ktx connect --type postgresql --connection-string "postgresql://..."
# Define a semantic layer (e.g., map "revenue" to SUM(amount))
ktx define "revenue" as "SUM(orders.amount)"
# Run an agent with ktx context
claude --mcp "ktx"
Once connected, you can ask your agent questions like:
- "What was our revenue last quarter?"
- "Show me the top 10 customers by lifetime value"
ktx handles the translation, memory, and execution.
Why it's interesting
- Works with any MCP-compatible agent – Claude Code, Codex, and more.
- Semantic layer – No more teaching your agent your business logic every time.
- Memory – The agent learns from past interactions, improving accuracy over time.
- Open-source friendly – Extensible with custom skills.
If you're tired of correcting your AI's data queries, give ktx a try. It's the context layer your agent has been missing.
Top comments (0)