Presence

MCP文档知识

提供方 未标注

文档知识 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

Presence:跨会话记忆与Claude Code的验证门

一句话选型结论

按资料字段整理

Presence 属于文档知识类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Presence当前 未标注 未标注 未标注 无 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

14.7 KB
来自项目仓库与上游目录的原文,未做删改

presence

> New in v0.8.0: opt-in webhook notifier for confidence-gate verdicts, off by default and hard-disabled under zerotrust. See docs/recipes.md.

Every Claude Code session starts cold. presence makes the next one start where the last one left off.

A Claude Code plugin with read-only projections (MCP server, AGENTS.md adapter) so MCP-aware clients (Cursor, Claude Desktop, Continue) and AGENTS.md-aware tools (Codex, Gemini CLI, Windsurf, GitHub Copilot) can also read its accumulated context. Turns every session into part of a continuum.

presence adds four things to Claude Code, globally, with one install and zero per-project setup:

  1. Living project model. Claude builds and reuses notes about each repo it touches. No more re-deriving the same architecture every session.
  2. Outcome telemetry. Tracks what Claude committed, then watches for reverts, amends, and PR closes. Future sessions see "your last 3 changes here were reverted within 24h" instead of repeating the same mistake.
  3. Event digest. File changes, test failures, and build results that happened between turns are surfaced at the next prompt instead of needing to be polled.
  4. Calibrated confidence. The Stop hook checks whether success claims ("fixed", "done", "works") are backed by actual verification (tests run, build green) since the change. Warns when they're not. Optional hard gate on git commit/push.

State lives in ~/.claude/presence/, fully local, never uploaded.

Install (30 seconds)```bash

curl -fsSL https://raw.githubusercontent.com/sara-star-quant/presence/main/install.sh | bash


> No Python 3.12+? Append `-s -- --bootstrap` to auto-install it via uv (one call to astral.sh). The plain command above makes zero outbound calls.

That's the whole thing. Idempotent installer, makes no outbound network calls beyond fetching itself, applies globally to every Claude Code project. Restart Claude Code and run `/presence-status` to confirm. For options (`--bootstrap` to auto-install Python, `--verify`, `--build-ext` for the native fast path), see Quickstart below.

## By the numbers

| Metric | Default (stdlib) | With `--build-ext` | Method |
|---|---|---|---|
| Cold hook startup | 82 ms median | **8.9 ms median** | n=50 / n=30, `bench/cold_startup.py` |
| SessionStart populated | 112 ms median | **9.1 ms median** | 10 KB model + 100 events + 50 claims |
| Aggregate session (77 fires) | 6.4 s | **770 ms** | n=10 / n=5, `bench/aggregate_session.py` |
| Install + first /presence-status | 245 ms total | 245 ms total | n=25, `bench/install_to_working.py` |
| Tests | 291 passing | | Python 3.12 + 3.13 + 3.14 across Linux + macOS |
| Runtime deps (default) | 0 (stdlib only) | | one optional: `cryptography` for Zero-Trust at-rest encryption |
| Optional with `--build-ext` | | Rust toolchain at install time | binary then runs without Rust |
| Surface area | 4 presets, 6 hooks, 6 slash commands, 3 skills, 1 subagent, 1 MCP server, 1 cross-tool adapter, 3 redaction profiles | | redaction profiles opt-in for regulated workloads |
| Network egress | 0 in default presets | | opt-in `gh` PR-status call; opt-in `--bootstrap` / `--download-ext`; all disabled by default |
| Platforms | macOS arm64 + Linux x86_64 (CI) | | Windows: install in WSL2 |

The `--build-ext` column reflects optional native acceleration via the Rust daemon client (`./install.sh --build-ext` to compile locally, or `--download-ext` to fetch a pre-built binary from the latest release). Without it, hooks run on the stdlib-only path. See `bench/HISTORY.md` for the full version-by-version benchmark history.

All measurements: macOS arm64, Python 3.14.4. Reproduce locally with `python3 bench/.py --runs N`. See `bench/README.md` for the full convention.

> **Recent changes**: see `CHANGELOG.md` for the full per-version diff.
> v0.8.0 ships an opt-in webhook notifier for confidence-gate verdicts, gated by the same `network.egress_allowed` zerotrust switch as the release-freshness check.
> v0.5.0 ships composable redaction profiles for jurisdiction-aware sensitive data. Opt-in via `redact.profiles` in settings: `pii-eu`, `pii-us`, `pci-dss` (PAN matches gated by Luhn). New `docs/compliance.md` says exactly what presence does and does not do for regulated workloads. No certification framing: profile names describe data classes, not compliance frameworks.
> v0.4.2 ships the cross-tool AGENTS.md adapter. Set `PRESENCE_HOST=agents-md` and presence refreshes `/AGENTS.md` on every Claude Code SessionStart, picked up automatically by Codex, Cursor, Gemini CLI, Windsurf, GitHub Copilot, and others reading the open AGENTS.md standard. See `docs/multi-host.md`.
> v0.4.1 shipped the MCP server: any MCP-aware client (Claude Desktop, Cursor, Continue, custom agents) can read presence's living model + outcome telemetry over JSON-RPC stdio. See `docs/mcp.md`.
> v0.4.0 shipped the Rust daemon client + warm Python daemon + adapter seam. Optional via `--build-ext` / `--download-ext`. Cuts hot-path latency from 82 ms to 8.9 ms (-89%).
> v0.3.x cut cold-hook latency by ~27% and fixed a latent v0.2 bug where Zero-Trust users had their event digest silently emptied.
> v0.2.0 shipped the Zero-Trust preset: AES-GCM at rest, tamper-evident audit log, fail-closed SessionStart integrity. See `docs/zerotrust.md`.

## Quickstart

If this is your first Claude Code plugin: just run these two commands.

### 1. Install```bash
curl -fsSL https://raw.githubusercontent.com/sara-star-quant/presence/main/install.sh | bash

The installer is idempotent. It checks for Python 3.12+, symlinks the plugin into ~/.claude/plugins/presence, creates the state directory at ~/.claude/presence/ with 0700 perms, generates MANIFEST.lock, and pre-compiles lib/ to bytecode.

If you don't have Python 3.12+, the installer prints a warning and continues; presence is installed but stays inactive until a 3.12+ Python is on PATH. This is intentional so you can install on a machine that will get Python later (or run --bootstrap). To auto-install Python 3.13 via uv (single binary, no sudo, ~5 MB), pass --bootstrap:```bash
curl -fsSL https://raw.githubusercontent.com/sara-star-quant/presence/main/install.sh | bash -s -- --bootstrap


`--bootstrap` is opt-in because it makes one network call to `astral.sh`. The default install path makes no outbound calls.

### 2. Verify it works```bash
~/.claude/plugins/presence/install.sh --verify

Checks the symlink, plugin registration in settings.json, perms, Python, the MANIFEST.lock integrity, and synthetically fires all 6 hooks against the real lib/ tree. Exit 0 means ready. FAIL lines tell you exactly what is missing. For machine-readable output: --verify --json.

3. Use it

Restart Claude Code (or open a new session) in any repo and run /presence-status.

Other install methods

Via the Claude Code plugin marketplace flow

The repo ships its own marketplace.json so it can be added directly:```
/plugin marketplace add github.com/sara-star-quant/presence
/plugin install presence


### Via git clone```bash
git clone https://github.com/sara-star-quant/presence ~/code/presence
~/code/presence/install.sh

For the Zero-Trust preset's at-rest encryption (opt-in), also install the cryptography library into the same Python presence uses. On modern macOS / Linux this matters because Homebrew and most distros mark the system Python as PEP 668 externally-managed; a bare pip install exits with error: externally-managed-environment.

Pick the path that matches how you got Python:```bash

A. You used --bootstrap (presence has its own uv-managed Python).

pip works directly there, no PEP 668 wall.

"$(cat ~/.claude/presence/.python_bin)" -m pip install cryptography

B. You're on Homebrew / a system Python and want to override PEP 668

(installs into your user site, not system; safe in practice).

python3 -m pip install --user --break-system-packages cryptography

C. You want isolation (cleanest): create a venv and pin presence at it.

python3 -m venv ~/.claude/presence-venv
~/.claude/presence-venv/bin/pip install cryptography
echo "$HOME/.claude/presence-venv/bin/python3" > ~/.claude/presence/.python_bin


If unsure which Python presence is using, run `/presence-doctor` and look at the `pinned python` / `python` lines, then use that interpreter's `-m pip install cryptography`.

Other presets and the rest of the Zero-Trust controls (integrity check, redaction, gates, audit log) are stdlib-only.

## Update

For installs done via curl or git clone:```bash
~/.claude/plugins/presence/install.sh --update

--update does git fetch + git pull --ff-only + a re-run of the installer. It refuses to proceed if the working tree has uncommitted changes (so it never clobbers WIP). For installs done via the /plugin flow, use Claude Code's native plugin update mechanism.

Get notified of new releases (opt-in)

/presence-doctor can surface the latest released tag against your installed version. Off by default; enable by adding the following to ~/.claude/presence/settings.json:```json
{ "update_check": { "enabled": true } }


The next SessionStart pre-warms a 24 h cache (one anonymous HTTPS GET to `api.github.com`); the doctor then renders one line, e.g. `latest       : v0.6.0 (you have v0.5.4) [checked 12h ago]`. Forced off under the `zerotrust` preset (no network egress under that posture). Run `/presence-doctor --refresh` to bypass the TTL when verifying a fresh tag.

## Verify install

The fastest check is `./install.sh --verify` from the previous section. From inside Claude Code you can also run:```
/presence-status

You should see your active preset, the project ID for the current repo, and the size of the model + telemetry stores. For a focused Zero-Trust checklist:```
/presence-status --zerotrust


For a full diagnostic:```
/presence-doctor

To auto-correct recoverable issues (perm drift, missing manifest, stale .integrity-blocked marker):```bash
PYTHONPATH=~/.claude/plugins/presence/lib python3 ~/.claude/plugins/presence/lib/doctor.py --fix


## Presets

`presence` ships with four preset bundles. Switch any time:```
/presence-preset use solo-dev
/presence-preset use team-oss
/presence-preset use enterprise-strict
/presence-preset use zerotrust
Preset Model Telemetry Commit gate Stop gate At rest
solo-dev (default) on, terse on, no PR check off (advisory only via Stop) silent (logged, surfaced next session) plain
team-oss on, verbose on, optional PR check warn (advisory text injected) silent plain
enterprise-strict on, verbose, audit on, audit log block (refuses commit) block (re-prompts on unverified success) plain
zerotrust on, encrypted, audit on, encrypted, audit, no PR check block block AES-GCM + keychain

Custom presets: drop a .json in ~/.claude/presence/presets/ and switch to it.

See docs/zerotrust.md for the Zero-Trust profile in detail and CHANGELOG.md for the per-version diff.

Uninstall```

/plugin uninstall presence


Or, for local install:```bash
~/.claude/plugins/presence/install.sh --uninstall

State at ~/.claude/presence/ is preserved by default. Pass --purge to also remove state. Under the Zero-Trust preset, also use /presence-reset --crypto to rotate the keychain key and wipe encrypted state.

Privacy

  • All state is local. Nothing is ever uploaded.
  • No analytics, no telemetry-to-vendor, no remote calls.
  • The outcome-check skill makes one optional gh call to read PR status if gh is on $PATH and authenticated; this hits GitHub's API directly, not any third party. Disable in preset.
  • Under zerotrust, even that optional call is disabled.
  • Composable redaction profiles for jurisdiction-relevant patterns (EU PII, US PII, PCI-DSS) ship in presets/redaction/. See docs/compliance.md for the honest scope (presence has no formal certification).

Architecture

See docs/architecture.md for the full design: what each hook does, how state is laid out, the XML context schema, and how to write a custom preset.

Documentation

Start at docs/index.md for a map. Highlights:

  • docs/architecture.md - how the pieces fit together
  • docs/security.md - threat model (T1 through T12)
  • docs/zerotrust.md - the opt-in Zero-Trust profile
  • docs/compliance.md - what presence does / does not do for regulated workloads (no certification framing)
  • docs/glossary.md - definitions for project-specific terms
  • docs/recipes.md - common preset customizations
  • docs/roadmap.md - what we've deferred and why

Reporting bugs

Open a GitHub issue using the bug template. For security findings, do not file a public issue - follow the private disclosure process in SECURITY.md.

Disclaimer

presence is provided as is under the Apache License 2.0, without warranty of any kind, express or implied. The authors and copyright holders (Sara Star Quant LLC) and any contributors are not responsible for any damage, data loss, security incident, regression, lost productivity, or other adverse outcome arising from the installation or use of this plugin.

This project is not advice of any kind:

  • Not legal advice. The security model documented in docs/security.md and docs/zerotrust.md is informational. It is not a compliance attestation, certification, or guarantee under any regulatory framework (GDPR, HIPAA, SOC 2, ISO 27001, etc.). If you operate in a regulated environment, consult qualified counsel before relying on this plugin's properties.
  • Not security advice. The Zero-Trust preset reduces attack surface and adds layered controls (encryption at rest, audit log, fail-closed integrity, hard commit gates) but is not a substitute for proper threat modeling, penetration testing, or operational security review in your specific environment.
  • Not engineering advice. The calibrated-confidence gate and the living project model are useful nudges, not proofs of correctness. They reduce one common failure mode (asserting completion without verification); they do not replace tests, code review, or your own judgment.

By installing or using presence, you accept full responsibility for:

  • Reviewing the source before running it on your system or in any session that touches sensitive data.
  • Verifying that the documented properties (no network egress, local-only state, redaction patterns, encryption format, etc.) actually match what your environment requires.
  • Any downstream consequences of decisions made or claims accepted while presence was active in your sessions, including but not limited to: code committed, code reverted, settings changed, and inferences drawn from the project model or telemetry digest.

The full legal terms are in LICENSE. This README's Disclaimer section is an informational summary of the spirit of those terms; in any conflict, the LICENSE controls.

License

Apache-2.0, see LICENSE.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Presence 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Presence 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Presence 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Presence 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Presence 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Presence 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。