bulhufas

MCP搜索检索

提供方 HugoluizMTB

搜索检索 stdio · 本地进程 API Key 社区 / 第三方 ClaudeZed
查看接入方式

A RAG-powered project management tool that extracts structured information (e.g., decisions, action items, blockers) from raw conversations and provides intelligent retrieval through semantic search.

一句话选型结论

按资料字段整理

bulhufas 属于搜索检索类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude、Zed,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

Local Deployment Project Management Semantic Search Go Conversation Analysis RAG Technology AI Assistant

支持客户端

适用场景

Local DeploymentProject ManagementSemantic Search

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
docker build -t bulhufas . docker run -d --name bulhufas -p 8420:8420 -v bulhufas-data:/data bulhufas

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 go,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
bulhufas当前 未标注 stdio · 本地进程 本地部署 有 2026-08-04
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方HugoluizMTB上游标注的维护方 HugoluizMTB
分类搜索检索本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · go本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-08-04上游最后核验时间

详细介绍

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

bulhufas

RAG-powered project management that captures what PM tools miss.


Why "bulhufas"?

Bulhufas is Brazilian Portuguese slang for "zilch", "diddly-squat", "bupkis" — absolutely nothing.

As in: "How much does Claude know about that decision your team made on WhatsApp last Thursday?" Bulhufas.

"What about that blocker someone mentioned in standup?" Bulhufas.

"And that architecture decision from two sprints ago?" You guessed it. Bulhufas.

Now it knows.


Teams make decisions in Slack, WhatsApp, and meetings — then none of it reaches the PM tool. bulhufas captures raw conversations, extracts structured project artifacts (decisions, action items, blockers, scope changes), and makes them searchable via semantic embeddings.

Single binary. No external dependencies. Embeddings run in-process.

Features

  • Conversation to Structure — Paste raw chat, get structured chunks: decisions, action items, blockers, requirements, scope changes
  • Agent Memory — Store working, episodic, semantic and procedural memories in isolated namespaces with provenance, confidence, importance and validity windows
  • Semantic Search — Find context by meaning, not keywords. "What did we decide about auth?" finds the right chunk even if "auth" isn't in the text
  • Compact Recall — Return a bounded context packet with memory IDs and source references so any LLM can recall only what it needs
  • CRUD on Knowledge — Update status, add context, archive outdated chunks. Your knowledge base stays current
  • Single Binary — One Go binary with embedded vector store (chromem-go) and embedding model (hugot/all-MiniLM-L6-v2). No Ollama, no Docker, no external processes
  • Self-Hostable — Deploy anywhere: Coolify, Railway, Hetzner, AWS, GCP. Runs on a 2GB VPS

How It Works```

You paste a conversation into your AI assistant
|
The LLM extracts structured chunks with metadata
|
bulhufas stores chunks + generates embeddings in-process (hugot)
|
Later: "what's pending from last week?" -> semantic search returns relevant chunks


### What Gets Captured

| Chunk Type | Example |
|-----------|---------|
| `decision` | "We chose WebSockets over polling for real-time updates" |
| `action_item` | "Hugo will create read-only DB credentials by Friday" |
| `blocker` | "Can't deploy until the SSL cert is renewed" |
| `requirement` | "Client needs CSV export for the finance report" |
| `scope_change` | "Auth module expanded to include SSO" |
| `context` | "The legacy API returns XML, not JSON" |
| `research_finding` | "pgvector outperforms pinecone for our dataset size" |
| `status_update` | "Payment integration is live in staging" |

## Installation

### 1. Build from source```bash
# Requires Go 1.22+ with CGO enabled
git clone https://github.com/HugoluizMTB/bulhufas.git
cd bulhufas
make build

2. Add to Claude Code```bash

claude mcp add --transport stdio --scope user bulhufas -- /absolute/path/to/bulhufas/bin/bulhufas --mcp


> Replace `/absolute/path/to` with the actual path where you cloned the repo.
> Use `--scope user` to make it available across all your projects.
> Use `--scope project` to restrict it to the current project only.

### 3. Restart Claude Code and verify

Run `/mcp` inside Claude Code. You should see `bulhufas` connected with 10 tools:

| Tool | Description |
|------|-------------|
| `save_conversation` | Save a conversation with extracted structured chunks |
| `remember` | Save one scoped memory record with provenance and lifecycle metadata |
| `search` | Semantic search across all stored chunks |
| `recall` | Retrieve a namespace-isolated, token-conscious context packet |
| `observe_turn` | Automatically learn a meaningful turn as episodic memory |
| `list_chunks` | List chunks with optional type/status filters |
| `update_status` | Update chunk status by ID |
| `delete_chunk` | Delete a chunk by ID |
| `list_actions` | List all pending action items |
| `consolidate_memory` | Preview or run episodic-to-semantic/procedural consolidation |

On first run, the embedding model (all-MiniLM-L6-v2, ~80MB) is downloaded automatically to `./data/models/`.

### Run as HTTP Server (optional)```bash
./bin/bulhufas

Starts an HTTP API on port 8420. Use --mcp flag for MCP stdio mode instead.

Automatic gateway for any OpenAI-compatible LLM

To capture turns automatically in Claude Code without relying on the model calling observe_turn, register the Stop hook in integrations/claude-code-hook.mjs. See docs/claude-code-sessions.md.

For providers that do not support MCP, run the dependency-free memory proxy:```bash
LLM_UPSTREAM_URL=https://api.openai.com \
LLM_UPSTREAM_API_KEY="$OPENAI_API_KEY" \
BULHUFAS_NAMESPACE=project:bulhufas \
make proxy


Point the client at `http://127.0.0.1:8421/v1`. The proxy recalls scoped memory before each chat completion and captures substantive turns after the response. It works with OpenAI-compatible endpoints such as Ollama, vLLM and LM Studio; see integrations/README.md.

With Docker Compose, use `docker compose --profile proxy up -d` after setting `LLM_UPSTREAM_URL`, `LLM_UPSTREAM_API_KEY` and `BULHUFAS_NAMESPACE` in the environment.

### Environment Variables

| Variable | Default | Description |
|----------|---------|-------------|
| `PORT` | `8420` | Server port |
| `DATA_DIR` | `./data` | Persistent storage directory (SQLite db, model files, vector index) |
| `MEMORY_LLM_BASE_URL` | unset | OpenAI-compatible `/v1` endpoint used for automatic consolidation |
| `MEMORY_LLM_API_KEY` | unset | Optional API key for the consolidation provider |
| `MEMORY_LLM_MODEL` | `gpt-4o-mini` | Model used by the background memory manager |
| `MEMORY_CONSOLIDATION_INTERVAL` | `15m` | Interval for promoting episodic memories when `MEMORY_LLM_BASE_URL` is set |
| `MEMORY_NAMESPACE` | `default` | Namespace processed by the automatic consolidator |
| `BULHUFAS_API_KEY` | unset | Optional API key required by HTTP API clients |
| `BULHUFAS_ALLOWED_NAMESPACE` | unset | Optional hard namespace boundary for this server instance |
| `BULHUFAS_TLS_CERT_FILE` | unset | Certificate path; enables HTTPS together with key file |
| `BULHUFAS_TLS_KEY_FILE` | unset | Private key path for HTTPS |

## API

### Save a conversation with chunks```bash
curl -X POST http://localhost:8420/api/conversations \
  -H "Content-Type: application/json" \
  -d '{
    "source": "whatsapp",
    "summary": "Discussion about database access",
    "participants": ["renan", "hugo"],
    "chunks": [
      {
        "content": "Renan needs read-only access to PostgreSQL",
        "type": "decision",
        "tags": ["infra", "postgres"],
        "people": ["renan"],
        "status": "pending",
        "action_item": "Create read-only credentials"
      }
    ]
  }'

Semantic search```bash

curl -X POST http://localhost:8420/api/search \
-H "Content-Type: application/json" \
-d '{"text": "database access", "limit": 5}'


### Save and recall agent memory```bash
curl -X POST http://localhost:8420/api/memories \
  -H "Content-Type: application/json" \
  -d '{
    "content": "The payments service uses idempotency keys for retries",
    "memory_kind": "procedural",
    "namespace": "project:bulhufas",
    "source": "architecture-review",
    "source_ref": "meeting:2026-08-01",
    "confidence": 0.95,
    "importance": 0.8,
    "tags": ["payments", "reliability"]
  }'

curl -X POST http://localhost:8420/api/recall \
  -H "Content-Type: application/json" \
  -d '{
    "text": "How should payment retries work?",
    "namespace": "project:bulhufas",
    "memory_kinds": ["semantic", "procedural"],
    "limit": 5,
    "max_chars": 3000
  }'

recall returns both structured results and a bounded context string. Namespaces, project/tenant/session IDs and memory kinds are hard filters, so unrelated agent contexts are not concatenated accidentally.

When MEMORY_LLM_BASE_URL is configured, a background manager periodically consolidates episodic memories into conservative semantic/procedural records. It can also be triggered or previewed explicitly:```bash
curl -X POST http://localhost:8420/api/consolidate \
-H "Content-Type: application/json" \
-d '{"namespace":"project:bulhufas","limit":32,"dry_run":true}'


### Ambient learning

In normal agent usage, the client can call `recall` at task start and `observe_turn` after substantive turns. These are internal tool calls: you do not need to type “remember this” for ordinary learning. The explicit `remember`, update and delete tools remain available for corrections, promotions, forgetting and exact control. For chat gateways that can forward every message automatically, `POST /api/turns` provides the same capture path without relying on the model to initiate the call.

### List chunks with filters```bash
curl "http://localhost:8420/api/chunks?type=blocker&status=pending"

List pending action items```bash

curl http://localhost:8420/api/actions


### Update chunk status```bash
curl -X PATCH http://localhost:8420/api/chunks/{id}/status \
  -H "Content-Type: application/json" \
  -d '{"status": "resolved"}'

Delete a chunk```bash

curl -X DELETE http://localhost:8420/api/chunks/{id}


### Health check```bash
curl http://localhost:8420/healthz

Metrics are available at GET /metrics in Prometheus text format. Set BULHUFAS_API_KEY to protect API routes; place the service behind a TLS reverse proxy or set both TLS file variables directly.

Architecture```

cmd/server/ -> entrypoint, wires everything together
internal/
domain/ -> core types: Conversation, Chunk, WorkItem, Relation
mcp/ -> HTTP server, handlers, request/response logic
store/ -> persistence interface + SQLite implementation
vectorstore/ -> embedded vector search via chromem-go
embedder/ -> in-process embeddings via hugot (all-MiniLM-L6-v2)
scripts/ -> test scripts
macos/BulhufasMac/ -> native macOS app: Dynamic Island + menu bar (GPL-3.0)


All external dependencies are behind interfaces. Swap SQLite for Postgres, or chromem-go for pgvector — without touching business logic.

### Stack

| Component | Library | Runs in-process? |
|-----------|---------|-----------------|
| Embedding | hugot + all-MiniLM-L6-v2 (384 dim) | Yes |
| Vector store | chromem-go | Yes |
| Database | SQLite (mattn/go-sqlite3) | Yes |
| HTTP server | Go stdlib net/http | Yes |
| macOS UI | SwiftUI + AppKit NSPanel | Native app |

No Ollama. No Docker. No external databases. One binary.

The local backend is deliberately the first tier of a larger memory design. SQLite/chromem is the default offline store; the native macOS app talks to it over the local HTTP API, while the optional Postgres adapter can use pgvector HNSW plus PostgreSQL full-text search. Vector quantization such as TurboQuant is an optional index optimization and must be validated against recall before enabling it.

The optional PostgreSQL/pgvector adapter is documented in docs/pgvector.md. The deeper LLM and memory research is summarized in docs/research-landscape.md.

## Self-Hosting

### Binary```bash
CGO_ENABLED=1 GOOS=linux go build -o bulhufas ./cmd/server
scp bulhufas your-server:/opt/bulhufas/
ssh your-server '/opt/bulhufas/bulhufas'

Docker```bash

docker build -t bulhufas .
docker run -d --name bulhufas -p 8420:8420 -v bulhufas-data:/data bulhufas


### Docker Compose```bash
git clone https://github.com/HugoluizMTB/bulhufas.git
cd bulhufas
docker compose up -d

Works with Coolify, Railway, Hetzner, AWS, GCP, Oracle Cloud — anything that runs Docker.

Native macOS app

The macOS app has no regular window. It lives in two places: a Dynamic Island that hangs from the notch, and a menu bar panel.bash make macos-open

Dynamic Island. Closed, it is exactly the size of the notch and therefore invisible. Hovering opens it; clicking pins it open. When new memories arrive it briefly widens into a sneak peek. The open state shows the active Claude Code session and either recent memories or the session list. On displays without a notch the same shape hangs from the top edge.

Menu bar. A panel with the memory count, capture activity over time, and a breakdown of what was captured by chunk type.

Claude Code sessions. The app lists sessions by reading file metadata from $CLAUDE_CONFIG_DIR/projects, ~/.claude/projects and ~/.claude-pessoal/projects — modification times and file names only. Transcript contents are never opened and no credentials are read. Memory capture itself still happens through the MCP server; see docs/claude-code-sessions.md.

The app defaults to http://127.0.0.1:8420. Set BULHUFAS_URL before launching it to use another local or remote HTTP endpoint. The Homebrew formula is documented in docs/homebrew.md.

> License note: the macOS app in macos/ is GPL-3.0, because it contains code derived from Atoll and, through it, boring.notch. The Go server and everything else in this repository stay Apache-2.0 — they are separate programs communicating over a local HTTP API. See macos/NOTICE.

Roadmap

  • [x] Core domain types and interfaces
  • [x] HTTP API with save/search/update/delete
  • [x] SQLite store implementation
  • [x] In-process embeddings via hugot (all-MiniLM-L6-v2)
  • [x] chromem-go vector store
  • [x] Semantic search with SQLite enrichment
  • [x] Action items endpoint
  • [x] MCP server protocol (stdio transport via mcp-go)
  • [x] Docker image
  • [x] Native macOS app: Dynamic Island + menu bar
  • [x] Claude Code session list from local transcript metadata
  • [ ] Slack plugin
  • [ ] Remote MCP via SSE transport

Contributing

See CONTRIBUTING.md for setup instructions, code style, and PR process.

License

Apache License 2.0 — use it freely, even commercially. Patent protection included.


Created by @HugoluizMTB

常见问题

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

在客户端按下面的安装命令接入:docker build -t bulhufas . docker run -d --name bulhufas -p 8420:8420 -v bulhufas-data:/data bulhufas。装完在客户端配置里引用同一个包或端点。

bulhufas 怎么在 Claude、Zed 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

bulhufas 收费吗?

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

bulhufas 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

bulhufas 支持哪些客户端?

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

bulhufas 能提供哪些能力?

资料显示能力标签包括 Local Deployment、Project Management、Semantic Search、Go、Conversation Analysis、RAG Technology。具体工具清单以官方文档为准。

bulhufas 需要什么运行环境?

运行时为 go;属于本地进程,需要在本机装好运行环境。

bulhufas 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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