
Cortex MCP — Multi-Level Reasoning Server
io.github.j0hanz由 GitHub 帳號 j0hanz 發布v1.11.0更新於 Oct 24, 2026
Multi-level reasoning MCP server with configurable depth levels
概覽
本機 stdio 伺服器,為助理提供具狀態、可設定深度的多步推理工具,並保留可檢視的會話軌跡。
- 可以做什麼
- 以 basic、normal、high 或 expert 深度執行並延續有步數上限的推理會話,可逐步進行或批次完成
- 依步驟記錄結構化的觀察、假設與評估,回滾到較早步驟,或提前給出結論結束會話
- 以資源形式讀取作用中會話清單、單一會話的 JSON 檢視、完整 markdown 軌跡與單一思考
- 使用內建提示依指定深度開始推理、繼續會話、重試失敗任務或取得說明
- 適用情境
- 適合希望助理以明確、有上限的步驟推演難題,並留下可檢視或稽核軌跡,而非一次給出推理的情境。
- 執行需求
- 需要 Node.js 24 或更新版本,透過 npx 在本機執行此 npm 套件,以及支援 stdio 傳輸的 MCP 用戶端。Docker 僅用於容器映像,為選用。不需帳號、API 金鑰或標頭;選用環境變數可調整會話有效期、會話數量、權杖上限與軌跡遮蔽。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Cortex MCP — Multi-Level Reasoning Server,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
Cortex MCP
[Install in VS Code] [Install in VS Code Insiders] [Install in Visual Studio]
[Add to LM Studio] [Install in Cursor] [Install in Goose]
Multi-level reasoning MCP server with configurable depth levels, session-based state management, structured thought input, and real-time trace resources.
Overview
Cortex MCP is a stdio-only MCP server for stateful, depth-controlled reasoning. The runtime entrypoint in src/index.ts connects createServer() to StdioServerTransport, and the server surface in src/server.ts enables tools, prompts, completions, logging, and subscribable resources around a single session-based reasoning engine.
The live MCP surface confirmed by Inspector is 1 tool, 6 concrete resources, 4 resource templates, and 7 prompts. Sessions are stored in memory, exposed as MCP resources, and cleared on process restart.
Key Features
reasoning_thinksupports step-by-step sessions,run_to_completionbatches, rollback, early conclusion, and structuredobservation/hypothesis/evaluationinput.- Four depth levels are built into the engine:
basic,normal,high, andexpert, each with bounded thought ranges and token budgets. - Prompt helpers expose
reasoning.basic,reasoning.normal,reasoning.high,reasoning.expert,reasoning.continue,reasoning.retry, andget-help. - Resource endpoints expose internal docs plus live session lists, per-session JSON views, full markdown traces, and individual thought documents.
- Completions are wired for levels, session IDs, and thought names through
completable()and resource-template completion hooks.
Requirements
- Node.js
>=24for localnpxornpmusage. - An MCP client that supports
stdiotransport. - Optional: Docker if you want to build or run the container image defined by
Dockerfile.
Quick Start
Use this standard MCP client configuration:
Client Configuration
Install in VS Code
Add to .vscode/mcp.json:
Or install via CLI:
For more info, see VS Code MCP docs.
Install in VS Code Insiders
Add to .vscode/mcp.json:
Or install via CLI:
For more info, see VS Code Insiders MCP docs.
Install in Visual Studio
Add to mcp.json (VS integrated):
For more info, see Visual Studio MCP docs.
Install in Claude Desktop
Add to claude_desktop_config.json:
For more info, see Claude Desktop MCP docs.
Install in Claude Code
Add to Claude Code CLI:
Or install via CLI:
For more info, see Claude Code MCP docs.
Install in Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
For more info, see Windsurf MCP docs.
Install in Codex CLI
Add to ~/.codex/config.yaml or codex CLI:
For more info, see Codex CLI MCP docs.
Install in Augment
Add to VS Code settings.json:
Add to your VS Code
settings.jsonunderaugment.advanced.
For more info, see Augment MCP docs.
Use Cases
Start bounded reasoning at the right depth
Use reasoning.basic, reasoning.normal, reasoning.high, or reasoning.expert when the client wants a prompt-first entrypoint, or call reasoning_think directly with query, level, and the first thought. Each response returns the current session state plus a summary string that tells the client how to continue.
Relevant tool: reasoning_think
Related prompts: reasoning.basic, reasoning.normal, reasoning.high, reasoning.expert
Continue, retry, or batch an active session
Reuse sessionId to continue a prior trace, switch to runMode="run_to_completion" when you already have the remaining thought inputs, or use the continuation and retry prompts to generate the next call payload. The handler also supports rollbackToStep and isConclusion for revising or ending a trace early.
Relevant tool: reasoning_think
Related prompts: reasoning.continue, reasoning.retry
Inspect live traces without re-running the tool
Read reasoning://sessions for the active session list, reasoning://sessions/{sessionId} for the JSON detail view, reasoning://sessions/{sessionId}/trace for the markdown transcript, or reasoning://sessions/{sessionId}/thoughts/{thoughtName} for a single thought. This lets a client present progress or audit a session independently from the next tool call.
Relevant resources: reasoning://sessions, reasoning://sessions/{sessionId}, reasoning://sessions/{sessionId}/trace, reasoning://sessions/{sessionId}/thoughts/{thoughtName}
Architecture
Request Lifecycle
MCP Surface
Tools
reasoning_think
Stateful reasoning tool for creating and continuing multi-step sessions. It supports one-step interactive calls, run_to_completion batches, structured observation/hypothesis/evaluation input, rollback, and early conclusion while returning structured session state.
Data Flow
Resources
Prompts
MCP Capabilities
Tool Annotations
Structured Output
reasoning_thinkdeclaresoutputSchemaand returnsstructuredContent, with an embedded trace resource when the trace is small enough. Evidence:src/tools/reasoning-think.ts:498,src/lib/mcp.ts:97-114.
Configuration
[!NOTE] The source does not define any HTTP host/port configuration. The only other environment-related signal is
NODE_ENV=productionin the Docker image and--env-file=.envin the localdev:runscript.
Security
[!NOTE] No auth, OAuth, HTTP origin checks, or rate-limiting controls are implemented in the current source because the server only exposes stdio transport.
Development
Additional helper scripts for diagnostics, coverage, asset copying, and knip are defined in package.json.
Build and Release
.github/workflows/release.ymlbumpspackage.jsonandserver.json, then runsnpm run lint,npm run type-check,npm run test, andnpm run buildbefore tagging and creating a GitHub release.- The same workflow publishes the package to npm with Trusted Publishing, publishes to the MCP Registry with
mcp-publisher, and pushes a multi-arch Docker image toghcr.io. Dockerfileuses a multi-stage Node 24 Alpine build, prunes dev dependencies, and runs the released container as themcpuser.
Troubleshooting
- Sessions are in memory and expire after 30 minutes by default. If you receive
E_SESSION_NOT_FOUND, start a new session or increaseCORTEX_SESSION_TTL_MS. runMode="run_to_completion"requires enoughthoughtentries to cover the remaining steps. If you want the server to return after each step, keep the defaultstepmode.- For stdio transport, do not add custom stdout logging around the server process. This server routes logs through MCP logging and falls back to
stderron failures.
Credits
Contributing and License
- License: MIT
- Contributions are welcome via pull requests.
來源:README.md,提交 c1171fd
工具
0版本歷史
1- v1.11.0最新Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。