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 分