A centralized context layer for every AI tool your team uses.
Cornu stores, organizes, and serves your company's information as structured, permission-aware context. Your team gets accurate answers from the AI assistants they already use, without learning a new interface.
Not another chatbot. Not an LLM. Cornu has no chat UI of its own. Your team uses the AI tool they already love, with Cornu serving as the context layer behind it.
How Cornu works
Teach and answer.
Do everything from the AI assistant your team already uses (Claude, ChatGPT, Gemini, Copilot).
01
Teach
Content Owners upload, approve, and version your company's information by asking their AI assistant. Knowledge areas segment content by department, team, or project, so the right people own the right content and only the right people can see it.
What you say to teach
02
Answer
When a question comes in, whether a person asks their AI assistant or an autonomous AI agent needs context, the AI calls Cornu and returns accurate, permission-aware answers.
What you ask to get answers
What's inside
Features.
Content management
A full lifecycle for the information that powers your AI: submission, approval, versioning, revision, expiry, and removal. PDF, DOCX, Markdown, and plain text are first-class.
- ✓Content submission and approval
- ✓Versioning and revision history
- ✓Stale content review and expiry
- ✓Hybrid semantic and keyword search
- ✓See the questions users and AI agents ask, to find the gaps in your information layer
Permissions that mirror your org
Knowledge areas segment content by department, team, project, or any other dimension you choose. Think of them as folders that control who can see what.
- ✓Knowledge areas scoped by department, team, or project
- ✓Manage users and their access from your company's identity provider (Okta, Google, Microsoft, etc.)
- ✓Per-area owners and contributors
- ✓Query-time permission enforcement on every retrieval
Native MCP integration
An MCP server that exposes Cornu's full toolset to any MCP-compatible client: content management tools for uploading and organizing documents, plus search and retrieval tools for answers. It is how Cornu delivers everything inside the AI assistant your team already uses, with no new tool to learn.
- ✓MCP server conforming to the current spec
- ✓OAuth 2.1 / SSO via your identity provider
- ✓Per-request permission enforcement
- ✓Hybrid retrieval, not just vector search
Automation ready
Content pipelines let you submit, update, and remove content programmatically. Available over both MCP tools and a REST API, so agents and traditional integrations both work.
- ✓REST API for traditional integrations
- ✓MCP tools for agent-driven flows
- ✓Service accounts with write scopes
- ✓Permissions resolved through your identity provider
Built for everyone touching information
Roles.
Most of your team never logs into Cornu. They just ask their AI tool a question. Behind the scenes, four roles keep information accurate, current, and properly scoped.
Admin
Owns the subscription, identity provider connection, and top-level configuration. Procurement or IT leadership at enterprise; an engineering lead at smaller companies.
Content Owner
Owns a knowledge area: HR, Engineering, Legal, or any other domain. Reviews and approves submissions, manages who can access the area, and keeps it accurate over time.
Contributor
A subject matter expert who submits content for review. Submissions route to a Content Owner for approval before they go live.
Consumer
Everyone else. They never log into Cornu. They ask their AI tool a question and get an answer scoped to what they're allowed to see.