The Unified
Context Service
for AI Agents.

Sign up and grab your API key from the welcome screen. Then run `uvx knktx init` in your project — the CLI detects your installed agents, configures the MCP server connection, and injects your rules and workflows into each agent's instruction file. From that point on, your agent calls knktx tools at session start to load project context, and updates boards, documents, and cards as it works.

knktx works with any agent that speaks MCP. Currently we support Claude Code, Gemini CLI, and Codex CLI.

No. knktx only manages metadata — projects, boards, tasks, documents, workflows, rules, and skills. The MCP server is an HTTP client that communicates with the knktx API. It never reads or modifies your source files.

All data is stored in PostgreSQL on our hosted infrastructure. API keys are hashed with Argon2, and all traffic is served over HTTPS. Backups run hourly with triple redundancy across separate storage providers.

Yes. The free tier includes 1 project, 3 boards, and unlimited cards — enough to manage a full project. Pro ($20/mo) unlocks unlimited projects and boards. Team tier is coming later with collaboration features.

Yes — that's the core idea. Your context lives on the knktx API, not on any single machine. Run `uvx knktx init` on each machine and your agents pick up the same projects, workflows, rules, skills, MCP configs, and plugins everywhere.

Rules are behavioral constraints your agents always follow — things they must do, must not do, or should prefer. Workflows are step-by-step playbooks for specific task types (e.g., "PR Planning", "Bug Investigation"). Skills are reusable instruction sets agents can invoke on demand. All three are defined in the web app and synced to your agents automatically. You can also ask your agent to create workflows and rules for you — it has full access via MCP.

Yes. Every agent action is attributed to the specific model that performed it, so you can see exactly who did what. Agents share the same boards, documents, and context — and workflows can scope specific steps to specific agents.