cortex-brain

cortex-brain

An MCP server that enables AI agents to search, read, and contribute to a structured markdown knowledge base with citations, freshness tracking, and a safe write path, providing a shared, auditable company memory.

Category
访问服务器

README

cortex-brain

Give your AI agents a company brain.

An MCP server over a plain-markdown knowledge base — cited articles, freshness tracking, open questions, and a safe write path. Your agents stop re-asking the same questions and start consulting (and growing) a shared, auditable memory of how your company actually works.

npx cortex-brain init my-brain      # scaffold a brain (12-domain taxonomy + conventions)
npx cortex-brain my-brain           # serve it to agents over MCP

Why

"AI agents need a living map of how a company works — knowledge extracted from scattered sources into executable form, so agents can actually do the work safely and consistently." — the "Company Brain" thesis (YC RFS)

Generic memory stores remember strings. A brain is structured: who said it, when, how fresh it is, what's still disputed. cortex-brain implements the cortex conventions — proven in production as an internal team wiki pattern — as five MCP tools any agent can use.

The tools

Tool What it does
brain_search Keyword search across all articles. Hits carry freshness (current/aging/stale/historical) so agents can judge reliability.
brain_get_article Full article: markdown + frontmatter — title, domain, tags, sources (who/when/where), linked open questions.
brain_file The single sanctioned write path: drops knowledge into inbox/ with a metadata header. A curator (human or agent) summarizes it into the wiki later — agents never mutate articles directly.
brain_list_questions Unresolved conflicts and code/wiki mismatches (q-NNN). Agents that learn an answer file it back.
brain_status Health report: coverage by domain, freshness distribution, stale articles, empty domains, pending inbox drops.

Use with Claude Code / any MCP client

{
  "mcpServers": {
    "company-brain": {
      "command": "npx",
      "args": ["-y", "cortex-brain", "/path/to/your/brain"]
    }
  }
}

Works on any cortex-style markdown knowledge base — including ones you already have. No database, no embeddings, no API keys: the markdown is the store, git is the history, humans can read every byte.

The conventions

The brain stays trustworthy because of five rules (enforced/encouraged by the tools):

  1. Citations — every claim tagged [sN], resolving to a frontmatter sources: entry (who, when, type, ref).
  2. Freshness lifecyclecurrent (≤60d) → aging (≤6mo) → stale; historical is deliberate and never auto-promoted. Computed live from frontmatter dates.
  3. State honesty — inbox drops declare state: local | staged | merged | deployed | n/a. Proposed work is never written up as shipped.
  4. Single writer — agents write only to inbox/; a curator owns the wiki. Conflicts become open questions, never silent overwrites.
  5. Open questions — disagreements are first-class (q-NNN), tracked to resolution.

Article format

---
title: Auth and Permissions
domain: products/atlas
last_updated: 2026-06-01
freshness: current
tags: [auth, rbac]
sources:
  - id: s1
    who: dana
    when: 2026-06-01
    type: meeting
    ref: resource-bin/products/atlas/2026-06-01-auth-sync.md
open_questions: [q-002]
---

# Auth and Permissions

Access tokens expire after 15 minutes. [s1]

CLI

cortex-brain init <dir> [--name <SystemName>]   Scaffold a new brain
cortex-brain <brain-path>                       Serve as MCP (stdio)
cortex-brain <brain-path> --status              Print health report, exit

Programmatic use

import { scanBrain, buildIndex, searchBrain, brainStatus } from "cortex-brain";

const articles = await scanBrain("./my-brain");
const hits = searchBrain(buildIndex(articles), articles, "deployment process");

Limitations (v0.1)

  • Keyword search (BM25-style). Hybrid dense retrieval + RRF is on the roadmap.
  • The curator (inbox → wiki summarization) is a convention + your agent's job, not yet an automated pipeline. The cortex skeleton includes a curator skill spec for Claude.
  • Single brain per server instance.

Development

npm install
npm test                  # vitest, 80%+ coverage enforced
npm run build
node scripts/smoke.mjs    # E2E: real MCP client over stdio, all five tools

License

MIT

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选