SQLiteとFTS5検索を使用して、ホームラボのログ、Dockerイベント、およびAIのトランスクリプトにインテリジェンス層を提供します。
別名 jmagar/cortex, cortex, cortex-rmcp
- スター
- 4
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 3.9.1
- 最終コミット
- 2026年11月9日
- ライセンス
- AGPL-3.0
Cortex MCPとは
CortexはMCPサーバーです。 SQLiteとFTS5検索を使用して、ホームラボのログ、Dockerイベント、およびAIのトランスクリプトにインテリジェンス層を提供します。.
プロジェクトのREADMEから生成された概要
Cortex MCP server について
Cortex RMCPは、ホームラボや小規模なプライベートフリートからのデータを管理および検索するための、集約されたインテリジェンス層を提供します。syslog、Dockerイベント、OpenTelemetryのログ、メトリクス、トレースといった多様な運用証跡に加え、Claude、Gemini、CodexなどのプロバイダーからのAIセッションのトランスクリプトを収集します。システムはこれらの情報をSQLiteデータベースに保存し、FTS5による全文検索を利用することで、ユーザーが異なるデータソースを統合されたタイムラインやインシデントの束として相関分析できるようにします。
開発者は、ネイティブCLI、認証済みREST API、またはMCP serverを通じてデータとやり取りできます。MCPの実装には2つのモードがあります。ローカルのデータベースファイルを読み取るクエリ専用のstdioモードと、ベアラートークンを使用して永続的なデーモンに接続するstreamable HTTPモードです。この構成は、公開された管理インターフェースではなく、信頼できる環境向けに特別に設計されています。検索、フィルタリング、および繰り返されるエラーシグネチャやサービストポロジの分析ツールを提供することで、複雑な調査を可能にします。
できること
- 1システムインシデントの調査AIクライアントが相関されたログやタイムラインを検索し、サービス障害の根本原因を特定できます。
- 2AIチャット履歴の分析開発者がさまざまなAIツールのトランスクリプトをインデックスおよびクエリして、特定のスキルやイベントを抽出できます。
- 3フリートアクティビティの監査ユーザーは、インフラストラクチャ全体のホストのハートビート、シェル履歴、およびエージェントのコマンド記録を追跡できます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
Cortex MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにCortex MCPをインストール
$ claude mcp add --env 'CORTEX_API_TOKEN=<YOUR_CORTEX_API_TOKEN>' --env 'CORTEX_TOKEN=<YOUR_CORTEX_TOKEN>' cortex -- npx -y cortex-rmcpCursorにCortex MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"cortex": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
],
"env": {
"CORTEX_API_TOKEN": "<YOUR_CORTEX_API_TOKEN>",
"CORTEX_TOKEN": "<YOUR_CORTEX_TOKEN>"
}
}
}
}VS CodeにCortex MCPをインストール
.vscode/mcp.json
{
"servers": {
"cortex": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
],
"env": {
"CORTEX_API_TOKEN": "<YOUR_CORTEX_API_TOKEN>",
"CORTEX_TOKEN": "<YOUR_CORTEX_TOKEN>"
}
}
}
}VS Code CLIにCortex MCPをインストール
$ code --add-mcp '{"name":"cortex","type":"stdio","command":"npx","args":["-y","cortex-rmcp"],"env":{"CORTEX_API_TOKEN":"<YOUR_CORTEX_API_TOKEN>","CORTEX_TOKEN":"<YOUR_CORTEX_TOKEN>"}}'Claude DesktopにCortex MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"cortex": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
],
"env": {
"CORTEX_API_TOKEN": "<YOUR_CORTEX_API_TOKEN>",
"CORTEX_TOKEN": "<YOUR_CORTEX_TOKEN>"
}
}
}
}CodexにCortex MCPをインストール
$ codex mcp add cortex --env 'CORTEX_API_TOKEN=<YOUR_CORTEX_API_TOKEN>' --env 'CORTEX_TOKEN=<YOUR_CORTEX_TOKEN>' -- npx -y cortex-rmcpCodex config.tomlにCortex MCPをインストール
~/.codex/config.toml
[mcp_servers.cortex] command = "npx" args = ["-y", "cortex-rmcp"] [mcp_servers.cortex.env] CORTEX_API_TOKEN = "<YOUR_CORTEX_API_TOKEN>" CORTEX_TOKEN = "<YOUR_CORTEX_TOKEN>"
Gemini CLIにCortex MCPをインストール
$ gemini mcp add -s user -e 'CORTEX_API_TOKEN=<YOUR_CORTEX_API_TOKEN>' -e 'CORTEX_TOKEN=<YOUR_CORTEX_TOKEN>' cortex npx -- -y cortex-rmcpGemini settings.jsonにCortex MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"cortex": {
"command": "npx",
"args": [
"-y",
"cortex-rmcp"
],
"env": {
"CORTEX_API_TOKEN": "<YOUR_CORTEX_API_TOKEN>",
"CORTEX_TOKEN": "<YOUR_CORTEX_TOKEN>"
}
}
}
}設定
CORTEX_API_TOKENシークレットBearer token for Cortex REST API routes when running daemon/API mode.
CORTEX_TOKENシークレットOptional bearer token for Cortex MCP HTTP mode; also used by some shared configs.
CORTEX_DB_PATHCORTEX_HOMEOptional Cortex home directory containing configuration and local SQLite data.
CORTEX_RMCP_RELEASE_BASE_URLOptional release download base URL override.
CORTEX_RMCP_REPOOptional GitHub owner/repo override for release asset downloads.
CORTEX_RMCP_VERSIONOptional GitHub release tag override for the downloaded Cortex binary.
RUST_LOGTracing filter for Cortex logs.
| 名前 | 説明 | 種類 |
|---|---|---|
| CORTEX_API_TOKEN | Bearer token for Cortex REST API routes when running daemon/API mode. | シークレット |
| CORTEX_TOKEN | Optional bearer token for Cortex MCP HTTP mode; also used by some shared configs. | シークレット |
| CORTEX_DB_PATH | — | |
| CORTEX_HOME | Optional Cortex home directory containing configuration and local SQLite data. | |
| CORTEX_RMCP_RELEASE_BASE_URL | Optional release download base URL override. | |
| CORTEX_RMCP_REPO | Optional GitHub owner/repo override for release asset downloads. | |
| CORTEX_RMCP_VERSION | Optional GitHub release tag override for the downloaded Cortex binary. | |
| RUST_LOG | Tracing filter for Cortex logs. |
自動チェック
実行日 2026年11月13日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能合格
- オープンソースライセンス (OSI)合格
- 過去1年以内にコミットまたはリリースあり合格
- パッケージ名が有名なパッケージに酷似していない合格
- リモートエンドポイントがHTTPSを使用未チェック
- 破壊的なツールがラベル付けされている未チェック
- モデルへの隠れた指示がない合格
- パッケージおよびその依存関係に重大な勧告なし合格
README
GitHubで見るCortex
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
It collects logs and operational evidence, stores them in SQLite with FTS5 search, and exposes one shared intelligence layer through CLI, REST, MCP, and a bundled browser workspace.
Cortex began as a syslog receiver. It now covers network logs, Docker, managed files, OpenTelemetry logs, metrics, and traces, host heartbeats, fleet inventory, shell and agent activity, and Claude, Codex, Gemini CLI, and Antigravity transcripts. It correlates those sources into timelines, incidents, and an evidence-backed topology graph without making the graph a second source of truth.
At a glance
| Area | What Cortex provides |
|---|---|
| Ingest | UDP/TCP syslog, OTLP/HTTP logs, metrics, and traces, Docker logs and events, managed file tails, host heartbeats, AI transcripts, shell history, agent command records, and fleet inventory |
| Storage | SQLite in WAL mode, FTS5 full-text search, bounded metadata, retention, storage budgets, maintenance jobs, checkpoints, and 63 sequential schema migrations |
| Investigation | Search, filtering, context, timelines, patterns, anomaly comparison, cross-source correlation, recurring error signatures, deterministic incident bundles, and graph explanations |
| Fleet intelligence | SSH and API inventory collectors, host state, service topology, container and route relationships, redacted evidence, and rebuildable graph projections |
| AI operations | Claude, Codex, Gemini CLI, and Antigravity session indexing; skill, MCP, and hook event extraction where each provider exposes them; incident clustering; and guarded local LLM assessments |
| Interfaces | Native CLI, one action-dispatched MCP tool, authenticated REST APIs, MCP prompts and resources, an MCP Apps search widget, and a bundled investigation workspace |
| Operations | Setup and repair, diagnostics, Compose control, backup, integrity checks, WAL checkpoints, vacuum, update workflows, agents, and health endpoints |
[!IMPORTANT] Cortex is designed for a trusted homelab or small private fleet. It is not a clustered log warehouse, a general-purpose SIEM, or a safe place to expose unauthenticated administrative surfaces to the public internet.
Contents
- Quick start
- How Cortex is built
- Ingestion
- Investigation and intelligence
- Fleet inventory and graph
- AI session intelligence
- Alerts and notifications
- Interfaces
- Configuration
- Authentication and trust boundaries
- Storage and maintenance
- Deployment and distribution
- Operations
- Development and verification
- Documentation
- Current boundaries
- License
Quick start
Install and choose a role
curl -fsSL https://raw.githubusercontent.com/dinglebear-ai/cortex/main/install.sh | sh
On Windows x64:
irm https://raw.githubusercontent.com/dinglebear-ai/cortex/main/install.ps1 | iex
The checksum-verified bootstrap supports Linux x64/ARM64, macOS ARM64, and
Windows x64. It runs cortex setup start, which asks whether this machine is a
server, a client, or a host agent. Server setup prepares configuration, distinct
MCP/REST credentials, storage and managed Compose. Client setup connects selected
MCP clients. Agent setup detects local collection prerequisites and enables only
the capabilities you explicitly select. First server setup also asks for
authentication mode, exposure, and an optional six-hour backup schedule.
Already have the CLI, or automating installation? Select the role explicitly:
cortex setup start --role server --clients codex,claude,gemini
cortex setup start --role client --server https://cortex.example.com \
--token-file /private/mcp-token --api-token-file /private/rest-token
cortex setup start --role agent --server https://cortex.example.com \
--token-file /private/ingest-token --capabilities docker,transcripts
First-time noninteractive setup requires --role; subsequent setup reuses the
saved choice. --dry-run --json previews configuration and capabilities without
installing services. All advanced settings remain available through --set and
--secret-file; sensitive collection requires explicit selection.
--backup-schedule and --no-backup-schedule save the backup scheduling choice.
cortex setup effective --json
cortex setup verify --json
cortex update
Verification proves authenticated MCP access and REST access when configured; source delivery still needs its own evidence. Updates use saved deployment settings and respect version pins. See the setup guide for capability selection, OAuth, prerequisites, source builds, manual native operation, and installer environment controls; see the deployment runbook for backup and recovery.
For guided agent assistance:
npx skills add dinglebear-ai/cortex --skill install-cortex
Start a fresh task and invoke $install-cortex.
The npm launcher remains available for local CLI and stdio MCP use with Node.js 18 or newer:
npx -y @dinglebear/cortex --help
npx -y @dinglebear/cortex mcp
npm install --global @dinglebear/cortex
Connect an MCP client
Query-only stdio mode reads the configured local database and starts no network listeners:
{
"mcpServers": {
"cortex": {
"command": "npx",
"args": ["-y", "cortex-rmcp", "mcp"],
"env": {
"CORTEX_DB_PATH": "/absolute/path/to/cortex.db"
}
}
}
}
Streamable HTTP mode connects to the persistent daemon:
{
"mcpServers": {
"cortex": {
"url": "http://127.0.0.1:3100/mcp",
"headers": {
"Authorization": "Bearer your-cortex-token"
}
}
}
}
A useful first call is:
{"action":"status"}
Then narrow the investigation with tail, errors, search, timeline, or context before using broader analysis operations.
How Cortex is built
Cortex is one Rust binary with multiple operating modes. The same application and service layer backs the CLI, REST handlers, and MCP handlers, so validation, limits, identity resolution, redaction, and business rules do not belong to one transport alone.
INGESTION
Syslog UDP/TCP OTLP signals Docker agent / pull
Managed file tails Heartbeats Claude / Codex / Gemini / Antigravity
Shell history Agent commands Fleet inventory
\ | /
\ | /
+---- bounded parsing and enrichment ----+
|
scrub, normalize, batch
|
SQLite WAL + FTS5
|
+----------------+----------------+
| |
authoritative records derived accelerators
logs, heartbeats, rollups, signatures,
inventory, sessions graph projections
| |
+----------------+----------------+
|
shared service layer
|
CLI REST MCP Web workspace
The daemon supervises its receivers and background services with cooperative cancellation. Shutdown drains HTTP requests, gives maintenance tasks 10 seconds to finish before abort-and-join, gives ingest 5 seconds to flush, and then attempts a WAL checkpoint. Already-running blocking SQLite calls cannot be cancelled by Tokio.
Background services include:
- Retention and storage-budget enforcement
- WAL and FTS maintenance
- Docker ingest supervision
- File-tail supervision
- Error-signature scanning
- Notification evaluation, dispatch, and digest scheduling
- Inventory refresh and backfill
- Graph projection refresh
- AI-session and timeline rollups
- Database optimization and maintenance jobs
Heavy analytical reads and maintenance jobs have separate concurrency controls so one expensive investigation cannot starve the ingest path.
Ingestion
All log-like sources are normalized into the same durable log model, enriched where safe, scrubbed where configured, and written through bounded batch paths.
Syslog over UDP and TCP
Cortex listens on the same configurable port for UDP and TCP syslog. It parses common RFC 3164 and RFC 5424 shapes, preserves the raw frame, records sender identity, normalizes severity and facility, and enriches known application formats.
Relevant defaults:
- Bind:
0.0.0.0:1514 - Maximum message: 8 KiB
- Maximum concurrent TCP connections: 512
- TCP idle timeout: 300 seconds
- Writer batch: 100 records or 500 ms
- Write queue capacity: 10,000 records
Syslog has no application-layer authentication. Restrict senders with network controls and CORTEX_ALLOWED_SOURCE_CIDRS when the listener is reachable beyond a trusted network.
Built-in enrichment recognizes useful signals from AdGuard, Authelia, Docker lifecycle events, fail2ban, Linux kernel and OOM events, SWAG, reverse-proxy logs, and host-local Cortex Docker agent metadata. Source gates can restrict enrichment that would otherwise trust a marker inside an unauthenticated syslog body.
OpenTelemetry ingestion
Cortex accepts protobuf OTLP/HTTP export requests on the shared HTTP listener. Logs use POST /v1/logs with a 4 MiB body limit and flow through the normal writer. Metrics use POST /v1/metrics and traces use POST /v1/traces, each with an 8 MiB body limit and dedicated storage. Metric requests admit at most 5,000 points and also enforce a bounded normalized payload budget.
Current OTLP scope is intentionally narrow:
- Logs, traces, and metrics over HTTP/protobuf are supported.
- OTLP/gRPC is not implemented.
All three OTLP endpoints authenticate with CORTEX_TOKEN — the same static MCP bearer token that guards POST /mcp, read from the managed ~/.cortex/.env on a deployed host. It is not CORTEX_API_TOKEN (REST /api/*) and not CORTEX_API_ADMIN_TOKEN. Loopback and trusted-gateway policies skip the check. An OAuth-only deployment with no static token denies OTLP outright, because machine exporters have no OAuth flow — so a non-loopback OAuth-only OTLP exposure is rejected at startup unless CORTEX_TOKEN is set.
Docker logs and events
Cortex supports two Docker collection paths:
- Host-local agent, the preferred multi-host path. The host-local cortex agent reads the local Docker socket, converts logs and lifecycle events into bounded records, and forwards them to the server without changing Docker's daemon logging driver.
- Central pull compatibility mode, an optional server-side collector for explicitly configured Docker Engine or docker-socket-proxy HTTP endpoints. It records per-container checkpoints and reconnects with bounded exponential backoff.
Central pull is disabled by default. The CORTEX_DOCKER_HOSTS shorthand expands hosts into insecure http://host:2375 endpoints and should only be used on a tightly controlled private network. A hosts file supports explicit base URLs and safer endpoint configuration.
Managed file tails
Managed file-tail sources are persisted in a registry and supervised by the daemon. Add, remove, list, and inspect sources through the CLI, REST, or the file_tails MCP admin action.
The path policy rejects unsafe targets, including paths outside configured roots, symlink escapes, non-regular files, and sensitive mounts. Container deployments expose an explicit read-only file-tail root rather than the entire host filesystem.
Host heartbeats
The host agent can post bounded JSON snapshots to POST /v1/heartbeats. Heartbeats include host state such as load, memory, disks, networking, processes, and container summaries. They power host_state, fleet_state, and correlate_state.
Heartbeat request bodies are capped at 256 KiB. Heartbeat data has short operational retention separate from the main log-retention policy.
AI transcripts
Cortex indexes local and forwarded transcript data from:
- Claude Code projects under
~/.claude/projects - Codex sessions and worktrees under
~/.codex/sessionsand~/.codex/worktrees - Gemini CLI chat data under
~/.gemini/tmp - Antigravity desktop's redacted transcript projections under
~/.gemini/antigravity/brain/<session>/.system_generated/logs/transcript.jsonl - Antigravity CLI's redacted transcript projections under
~/.gemini/antigravity-cli/brain/<session>/.system_generated/logs/transcript.jsonl
The Antigravity adapter reads only the narrow redacted JSONL projections above; it does not scan conversation databases or other brain artifacts. The scanner supports incremental checkpoints, parse-error records, bounded chunks, broad-path rejection, and safe recovery from changed files. It extracts normalized transcript rows plus dedicated skill, MCP tool-call, and hook events where those lanes are represented by the provider schema, and reports unsupported lanes honestly.
A satellite agent can send already-parsed records to POST /v1/ai-transcripts, which prevents transcript collection from depending on the database living on the same host as the AI client.
Shell and agent activity
Satellite agents can forward additional operational evidence to the shared server:
POST /v1/agent-commandsfor deduplicated agent command-spool recordsPOST /v1/shell-historyfor parsed Bash, Zsh extended-history, and Atuin records
These records use the same storage and correlation model as the rest of Cortex, which makes an agent change or shell command visible beside the service failure that followed it.
Fleet inventory
Inventory collection builds a redacted fleet snapshot from local files, SSH probes, Docker endpoints, and optional service APIs, then projects safe relationships into the investigation graph.
Investigation and intelligence
Cortex exposes bounded workflows rather than a raw SQL console.
Search and context
- FTS5 full-text search with host, app, severity, source, project, session, and time filters
- Structured filter-only retrieval for indexed fields
- Recent tails and single-row retrieval with raw-frame evidence
- Surrounding context around a log ID or timestamp
- Host, app, and source-IP inventories
- Clock-skew measurement using event and receive timestamps
Time and volume analysis
- Bucketed timelines
- Ingest-rate and queue-pressure state
- Near-duplicate message pattern clustering
- Recent-versus-baseline anomaly detection
- Side-by-side time-range comparison
- Silent-host and silent-stream detection
- Database, storage, and runtime statistics
Correlation
- Cross-host correlation around a timestamp
- AI-session anchor correlation against infrastructure logs
- Topic resolution through the entity graph before timeline construction
- Host-state correlation across logs, heartbeats, and inventory
- Historical incident similarity using FTS5
- Deterministic incident context bundles with bounded evidence
Recurring errors
An optional background scanner groups repeating error signatures into durable records. Operators can inspect unaddressed signatures, acknowledge them, revoke acknowledgements, and correlate a signature with logs and graph evidence.
Error detection is disabled by default. When enabled, it scans bounded batches, records lower-severity recurrences without paging, and can notify only above a configured severity floor.
Fleet inventory and graph
Inventory collectors
The native inventory subsystem can collect and normalize evidence from:
- Local and remote Compose, reverse-proxy, and AdGuard Home configuration
- Local process, storage, project, and raw configuration inventories
- SSH sessions to remote fleet hosts
- Local and remote Docker endpoints
- Tailscale
- UniFi
- Unraid
- Media-stack services and related APIs
SSH collection uses strict host-key verification, bounded concurrency, timeouts, and retry backoff. Sensitive fields are redacted before persistence.
The cache lives under ~/.cortex/inventory by default and includes:
normalized/homelab.json: the typed normalized fleet snapshotcollection-state.json: collector health, timing, and warning stateraw/<run-id>/...: raw-but-redacted supporting artifacts
The map action reads the normalized cache. It does not trigger a collection run and does not return raw config bodies or credential-bearing URLs.
Derived investigation graph
The graph connects canonical entities such as:
- Hosts and source identities
- Logical services and concrete service instances
- Applications and containers
- Domains, routes, and endpoints
- AI projects and sessions
- Error signatures and operational findings
Relationships carry confidence, trust, reason codes, timestamps, and bounded evidence references. The graph supports entity resolution, neighborhoods, topology questions, evidence lookup, and explanation paths.
The graph is a rebuildable projection. Raw logs, heartbeats, inventory records, error signatures, and AI session data remain authoritative. Projection rebuilds use staging tables and a short serialized swap, record watermarks and metrics, and preserve explicit degraded state when refresh fails.
AI session intelligence
Cortex treats AI transcripts as operational evidence, not merely chat archives.
Deterministic session analysis
The shared service layer can:
- List and search sessions by project
- Measure activity in five-hour usage blocks
- Summarize project context
- List observed tools and projects
- Detect frustration or abuse signals
- Group those signals into scored incidents
- Correlate AI activity with non-AI infrastructure logs
- Extract skill invocations
- Extract MCP server and tool-call events
- Extract hook configuration and runtime events
- Build skill-first, MCP-first, and hook-first investigation bundles
The deterministic query and incident workflows are available through CLI, REST, and MCP.
Guarded local assessments
LLM-backed assessments are deliberately local-only. They run through cortex assess and are not exposed as MCP actions or REST routes because they spawn a local provider subprocess.
CORTEX_LLM selects the provider and optional model for every LLM operation: skill, MCP, hook, and abuse assessments, including dry-run audit metadata. Set CORTEX_LLM=codex (the default, using Codex app-server) or CORTEX_LLM=gemini (Gemini CLI). To pin the model globally, use CORTEX_LLM=codex/gpt-5.5 or CORTEX_LLM=gemini/gemini-3.1-flash-lite-preview. An explicit model in CORTEX_LLM wins over --model; otherwise that existing flag can select a model for one invocation. Empty or unsupported selectors fail without provider fallback.
The selector also works in managed ~/.cortex/.env; process environment values take precedence. Settings are retained after config loading.
The old CORTEX_CODEX_MODEL and CORTEX_HEADLESS_GEMINI_MODEL variables are ignored. Command and authentication-home overrides remain installation settings, not provider selectors. --no-llm needs no provider configuration or credentials.
The shared LLM runner enforces:
- A global kill switch
- Global and per-action concurrency limits
- Per-minute and per-hour rate limits
- Per-action circuit breakers and cooldowns
- Invocation timeouts
- Prompt and output byte caps
- An explicit background-enrichment gate, disabled by default
- Durable audit records for successes, failures, timeouts, and policy denials
Default guard values allow one concurrent invocation, three per minute and thirty per hour per action, a 120-second timeout, a 1 MiB prompt cap, and a 256 KiB output cap.
Prompt scrubbing is enabled by default. Skill, MCP, and hook event extraction happens before scrubbed transcript text is persisted, so structured operational signals are retained without requiring raw prompt storage.
Alerts and notifications
Notifications are optional and disabled by default. When enabled, Cortex uses Apprise as the delivery bridge and a durable SQLite outbox for retry, deduplication, and dead-letter handling.
Built-in evaluators cover:
- OOM kills
- Containers exiting nonzero
- fail2ban bans
- Authelia MFA failures
- Disk-fill and storage guardrail pressure
- Ingest queue pressure
- Complete ingest silence
- Heartbeat silence
- Silence from previously active continuous streams
The notification subsystem includes:
- Configurable evaluator cadence
- Per-rule toggles and thresholds
- Deduplication windows
- Outage-scoped silence keys
- Bounded retry with dead-letter state
- Recent-firing history
- Test notifications
- A scheduled daily digest
By default, continuous stream-silence tracking covers UDP/TCP syslog, agent Docker, Docker stream and event records, and managed file tails. Sporadic sources such as transcripts and shell history are intentionally excluded.
Interfaces
CLI
Run cortex --help and command-specific --help for the generated command tree.
| Group | Purpose |
|---|---|
search, filter, tail |
Log retrieval |
hosts, apps, entity, graph |
Discovery and topology |
analysis, correlate, state, stats, timeline |
Investigation and analytics |
sessions, assess |
AI-session queries and local guarded assessments |
alerts |
Error signatures, acknowledgements, and notification history |
ingest, heartbeat |
Collectors, agents, file tails, inventory, and heartbeats |
serve, mcp |
Full daemon and query-only stdio MCP modes |
doctor, status, db, compose |
Diagnostics and maintenance |
setup, update, config, completions |
Lifecycle and operator tooling |
Examples:
cortex search "oom killer" --host devhost --since 1h
cortex filter --severity err --since 6h
cortex timeline --since 24h
cortex sessions search "migration failure"
cortex graph explain --help
cortex alerts errors list
cortex ingest inventory refresh --json
cortex ingest filetail list
cortex status
cortex doctor
The CLI supports direct/local operation and HTTP operation. REST-backed mode is the normal remote path and uses CORTEX_URL plus CORTEX_API_TOKEN.
MCP
Cortex exposes one MCP tool named cortex. Its required action field selects an action from a single authoritative Rust registry. The mechanically generated current count is published in the live coverage inventory.
The current scope split is:
- 53 read actions requiring
cortex:read - 6 admin actions requiring
cortex:admin:artifact_evidence_record,ack_error,unack_error,file_tails,notifications_test, andllm_invocations - 1 informational action,
help, which requires an authenticated context when authentication is mounted but no read/admin scope
Cortex MCPのよくある質問
Cortex MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --env 'CORTEX_API_TOKEN=<YOUR_CORTEX_API_TOKEN>' --env 'CORTEX_TOKEN=<YOUR_CORTEX_TOKEN>' cortex -- npx -y cortex-rmcpを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
Cortex MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
Cortexはどのような種類のログを取り込めますか?
Cortexは、syslog (UDP/TCP)、OTLPログ、メトリクス、トレース、Dockerのログとイベント、管理されたファイルのテール、ホストのハートビート、およびAIのトランスクリプトを収集します。
Cortexは大規模なエンタープライズ利用に適していますか?
いいえ。Cortexは、クラスター化されたログウェアハウスや汎用SIEMではなく、信頼できるホームラボや小規模なプライベートフリート向けに特別に設計されています。
MCPクライアントをCortexに接続するにはどうすればよいですか?
ローカルデータベースを指定してクエリ専用のstdioモードを使用するか、ベアラートークンを使用して永続的なデーモンに接続するstreamable HTTPモードを使用できます。