Hyperconsciousness

MCP文档知识

提供方 未标注

文档知识 未标注 未标注 社区 / 第三方 ClaudeCursorVS CodeCodex

由Louis Beaumont维护的开发者alpha版MCP服务器,通过限定范围、限时授权的加密追加式知识库提供搜索与检索功能。

一句话选型结论

按资料字段整理

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

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

工具与能力

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

能力标签

支持客户端

适用场景

记忆

安装与配置

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

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

知识库读写

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

内容整理

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

选择建议

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

值得选的地方

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

先想清楚的地方

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

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Hyperconsciousness当前 未标注 未标注 未标注 无 未标注
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

服务器档案

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

详细介绍

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

Hyperconsciousness (hc)

HC is an encrypted, append-only knowledge store for humans and agents. One
trusted node owns the store; other devices use its authenticated API. You
choose what an agent can access and for how long through scoped, expiring
grants. The node can run on your own machine or server.

The repository contains the Rust engine, CLI, MCP/HTTP server, and agent skills,
along with the optional local dashboard described below. Desktop, iOS, Android,
and mobile web apps are outside its scope. Private Companion and agent
orchestration are maintained separately.

HC is a developer alpha, so APIs and commands may change. No independent
security audit is claimed. Read the security limits before
using it for important data. The package is hyperconsciousness; run it with hc.

Read HC for humans for permissions, sharing, privacy and working with agents.
Agents can follow the usage skill.

Install

On macOS or Linux, install the latest published alpha with one command:```sh
curl -fsSL https://raw.githubusercontent.com/louis030195/hyperconsciousness/main/install.sh | sh


The installer verifies the release checksum and version before installing to
`~/.local/bin`. It does not create a brain or start a service. Follow its PATH
instruction if needed. GitHub releases
include Apple Silicon/Intel Mac, Linux x86-64/ARM64 and Windows x86-64 builds.
Linux builds require Ubuntu 24.04-compatible libraries; Mac builds are not
notarized. On Windows, extract the ZIP and run `hc.exe`.

Installer-managed copies update automatically from GitHub releases. On use, HC
checks in the background at most once every six hours. Running commands and MCP
sessions keep their current binary; the next launch uses the update. No dashboard
or persistent updater service starts. Windows ZIP users can opt in with
`hc update --enable`.

Use `hc update` to update now, `hc update --check` to check without installing,
or `hc update --disable` to turn it off. `HC_AUTO_UPDATE=0` skips automatic checks
for that process. Source/Cargo/npm builds and installs pinned with `HC_VERSION`
do not opt in automatically. See update behavior.

To connect to an existing organization, use its connection pack:```sh
hc setup company-hc.json --codex
hc login
hc status --remote

Setup installs the supplied instruction skills and registers HC with Codex.
Start a new Codex task after signing in. No Bun or provider API keys are needed.
See hosted access for other clients and access boundaries.
The company connection is separate from your personal brain.

Ingest chats and tools

The ingestion skill catalog includes Codex and Claude chats,
Slack, Google Workspace, GitHub, CRM, support, documents, meetings, analytics,
ads, billing, marketing and cloud operations. Install all recipes from a clone:```sh
python3 scripts/install-ingestion-skills.py --dest ~/.codex/skills


For Claude Code, use `--dest ~/.claude/skills`. These are portable agent
instructions using existing source access and an authorized HC writer. They
preserve source identity, freshness and retry receipts. Installing skills does
not connect accounts or start background ingestion; the catalog explains
selection, prerequisites and verification.

## Local dashboard

Use the optional HC Atlas dashboard to inspect storage,
file metadata, identity, and grants. You can navigate with the
keyboard or use its command menu. The UI guide and screenshots
show each view. With an existing authenticated HC reader configured, Records
also lets you search notes and imported source records, page through older
results, and open text previews.

The dashboard runs locally and requires an existing HC installation. Install it
separately from the CLI. Agents can start it when a visual inspection would help;
the agent startup notes explain how.

Check the prerequisites, then run these commands
from the repository root:```sh
cd dashboard
bun install --frozen-lockfile
bun run build
bun run start

Open , or reuse the dashboard there if it is already running.
Its server keeps running when you close the browser and stops when you end the
server process. Startup is manual: HC setup and CLI commands do not launch the
dashboard or open a browser. The dashboard inspects local metadata; it does not
provide hosted team access.

Install from source

Install Rust with rustup. This checkout pins Rust 1.88.0. Linux builds also
need native headers; on Ubuntu or Debian, install them with:```sh
sudo apt-get install build-essential pkg-config libssl-dev libdbus-1-dev


Build the source on macOS or Linux:```sh
git clone https://github.com/louis030195/hyperconsciousness.git
cd hyperconsciousness
cargo build --release --locked
mkdir -p "$HOME/.local/bin"
install -m 755 target/release/hc "$HOME/.local/bin/hc"
export PATH="$HOME/.local/bin:$PATH"
hc --help

On Windows, use cargo build --release --locked and run
target\release\hc.exe. Add the binary's directory to your PATH if needed.

The npm registry package is not the distribution source for this alpha. Use
the verified binaries above or build this checkout. npm packaging remains
tested for compatibility. See release automation.

Try an isolated store

Try HC in a new directory. Passing that directory to every command keeps this
example separate from an existing personal store:```sh
HC_STORE="$PWD/hc-demo"
hc start --dir "$HC_STORE"
hc write "A demo note" --tags demo --sensitivity normal --dir "$HC_STORE"
hc read --dir "$HC_STORE"
hc status --dir "$HC_STORE"


`hc read` displays local records without a full integrity check. It can display
a record whose signature was modified, and it can exit successfully after
withholding a record whose ciphertext was modified. Grant-scoped MCP reads
verify history and reject those mutations. To validate backups, use the
documented recovery verification and drill workflow.

## Give an agent limited access

For an agent running on the same trusted node, grant access to that node's
device identity. This example allows one day of read-only access to normal
notes tagged `demo`:```sh
HC_DEVICE="$(hc id --dir "$HC_STORE" | cut -d: -f2)"
hc grant "$HC_DEVICE" --kinds note --tags demo \
  --sensitivity normal --days 1 --dir "$HC_STORE"
hc grants --dir "$HC_STORE"

Copy the grant id into your MCP client configuration. Use absolute paths for
your HC executable and the store you chose:```json
{
"mcpServers": {
"hc": {
"command": "/absolute/path/to/hc",
"args": ["mcp", "--as", "<grant-id>", "--dir", "/absolute/path/to/hc-demo"]
}
}
}


MCP search supports an opt-in lexical relevance mode
for multiword queries. Literal search and chronological pagination remain the
default. Relevance mode requires no model or external service.

MCP exposes `overview`, `request_access`, `access_status`, `search`, `recent`,
`record`, `remember`, `remember_many`, `use_secret`, and `files`. A tool&#x27;s
presence does not grant permission to use it. Add `--write` only when the agent
needs capture access. Credential operations require a separate `USE` grant and
a signed device request. For company members, groups, multiple devices and
agents, use company gateway access. Company mode checks
current membership on every tool call and requires client-side request signing.```sh
hc revoke &lt;grant-id&gt; --dir &quot;$HC_STORE&quot;
hc audit --dir &quot;$HC_STORE&quot;

Grants limit what the server returns. A process with access to the owner's OS
account, files, or keys still has that access; grants do not sandbox it. Hosted
model providers can see the plaintext returned through their grants.

Small devices can query a trusted HC node through the same
MCP tools and hc find interface without replicating the brain. An opt-in default
reader preserves explicit local connections.

The HTTP server supports OAuth/DPoP, capture, and owner-approval APIs for
separate clients. It has no bundled application or approval UI. Existing
/mobile/... API names are preserved for compatibility; removed client pages
and assets return 404.

Keep company and personal data separate

Initialize company and personal stores independently. Give each its own runtime
identity and credentials, and select the store with an explicit --dir path.
Directory names alone provide no OS isolation. Run untrusted company agents
under a separate OS account or on a separate host.

Do not put API keys, recovery phrases, or private brain data in Git, skills,
container layers, or machine images. Credential adapters retain secret values;
HC stores opaque capability references and grants specific operations.

Documentation

  • Mission and scope and scope evals.
  • Operator skill: workspaces, grants, secrets,
    object-storage backup, and recovery commands.
  • Agent skill: scoped knowledge discovery.
  • Architecture and format specification.
  • Central-only migration: move an existing store to one trusted node.
  • Harness context plan: bounded evidence, capture provenance, skills, handoffs and independent adapters.
  • Threat model and constraints.
  • Failure cases and design decisions.
  • Historical roadmap, contributing, and
    security reporting.

Development```sh

cargo fmt --all -- --check
cargo clippy --locked --all-targets -- -D warnings
cargo test --locked
npm test
npm pack --dry-run
cargo package --locked
```

MIT licensed. See LICENSE.

常见问题

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

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

Hyperconsciousness 怎么在 Claude、Cursor、VS Code 里配置?

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

Hyperconsciousness 收费吗?

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

Hyperconsciousness 需要 API Key 吗?

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

Hyperconsciousness 支持哪些客户端?

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

Hyperconsciousness 能提供哪些能力?

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

热门专题

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

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