
Cortex
β 20from abbacusgroup
Ontology driven knowledge system with formal OWL-RL reasoning, SPARQL graph + SQLite dual store, and self-improving memory tiers. 22 MCP tools for capture, search, reasoning, graph operations, and diagnostics. Local-first.
Cortex
Cognitive knowledge system with formal ontology, reasoning, and intelligence serving.
Cortex captures knowledge objects (decisions, lessons, fixes, sessions, research, ideas), classifies them with an OWL-RL ontology, discovers relationships, reasons over the graph, and serves intelligence through hybrid retrieval.
CLI Commands
Command Description
cortex setup Interactive setup wizard
cortex init Initialize data directory and stores (deprecated β use cortex setup)
cortex install Install background services (macOS/Linux)
cortex uninstall Remove background services
cortex register Register MCP server with Claude Code
cortex capture Capture a knowledge object
cortex search Hybrid keyword + semantic search
cortex read Read object in full
cortex list List objects with filters
cortex status Health and counts
cortex context Briefing mode (summaries)
cortex dossier Entity-centric intelligence brief
cortex graph Show object relationships
cortex synthesize Cross-document synthesis
cortex entities List resolved entities
cortex serve Start MCP or HTTP server
cortex dashboard Start web dashboard
cortex backup Backup data directory to archive
cortex restore Restore from backup archive
cortex doctor Diagnostics: check, unlock, logs, repair
cortex pipeline Re-run intelligence pipeline on an object
cortex reason Run advanced reasoning (contradictions, patterns, gaps)
cortex import-v1 Import from Cortex v1 database
cortex import-vault Import from Obsidian vault
MCP Tools
26 tools for AI agent integration. Localhost-bound HTTP exposes all; non-localhost binds expose only the public set.
Public: cortex_search, cortex_context, cortex_dossier, cortex_read, cortex_capture, cortex_link, cortex_feedback, cortex_graph, cortex_list, cortex_classify, cortex_pipeline
Admin (localhost only): cortex_status, cortex_synthesize, cortex_delete, cortex_delete_entity, cortex_update, cortex_unlink, cortex_reason, cortex_query_trail, cortex_graph_data, cortex_list_entities, cortex_export, cortex_import, cortex_safety_check, cortex_debug_sessions, cortex_debug_memory
Architecture
Cortex runs as a single MCP HTTP server that owns the graph store. Claude Code, the dashboard, the CLI, and the REST API are all HTTP clients of that one server.
βββββββββββββββββ ββββββββββββββ βββββββββββββββ
β Claude Code β β Dashboard β β CLI β
β (MCP client) β β (browser) β β (terminal) β
βββββββββ¬ββββββββ βββββββ¬βββββββ ββββββββ¬βββββββ
β β β
β HTTP JSON-RPC β HTTP MCP β HTTP MCP (default)
β β β direct (--direct)
βΌ βΌ βΌ
ββββββββββββββββββββββββββββββββββββββββ
β cortex serve --transport mcp-http β
β (canonical MCP HTTP server) β
β PID-locked owner of graph.db β
ββββββββββββββββββββββββββββββββββββββββ
β
βΌ
βββββββββββββββββββββββββββββββ
β ~/.cortex/ β
β graph.db (Oxigraph) β
β cortex.db (SQLite WAL) β
βββββββββββββββββββββββββββββββ
-
Ontology: OWL-RL formal ontology with 8 knowledge types and 8 relationship types
-
Storage: Oxigraph (RDF/SPARQL) + SQLite (FTS5/BM25) dual-write
-
Pipeline: Classify β Extract entities β Link β Enrich β Reason
-
Retrieval: Hybrid keyword + semantic + graph-boosted ranking
-
Serving: 5 presentation modes (briefing, dossier, document, synthesis, alert)
-
Transports: MCP (stdio + HTTP), REST API, Web Dashboard
Service Management
# Install both MCP server and dashboard as background services
cortex install
# Install only the MCP server
cortex install --service mcp
# Remove all services
cortex uninstall
On macOS, this creates LaunchAgent plists (auto-start on login, auto-restart on crash). On Linux, this creates systemd user units.
Raw templates are available in deploy/ for manual setup.
--direct escape hatch
By default, CLI commands route through the running MCP server. If the server is down:
cortex --direct list # bypass MCP, open store directly
cortex --direct pipeline --batch # required for bulk SQL operations
Bootstrap commands (init, setup, import-v1, import-vault) always run directly.
Docker
docker compose up -d
# Server at http://localhost:1314
Knowledge Types
decision, lesson, fix, session, research, source, synthesis, idea
Relationship Types
causedBy, contradicts (symmetric), supports, supersedes (transitive), dependsOn, ledTo (inverse of causedBy), implements, mentions
Privacy
Cortex stores all data locally. No telemetry, no analytics, no phone-home. If you configure an LLM provider (via CORTEX_LLM_API_KEY), object content may be sent to that provider for classification and reasoning. Embeddings are computed locally by default using sentence-transformers.
License
Copyright (c) 2026 Abbacus Group. Licensed under the MIT License.
Trademark Notice
Cortex is a project of Abbacus Group and is not affiliated with any other product named Cortex.
pip install abbacus-cortex[embeddings]
cortex setupBefore it works, you'll need: CORTEX_LLM_API_KEY
Install
pip install abbacus-cortex[embeddings]
cortex setup
The setup wizard configures everything: LLM provider, embeddings, dashboard password, background services, and Claude Code registration.
Other install methods Lightweight (no PyTorch β wizard offers to install embeddings):
pip install abbacus-cortex
cortex setup
Homebrew:
brew install abbacusgroup/cortex/abbacus-cortex
cortex setup
From source:
git clone https://github.com/abbacusgroup/Cortex.git && cd Cortex
uv sync --extra embeddings
cortex setup
Docker:
docker compose up -d
For non-interactive installs (CI, scripts): cortex setup --auto uses environment variables.
Quick Start
cortex capture "Fix: Neo4j pool exhaustion" --type fix --content "Root cause was..."
cortex search "Neo4j"
cortex list
cortex context "Neo4j"
cortex dashboard # web UI at http://localhost:1315
Configuration
cortex setup writes configuration to ~/.cortex/.env. You can also edit it directly:
CORTEX_LLM_PROVIDER=anthropic
CORTEX_LLM_MODEL=claude-sonnet-4-20250514
CORTEX_LLM_API_KEY=sk-...
CORTEX_EMBEDDING_MODEL=all-mpnet-base-v2
Cortex loads .env from these locations in priority order: environment variables (highest), .env in the current working directory, then ~/.cortex/.env. The recommended location is ~/.cortex/.env for persistent configuration.
See .env.example for all options.
Troubleshooting
Crashed MCP server
If the MCP server is killed hard, stale lock files auto-recover on next start. For manual cleanup:
cortex doctor unlock # normal cleanup
cortex doctor unlock --dry-run # report only
cortex doctor unlock --force # bypass live-holder check
Log management
cortex doctor logs # show log file sizes and status
cortex doctor logs --tail 20 # last 20 lines
cortex doctor logs --rotate # rotate log files (safe while running)
Claude Code session staleness
After restarting the MCP server, restart Claude Code to clear its stale session ID. claude --resume restores your conversation. The dashboard and CLI do not have this issue.