A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
1 ★ · giuliohome-org/doc-manager · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 1 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository giuliohome-org/doc-manager;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
A zero-knowledge document vault backed by Azure Blob Storage, with a built-in **MCP server** so you can add, read and search your docs straight from a Claude conversation. Talk to your docs through Claude — create from chat, see it in the vault instantly. - **Zero-knowledge by design** — documents and attachments are encrypted in the browser with AES-256-GCM (PBKDF2-SHA256, 600k iterations); the password never leaves the client. - **Talk to your docs** — Claude (web, desktop, Claude Code) can list, fetch, search, create and update plaintext documents through the MCP endpoint. - **One Rust binary** — Rocket backend + React 19 / Vite 8 frontend, deployable to Azure Container Apps, plain Docker, or containerd + Kaniko in a homelab. --- Talking to your docs through Claude The same Rust process exposes a Streamable-HTTP [Model Context Protocol] (https://modelcontextprotocol.io) server at /mcp, gated by an OAuth 2.1 flow against an upstream identity provider (currently **GitHub** — Auth0 reserved for a future round, the code is provider-shaped). Encrypted documents stay private (their content is never returned to Claude); plaintext documents become first-class citizens in the chat. Tools | Tool | What it does | Available in MCP_READ_ONLY | | ------------------- | ------------------------------------------------------------------------------- | ---------------------------- | | list_documents | List every doc with id, title, encrypted flag, attachment info, size | yes | | get_document | Fetch one plaintext document by id; refuses encrypted ones | yes | | search_documents | Case-insensitive substring search over titles (always) and plaintext content | yes | | get_attachment | Fetch the file attached to a doc (filename, bytes, base64, UTF-8 if applicable) | yes | | create_document | Create a new plaintext document; returns the new id | no | | update_document | Replace content (and optionally title) of a plaintext document | no | | add_attachment | Attach a file (text or base64-encoded binary) to a doc; replaces any existing | no | | delete_document | Delete a document and all its blobs (main, title, attachment); irreversible | no | | delete_attachment | Delete only the attachment of a document, leaving the document itself intact | no | Encrypted documents are surfaced to Claude with encrypted: true so it can discover them by title, but their contents and writes are refused server-side. That keeps the zero-knowledge guarantee intact: encrypted = "private to me", plaintext = "shareable with Claude". Add it to Claude Claude.ai's custom-connector advanced settings accept an OAuth **Client ID + Client Secret** (only those two fields), so Claude.ai runs the full OAuth 2.1 + PKCE flow itself and our server only needs to (a) advertise the IdP via well-known metadata and (b) validate the resulting bearer. 1. **Register a GitHub OAuth App.** GitHub → *Settings* → *Developer settings* → *OAuth Apps* → *New OAuth App*. Set: - *Authorization callback URL*: https://claude.ai/api/mcp/auth_callback - Copy the *Client ID* and generate a *Client Secret*. 2. **Configure the server** (env vars on the container app):