prism-coder MCP工具
prism-coder MCP工具 是 AI Skill Hub 本期精选MCP工具之一。综合评分 8.2 分，整体质量较高。我们强烈推荐将其纳入你的 AI 工具库，帮助提升工作效率。
📚 深度解析
通过安装 prism-coder MCP工具，你的 AI 助手将获得额外的工具调用能力，可以用自然语言直接操控该工具的功能，无需学习复杂的命令行语法。MCP 工具的核心价值在于"一次配置，永久增强"——配置完成后，每次与 AI 对话时都可以无缝调用这些工具。
在技术实现上，MCP 工具通过标准的 JSON-RPC 协议与 AI 客户端通信，工具的功能以"工具列表"的形式暴露给 AI 模型，AI 可以按需调用。prism-coder MCP工具 提供了结构化的工具调用接口，使 AI 模型能够精确地理解和使用每个功能点，显著降低 AI 在工具使用上的错误率。
与传统的 API 集成相比，MCP 工具的优势在于无需编写代码——用户只需在配置文件中添加几行 JSON，即可让 AI 获得全新能力。AI Skill Hub 将 prism-coder MCP工具 评为 AI 评分 8.2 分，属于同类工具中的优质选择。
📋 工具概览
prism-coder MCP工具 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。
📖 中文文档
prism-coder MCP工具 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。
- 通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
- 提供结构化工具调用接口，显著降低 AI 集成复杂度
- 支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
- 可与其他 MCP 工具组合叠加，构建完整 AI 工作站
- 轻量无侵入设计，不影响现有系统架构
- 在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
- 通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
- 将多个 MCP 工具组合使用，构建个人专属 AI 工作站
# 方式一：通过 Claude Code CLI 一键安装
claude skill install https://github.com/dcostenco/prism-coder
# 方式二：手动配置 claude_desktop_config.json
{
"mcpServers": {
"prism-coder-mcp--": {
"command": "npx",
"args": ["-y", "prism-coder"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
- 确认已安装 Node.js（v18 或以上版本）
- 打开 Claude Desktop 或 Claude Code 的 MCP 配置文件
- 按「交给 Agent 安装 → Claude Desktop」标签中的 JSON 配置填入 mcpServers 字段
- 保存配置文件并重启 Claude 客户端
- 重启后，在对话中即可使用本工具
# 安装后在 Claude 对话中直接使用 # 示例： 用户: 请帮我用 prism-coder MCP工具 执行以下任务... Claude: [自动调用 prism-coder MCP工具 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入："列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"prism-coder_mcp__": {
"command": "npx",
"args": ["-y", "prism-coder"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
Prism Coder
Give your AI agent memory that lasts — and see the cloud tokens it never had to spend. Persistent sessions, knowledge graphs, offline tool-routing, and an auditable savings meter. Fully local and free.
<p align="center"> <img src="docs/mind-palace-dashboard-v20.8.png" alt="Prism Mind Palace dashboard v20.8.0 — project state with handoff summary, pending TODOs, intent health, neural graph, and time-travel history" width="700" /> </p>
Prism Coder is an MCP server that gives Claude, Cursor, and other AI tools long-term memory that survives across sessions. It ships with the open-weight prism-coder model fleet (2B–27B) for fast, offline tool-routing — no cloud required. And it keeps score: every call served locally is metered, so prism savings shows the token volume that never reached your cloud model — measured honestly, in tokens.
No account needed. No API keys. Runs on your machine. A paid subscription adds cloud sync, higher model tiers, and team features through the Synalux portal.
---
What `prism connect` changes about host subagents
connect steers bounded work to prism_infer on your machine rather than to host-spawned agents. What it writes differs per host, and it does not disable subagents everywhere — Claude Code keeps them and is pointed at an economy model instead. Prism's local workers stay available over MCP in every case.
| Host | Setting written | Effect |
|---|---|---|
| Claude Code | env.CLAUDE_CODE_SUBAGENT_MODEL = "sonnet" in ~/.claude/settings.json | Subagents stay **enabled**, pinned to an economy model. Fan-out is discouraged by policy text, not by config |
| Gemini CLI | experimental.enableAgents = false in ~/.gemini/settings.json | Subagents **off**. Gemini exposes one boolean, so that is all there is to set |
| Codex | features.multi_agent = false in $CODEX_HOME/config.toml (default ~/.codex), plus a bounded fallback: 2 threads, depth 1, cheap subagent model, 900s cap | Subagents **off**, with a bounded profile underneath so a deliberate re-enable lands somewhere sane |
Two things worth knowing:
- experimental is Gemini's namespace, not ours. Prism is not enabling anything experimental — it writes false to a flag Gemini already defines at that path. Writing anywhere else would have no effect. - That namespace is by definition temporary. If Gemini promotes enableAgents out of experimental, Prism keeps writing the old path, Gemini reads the new one, and host subagents quietly turn back on. Nothing errors and the settings file still looks correct. If you see host subagents running while enableAgents reads false, check whether the key has moved before assuming connect failed to write it.
Both writes are idempotent in the sense that a host already configured this way is left untouched — but they are re-applied on every prism connect run, not only on --refresh. If you deliberately re-enable host subagents, the next connect will turn them off again. Keep them on by not re-running connect, or by re-enabling after each run.
---
<details> <summary>Release history (optional)</summary>
What's New in v20.18.0
What's New in v20.17.3
- A plugin install can no longer enable the prompt-routing hook. The package's maintenance paths (npm postinstall, server startup) now only refresh a hook that an explicit prism connect previously installed — a prism MCP registration in host config no longer counts as consent. First install of the hook happens through prism connect or not at all. - The Claude Code plugin launcher is fully deterministic. It runs the exact pinned server version with npm lifecycle scripts disabled, and the plugin now documents its security posture in plugins/prism/README.md.
What's New in v20.17.2
- Pasted logs can no longer falsely activate skills. Symptom-triggered routing now strips fenced blocks and routable skill-name mentions (including inside compound identifiers like container/pod names) from the routing view of a prompt, so quoting an agent log or a skill list doesn't load skills the text merely mentions. Skills named by ordinary words keep routing normally. - Symptom-routed skills now arrive whole. Startup budgets deliver the full rule text at every depth that fits; when a rule genuinely cannot fit, the display says exactly how much is missing and how to load the rest, instead of silently truncating. - Routing can no longer be silently disabled by one bad skill. Corrupt or hostile trigger tables — wrong value shapes, patterns named after object prototype properties — are skipped per entry instead of taking down all prompt routing (or, in one case, the vault export) for the session.
What's New in v20.17.1
- Fixes a broken CLI in 20.17.0 — a command-name collision made every prism CLI invocation exit with a commander error at startup (the MCP server was unaffected). The handoff-sync command is prism handoff …; prism sync remains cross-backend data synchronization. If you installed 20.17.0, update.
What's New in v20.17.0
What's New in v20.16.0
What's New in v20.12.1
- prism connect --refresh now converges every registration it owns, not just the top-level one — directory-scoped entries could otherwise keep launching an old build indefinitely. - prism update checks the installed package, not the CLI that happens to be running, so it can no longer report "current" while the install is stale. - The opt-in scheduled updater can actually start — the LaunchAgent now carries a PATH that includes node and npm.
What's New in v20.12.0
- Prism now tells you when it's out of date. Session startup shows a one-line update notice when a newer release exists — cache-backed, at most one registry check per day, silent offline. PRISM_NO_UPDATE_CHECK=1 opts out. - Hands-free updates, if you want them. prism autoupdate enable sets up a daily prism update --if-idle: it updates only the global npm package, defers while any Prism server is running, and never touches host configuration — that stays behind a visible prism connect.
What's New in v20.11.1
- Saving memory never gets refused. The save path used to reject session_save_ledger/save_handoff calls when its path-to-project heuristic disagreed with the project you declared — and the registry the heuristic trusted could contain junk from earlier auto-registration, so legitimate sessions ended unsaved. Your declaration now always wins; the disagreement is returned as an advisory warning, and auto-registration only accepts real repository roots. - Screenshots are evidence again. prism browser captures on macOS were silently upscaled to the size cap, so a screenshot no longer showed what actually rendered. Only genuinely oversized captures are resized now, and the cap no longer clips a standard 1920-wide viewport.
What's New in v20.10.0 – v20.11.0
- Skill routing now works mid-session. New prompts are matched on-device as the conversation moves — not just on turn one — and injected within each host's real context limits (Claude Code caps hook output at 10k chars; Codex truncates by default), with pointer-first delivery when a payload can't fit inline. - prism connect is a converge command. It self-updates first, re-execs, then reconciles MCP registration, skills, and hooks — no more "fresh config, stale code" machines. - Scoped skills route on prompts too, and startup output survives hosts that discard structured tool content.
What's New in v20.9.0 – v20.9.3
- Your skills follow your account. skill_save stores a skill at the scope you choose: this machine only (local, works offline and signed out), your account (user — every machine you sign into receives it), or a workspace (team — shared with members, admin-managed, optionally targeted to specific people). - Trim the catalog you don't use. skill_manage can release platform skills you never touch — freeing host skill-catalog budget — and restore them any time, losslessly. Deleting a scoped skill archives its final content locally first, so nothing is ever silently unrecoverable.
- Delivery that queues instead of failing. Concurrent sessions no longer starve skill sync on the local config store (WAL + busy-timeout) — a failure that previously reported only "partial" where nobody could see it. - Withheld rules still bind. When the context budget can't inline a skill's text, the manifest of withheld names now states that those skills still govern the work and names every way to load them before completion claims. - The budget the floor never spent. A long-standing accounting bug meant no unprotected skill ever inlined at any normal context level — the always-inlined protected floor was debiting the budget meant for everything else. Task-matched skills (like the completion-evidence checklist) now actually arrive.
What's New in v20.8.2
- Skill delivery now admits failure instead of hiding it. A filesystem permission edge case (a umask stripping the owner-execute bit) could leave skill sync writing nothing while reporting itself current — measured at nine days on a real machine. Broken managed directories are repaired in place, every directory is created umask-proof, and the repair path refuses symlinks via an O_NOFOLLOW descriptor. - A stale install tells you at startup. Prism now tracks the generation that actually reached disk separately from the one the database accepted; if they diverge, the startup banner says so in a warning placed where display truncation cannot cut it. A successful sync clears it automatically.
What's New in v20.7 – v20.8.0
- First run proves the memory instead of describing it — session_bootstrap seeds one demo memory and shows it recalled from disk, so the save→recall loop is felt in session 1. One-shot, contained in its own prism-demo project, removable with one call. - Dashboard fixed — a quoting typo (shipped 2026-05-29) killed the inline script at parse time, so every dashboard since rendered "Loading projects..." forever. Fixed, and the ES5 lint now node --checks the built inline script so an unparseable dashboard can never ship again. - Trusted Publishing — npm releases authenticate via GitHub OIDC. No stored token to expire or leak, and every release carries a signed provenance attestation — you can verify the tarball you install was built from this repo by CI (npm audit signatures). - TLS enforced for cloud sync — a remote http:// storage URL is upgraded to https:// instead of silently sending session content in the clear. - Codex plugin collision + enabled-state detection — prism connect skips its own registration only when a plugin actually provides prism-mcp (cache present and enabled), preventing both duplicate and missing servers. - Windows CI stabilized; registry/npm listings realigned and deduplicated.
What's New in v20.6.0
What's New in v20.5.3
What's New in v20.5.0 – v20.5.2
What's New in v20.4.0
What's New in v20.3.2
What's New in v20.3.1
What's New in v20.2.7
What's New in v20.3.0
What's New in v20.2.6
What's New in v20.2.4
What's New in v20.2.2
What's New in v20.2.1
What's New in v20.2.0
What's New in v20.1.0
What's New in v20.0.8
What's New in v20.0.5
What's New in v20.0.3
What's New in v20.0.0
CLA Requirement
External contributions now require signing the Individual CLA. The CLA check is merge-blocking on the main branch.
---
</details>
Install as a plugin
Prism also ships as a plugin, which registers the MCP server and the startup skill for you.
Claude Code — from the community marketplace:
/plugin marketplace add anthropics/claude-plugins-community
/plugin install prism-coder@claude-communityCodex — this repository is itself a plugin marketplace:
codex plugin marketplace add dcostenco/prism-coder
codex plugin add prism-coder@prismThe plugin registers prism-mcp via npx -y prism-mcp-server. If you already configured Prism by hand — prism connect writes an mcp_servers.prism-mcp entry — you have that server twice under one key. Install the plugin or run prism connect, not both.
Quickstart
The free tier needs no account, no API key, and no cloud. Install Prism, then register it with every supported MCP host already installed on your machine:
npm install --global prism-mcp-server
prism connectprism connect detects Claude Code, Claude Desktop (macOS/Windows/Linux), Cursor, Gemini CLI, and Codex. Use prism connect --all to target all five, --host <name> for one host, or --dry-run to preview the files that would change. Existing prism and prism-mcp entries are never overwritten by default. --refresh updates only an entry previously created by Prism; custom entries remain untouched. For Claude Code, both the default command and --refresh also remove the exact legacy project-scoped npx -y prism-mcp-server entry from the effective ancestor .mcp.json after the native user registration succeeds. No custom or near-match project entry is changed. Close the target MCP hosts before a non-dry-run registration so they cannot edit their configuration at the same time.
The same connection installs the local-first orchestration contract:
| Host | Managed containment |
|---|---|
| Codex | features.multi_agent=false; a 2-thread, depth-1 Terra/low fallback profile is retained for explicit re-enable |
| Gemini CLI | experimental.enableAgents=false |
| Claude Code | CLAUDE_CODE_SUBAGENT_MODEL=sonnet; managed instructions reserve it for last-resort fallback |
| Cursor | Canonical policy delivered through MCP initialize instructions |
| Claude Desktop | Canonical policy delivered through MCP initialize instructions |
All five receive PRISM_AGENT_POLICY=local-first in their managed Prism MCP entry. Routine tasks use the RAM-aware local worker; native/background fan-out is not the default workflow. session_task_route supplies a complexity hint; prism_infer remains the single owner of model and thinking selection and can choose 27B when its viability gates support it.
Set PRISM_STORAGE before running prism connect to preserve an explicit storage choice in the generated host entries. This does not change local-model routing; Synalux cloud storage separately requires an active cloud-memory entitlement.
Codex registration preserves unrelated ~/.codex/config.toml content, appends only the marked Prism MCP block, and updates only the documented local-first feature/agent keys. CODEX_HOME is respected when set and must already exist, matching Codex's own contract. Restart Codex CLI, the IDE extension, or the ChatGPT desktop app after connecting.
Restart the connected host and your agent now has memory backed by a local SQLite database (~/.prism-mcp/data.db). See IDE setup for manual configuration and host-specific paths.
Optional — local model fleet for offline tool-routing. Pull whichever fits your hardware:
ollama pull dcostenco/prism-coder:2b # 3.3 GB · on-device / lowest RAM · sees images (100% on our routing suite)
ollama pull dcostenco/prism-coder:4b # 3.5 GB · verifier · sees images (100%)
ollama pull dcostenco/prism-coder:9b # 6.7 GB · default router · sees images (95.7%, reasons before answering)
ollama pull dcostenco/prism-coder:27b # 16.8 GB · complex code / quality · text only (100%)Prism detects both the namespaced (dcostenco/prism-coder:9b) and bare (prism-coder:9b) Ollama tags automatically.
The 2b/4b/9b tiers carry a vision tower and accept screenshots through prism_infer({ images: [...] }) — pass absolute paths or base64. Image requests are refused rather than answered blind when no tier (or the Layer 1 safety classifier) can actually see the image, so a text-only model is never handed a prompt about a screenshot it never received. The 27b is text only.
---
Safer Configuration Updates Across Every Agent
prism connect now reads Claude, Cursor, Gemini, and Codex configuration through a single verified file snapshot, preventing another process from swapping a file between Prism's safety check and its read. Supported symlinked dotfiles still work, while dangling or planted symlinks fail loudly instead of being followed or overwritten. This release also carries the patched dependencies and cross-platform release checks introduced in v20.2.5.
Cloud fallback is now documented consistently as Gemini 3.6 Flash. Plan ceilings govern automatic prism_infer routing; direct use of any downloaded model through local Ollama remains free on every tier.
---
One Local-First Workflow Across Every Agent
prism connect now installs one orchestration contract for Claude Code, Claude Desktop, Cursor, Gemini CLI, and Codex. Bounded delegated work goes to session_task_route and the local prism_infer worker first; routine work must not create background host agents. Local workers can receive the active project's dashboard-configured quick, standard, or deep memory and select a RAM-safe 2B/4B/9B/27B model at call time. The router forwards complexity but does not choose the model; prism_infer owns the final decision using memory and context fit, installed models, live RAM, entitlements, and explicit caller overrides.
Codex and Gemini native agent fan-out are disabled during connect. Codex keeps a two-thread, one-level Terra/low fallback profile if the developer explicitly re-enables native agents later. Claude Code keeps native agents as a last-resort path but pins their model to Sonnet. Cursor and Claude Desktop do not expose a supported global subagent-policy file, so they receive the identical workflow through Prism's MCP server instructions. prism_infer safety boundaries and the host's final verification responsibility are unchanged.
创新的AI智能体记忆系统，融合认知科学理论与隐私保护。架构设计前沿，代码维护活跃，135星体现社区认可度，值得关注前沿AI开发者。
- 需要让 Claude / Cursor 操作本地工具的 AI 工程师
- 构建多智能体协作系统的 Agent 开发者
- 构建企业知识库 / RAG 检索应用的团队
- 跨境业务、多语言内容运营团队
- 做语音类 AI 产品的开发者
- 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
- 本地部署优先选 GGUF 量化模型，节省显存并保持响应速度
- Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
- API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
- MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
- 显存不足直接 OOM — 优先降低 context 或换更小的量化模型
- CLI：直接 npm install -g / pip install，命令行调用
- 本地部署：CPU 8GB 起，GPU 推荐 16GB+ 显存
- 云端托管：可放在 Vercel / Railway / Fly.io 等 PaaS 平台
⚡ 核心功能
- 通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
- 提供结构化工具调用接口，显著降低 AI 集成复杂度
- 支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
- 可与其他 MCP 工具组合叠加，构建完整 AI 工作站
- 轻量无侵入设计，不影响现有系统架构
- 需要让 Claude / Cursor 操作本地工具的 AI 工程师
- 构建多智能体协作系统的 Agent 开发者
- 构建企业知识库 / RAG 检索应用的团队
- 跨境业务、多语言内容运营团队
- 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
- 本地部署优先选 GGUF 量化模型，节省显存并保持响应速度
- Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
- API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
- MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
- 显存不足直接 OOM — 优先降低 context 或换更小的量化模型
👥 适合人群
🎯 使用场景
- 在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
- 通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
- 将多个 MCP 工具组合使用，构建个人专属 AI 工作站
⚖️ 优点与不足
- +标准化 MCP 协议，生态互联性强
- +与 Claude 官方生态无缝对接
- +即插即用，配置简单快捷
- −依赖 Claude 客户端，非 Claude 用户无法使用
- −MCP 协议仍在持续演进，接口可能变更
- −需要一定的配置步骤
该工具使用 AGPL-3.0 协议，商用场景请仔细阅读协议条款，必要时咨询法律意见。
AI Skill Hub 为第三方内容聚合平台，本页面信息基于公开数据整理，不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后，再部署至生产环境，并做好必要的安全评估。
⚠️ AGPL 3.0 — 最严格的 Copyleft，网络服务端使用也需开源，SaaS 使用受限。
🔗 相关工具推荐
❓ 常见问题 FAQ
经综合评估，prism-coder MCP工具 在MCP工具赛道中表现稳健，质量优秀。如果你已有明确的使用需求，可以直接上手体验；如果还在评估阶段，建议对比同类工具后再做决策。
| 原始名称 | prism-coder |
| 原始描述 | 开源MCP工具：The Mind Palace for AI Agents - HIPAA-hardened Cognitive Architecture with on-de。⭐135 · TypeScript |
| Topics | 智能体记忆认知架构HIPAA合规反盲从机制Hebbian学习 |
| GitHub | https://github.com/dcostenco/prism-coder |
| License | AGPL-3.0 |
| 语言 | TypeScript |
收录时间：2026-05-17 · 更新时间：2026-05-19 · License：AGPL-3.0 · AI Skill Hub 不对第三方内容的准确性作法律背书。