Solucortex Mcp

io.github.soluai-spa由 GitHub 帳號 soluai-spa 發布v1.1.2更新於 Oct 24, 2026

Living technical memory for AI agents: recall approved project context, record what was learned.

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具

概覽

AI 產生的概覽

SoluCortex MCP 為助理提供專案的「活技術記憶」:取回已核准的決策、慣例與風險,並記錄任務中學到的內容。

可以做什麼
  • 在任務開始時取回依相關度排序的專案脈絡
  • 對已存記憶做臨時語意搜尋
  • 在任務收尾或做出技術決策時記錄新記憶
  • 修正既有記憶,修改後會回到待核准狀態等待人工重新核准
  • 將記憶標記為過時或錯誤,交由人工複核
  • 列出專案記憶,用於快速檢視或稽核
適用情境
適合助理長期在同一程式庫或專案上工作、需要在每個任務開始前了解團隊已核准的決策、慣例、風險與架構,並在結束時寫回所學內容的情境。也適合希望由代理提出、由人工在面板中核准記憶的團隊。
執行需求
需要 SoluCortex 帳號與以 scx_ 開頭的專案 API 金鑰。遠端方式使用託管的 Streamable HTTP 端點,需 Authorization bearer 標頭,可選 X-Solucortex-Project 標頭;本機方式需要 uv、Python 3.10 以上或 Docker,並設定 SOLUCORTEX_API_KEY,可選 SOLUCORTEX_PROJECT_ID 與 SOLUCORTEX_URL。需要能連線至 SoluCortex API 的網路。
安裝前請注意
API 金鑰屬於機密,應放在用戶端設定的 env 區塊或本機 .env 中,切勿提交到版本庫。此伺服器會寫入共用的專案記憶庫,記錄的記憶會影響其他助理的檢索結果;修改會回到待核准狀態,刪除只能由人工執行。取回與語意搜尋會消耗 OpenAI 嵌入配額,限速為每分鐘 20 次請求。不要在記憶中存放真實密鑰,只記錄位置、類型與嚴重程度。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Solucortex Mcp,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.soluai-spa%2Fsolucortex-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "solucortex": {
      "type": "http",
      "url": "https://mcp.solucortex.ai/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

SoluCortex MCP

[PyPI] [CI] [Python] [License: MIT]

Official Model Context Protocol server for SoluCortex — living technical memory for AI agents.

Connect any MCP-compatible agent (Claude Code, Claude Desktop, Cursor, Codex, Cline, …) to your SoluCortex project so it can recall the decisions, conventions, risks and architecture that matter before it works, and remember what it learns when it's done.

Website: solucortex.ai · Setup guide: solucortex.ai/docs/mcp · Tools reference: solucortex.ai/docs/mcp-tools · PyPI: solucortex-mcp · MCP Registry: io.github.soluai-spa/solucortex-mcp

[SoluCortex MCP demo: recall approved context at task start, remember learnings at close]

Tools

ToolWhat it doesWhen to use
solucortex_recallBuilds living context for a task (ranked by semantic similarity + importance)At the start of a task, before touching code
solucortex_searchAd-hoc semantic search over the project's memoriesSpecific questions mid-task
solucortex_rememberRecords a memory (stored approved + traced as an authorized agent)At close, or on a relevant technical decision
solucortex_update_memoryCorrects an existing memory — the edit returns it to pending for human re-approval in the panelWhen a memory is right in spirit but wrong in detail
solucortex_flag_memoryFlags a memory as outdated/incorrect with a reason; a human resolves it in the panelWhen a memory should be reviewed, archived or deleted
solucortex_list_memoriesLists memories without semantic searchQuick inspection / audit

Governance by design: agents propose, humans govern. Agents can never change a memory's status, rewrite its metadata, or delete it — edits go back to pending and deletions only happen from the SoluCortex panel.

Requirements

  • A SoluCortex account and a project API key (prefix scx_) — get it from your SoluCortex dashboard.
  • One of: uv (recommended), Python ≥ 3.10, or Docker.

Configuration

stdio mode (default, local)

The server is configured entirely through environment variables:

VariableRequiredDescription
SOLUCORTEX_API_KEY✅Project API key (scx_…)
SOLUCORTEX_PROJECT_IDoptionalDefault project UUID; if omitted, the backend infers it from the API key
SOLUCORTEX_URLoptionalAPI base URL. Default https://solucortex.ai

HTTP mode (remote, multi-tenant)

Run with MCP_TRANSPORT=http (or --http) to serve Streamable HTTP on $PORT (default 8080) — the mode behind https://mcp.solucortex.ai. Credentials travel with each request and the environment is ignored:

HeaderRequiredDescription
Authorization: Bearer scx_…✅The caller's project API key (401 without it)
X-Solucortex-ProjectoptionalDefault project UUID; if omitted, the backend infers it from the API key

GET /health (and /healthz locally; Cloud Run's frontend intercepts /healthz) responds without auth. The MCP endpoint is /mcp, runs stateless, and shares nothing between requests/tenants.

Never commit your API key. Keep it in your MCP client config's env block or a local .env (see .env.example).

Install

Remote (recommended — nothing to install)

The hosted server at https://mcp.solucortex.ai/mcp speaks Streamable HTTP; your key travels with each request:

bash
claude mcp add --transport http solucortex https://mcp.solucortex.ai/mcp \  --header "Authorization: Bearer scx_xxx" \  --header "X-Solucortex-Project: your-project-uuid"

Or in any client with remote MCP support:

json
{  "mcpServers": {    "solucortex": {      "type": "http",      "url": "https://mcp.solucortex.ai/mcp",      "headers": {        "Authorization": "Bearer scx_xxx",        "X-Solucortex-Project": "your-project-uuid"      }    }  }}

Claude Code (local, stdio)

bash
claude mcp add solucortex \  -e SOLUCORTEX_API_KEY=scx_xxx \  -e SOLUCORTEX_PROJECT_ID=your-project-uuid \  -- uvx solucortex-mcp

Claude Desktop / Cursor / Cline (JSON config)

Add to the client's MCP config (claude_desktop_config.json, Cursor mcp.json, etc.):

json
{  "mcpServers": {    "solucortex": {      "command": "uvx",      "args": ["solucortex-mcp"],      "env": {        "SOLUCORTEX_API_KEY": "scx_xxx",        "SOLUCORTEX_PROJECT_ID": "your-project-uuid"      }    }  }}

From a local clone

bash
git clone https://github.com/soluai-spa/solucortex-mcpcd solucortex-mcpcp .env.example .env   # fill in your key./run.sh               # loads .env, then runs via uv# or, with SOLUCORTEX_* already exported: uv run solucortex-mcp

Docker

Prebuilt image on GHCR:

bash
docker run --rm -i \  -e SOLUCORTEX_API_KEY=scx_xxx \  ghcr.io/soluai-spa/solucortex-mcp:latest

Or build it yourself:

bash
docker build -t solucortex-mcp .docker run --rm -i \  -e SOLUCORTEX_API_KEY=scx_xxx \  -e SOLUCORTEX_PROJECT_ID=your-project-uuid \  solucortex-mcp

The server speaks MCP over stdio, so clients launch it as a subprocess (-i keeps stdin open).

Instructions for your agent (AGENTS.md)

Once connected, give your agent the methodology too: copy templates/AGENTS.md into the root of your repo (it works as AGENTS.md or CLAUDE.md). The MCP handshake already carries these instructions — the file lets you version them alongside your code, extend them with your own conventions, and optionally enable the commented Claude Code hook recipe for guaranteed recall.

Development

bash
uv syncuv run solucortex-mcp            # run (stdio)MCP_TRANSPORT=http uv run solucortex-mcp   # run (HTTP on :8080)uv run pytest                    # test suitenpx @modelcontextprotocol/inspector uv run solucortex-mcp   # interactive test

Notes

  • Memory type vocabulary: the canonical set is architecture, decision, risk, convention, bug_history, tech_debt, sensitive_module, learning, external_integration. Some backends accept an older set (technical_decision, historical_bug, current_state, task_closure). The server passes type through and surfaces HTTP 422 so you can retry with the other set.
  • Never store real secrets in a memory. Record location, type, severity and action taken instead.

License

MIT — see LICENSE.

來源:README.md,提交 b97a3af

工具

6

solucortex_recall

SoluCortex: recall task context

Build living context for a task (POST /context/build). Call this at the START of a task, before touching code: returns approved, active memories (decisions, conventions, risks, sensitive modules, architecture) ranked by semantic similarity + importance. Uses OpenAI embeddings (slower, 20 req/min).

輸入參數query必填project_id

solucortex_remember

SoluCortex: record a memory

Record a memory in SoluCortex (POST /memories). Call when closing a task or making a relevant technical decision. As an authorized agent (Bearer api_key), the memory is stored with status 'approved' and traced. Never store real secrets: if you find one, record location/type/severity and action taken, with a redacted reference.

輸入參數type必填title必填content必填importanceproject_id

solucortex_update_memory

SoluCortex: update a memory (requires human re-approval)

Correct an existing memory (PATCH /memories/{id}). Agents propose, humans govern: the edit is applied but the memory returns to PENDING until a human re-approves it. ALWAYS tell the user the change awaits their approval in the SoluCortex panel. Status changes are not possible here.

輸入參數typetitlecontentmemory_id必填importance

solucortex_flag_memory

SoluCortex: flag a memory for human review

Flag a memory as outdated/incorrect (POST /memories/{id}/flag). The memory is marked for human review in the SoluCortex panel; nothing is deleted or unpublished. ALWAYS tell the user a memory awaits their decision in the panel. Deletion is human-only by design.

輸入參數reason必填memory_id必填suggested_action

solucortex_list_memories

SoluCortex: list memories

List the project's memories without semantic search (GET /memories). Useful for quick inspection/audit or to confirm a just-created memory was stored. Does not consume OpenAI quota.

輸入參數limitproject_id

版本歷史

1
  1. v1.1.2最新Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分