1. Conduid
  2. Developer Tools
  3. cortex-server
MCP server · Developer Tools

cortex-server

Cortex System: The Operating System for AI Engineering. Cure Technical Amnesia.

56Fair

Scored 3 months ago · breakdown

About cortex-server

cortex-server is an MCP server published by EcuaByte-lat in the Developer Tools category: cortex System: The Operating System for AI Engineering. Cure Technical Amnesia. It has been installed 0 times through Conduid.

The repository has 1 stars and 0 forks, with the last commit 7 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx @ecuabyte/cortex-mcp-server
Claude Code
claude mcp add cortex-ecuabyte -- npx -y @ecuabyte/cortex-mcp-server
npx
npx -y @ecuabyte/cortex-mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about cortex-server

Powered by Claude · Grounded in docs

I know everything about cortex-server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

🧠 Cortex


🚀 What is Cortex?

Cortex solves the "amnesia" problem for AI coding assistants. Your AI forgets everything when you close the window. Cortex doesn't.

It's a universal, persistent memory layer that lets your AI (Copilot, Claude, Cursor, etc.) remember:

  • 🏛️ Architecture Decisions: "We use Feature-Sliced Design"
  • 💡 Code Patterns: "All React components must use functional style"
  • 🔧 Configuration: "Production uses AWS RDS with specific flags"
  • 🚫 Exclusions: "Never touch the legacy payment module"

Unlike cloud-based solutions, Cortex stores everything locally on your machine (~/.cortex/memories.db). Your code context never leaves your computer.

💡 Stop teaching your AI the same things over and over.

✨ Key Features

1. 🧠 AI-Powered Project Scanner (Two-Pass)

Cortex doesn't just "read files". It performs a semantic analysis of your entire project:

  1. Pass 1 (Tree Scan): The AI analyzes your file structure to understand the project's topology.
  2. Pass 2 (Extraction): It selectively reads key files to extract "Facts", "Decisions", and "Patterns", storing them as structured memories.

2. 🌐 Universal MCP Support

Built on the Model Context Protocol (MCP), Cortex works with any modern AI tool:

  • VS Code / Cursor / Windsurf: Native integration.
  • Claude Desktop: Full memory access.
  • JetBrains / Neovim: Via MCP stdio.
  • Command Line Agents: Works with Goose, Zed, and others.
  • See full list of supported tools

3. 🔐 Privacy & Local-First

  • 100% Local Storage: Memories are stored in SQLite (~/.cortex/memories.db) on your machine.
  • Privacy Guard: (Coming Soon) Automatic PII redaction before context injection.
  • Project Isolation: Memories are automatically scoped to the specific git repository you are working on.

4. 🔎 Hybrid Search

Cortex uses a hybrid approach for finding context:

  • FTS5 (Full Text Search): Fast, exact matching for keywords/symbols.
  • Vectors (Semantic Search): (Optional) If you provide an OPENAI_API_KEY, Cortex enables semantic understanding to find related concepts even if keywords don't match.

⚡ One-Command Install (Recommended)

Cortex provides a universal installer that automatically configures Cursor, Windsurf, Claude Code, Gemini Code Assist, VS Code, and Zed in one go.

npx @ecuabyte/cortex-cli setup

This will:

  1. Detect your installed AI editors.
  2. Configure them to use the Cortex MCP Server.
  3. Scan your current project for initial context.

Manual Installation

If you prefer to configure manually or use a specific editor:

1. Install CLI Globally

npm install -g @ecuabyte/cortex-cli
# or
bun add -g @ecuabyte/cortex-cli

2. Configure Specific Editor

# For Cursor
cortex install --editor cursor

# For Claude Desktop
cortex install --editor claude-desktop

3. Manual Config Generation

If you need the raw JSON configuration:

npx -y @ecuabyte/cortex-mcp-server generate-config
goose configure mcp add cortex "npx -y @ecuabyte/cortex-mcp-server"

📦 Architecture

Cortex allows you to compose 5 core primitives:

// 1. STORE: Save items (facts, decisions, code)
await cortex.store({ content: "Use Zod for validation", type: "decision" });

// 2. ROUTE: Find context relevant to a generic query
const context = await cortex.route({ task: "Implement user login" });

// 3. GET: Retrieve specific memories
const memories = await cortex.get({ type: "code", tags: ["auth"] });

// 4. GUARD: (Beta) Sanitize output
const safe = await cortex.guard(content);

// 5. SCAN: Analyze project structure
await cortex.scan();

🗺️ Roadmap & Status

Feature Status Notes
Core Storage (SQLite) Production ready, local FTS5
Vector Search 🚧 Supported via OpenAI API, improving local embeddings
VS Code Extension Hierarchical Scanner, Native Models
MCP Server Universal support (Claude, Cursor, etc.)
Privacy Guard In development
Multi-Agent Sync 🔮 Future

🤝 Contributing

We welcome contributions! Please see CONTRIBUTING.md.

git clone https://github.com/EcuaByte-lat/Cortex.git
cd Cortex
bun install
bun run build

📄 License

MIT License © EcuaByte

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About cortex-server

How do I install cortex-server?

Run npx @ecuabyte/cortex-mcp-server, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is cortex-server safe to use with an AI agent?

Its trust score is 56 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is cortex-server still maintained?

The last commit was 7 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.