Doc Manager

مجتمعي البحث والويب

Personal document vault on Azure Blob Storage: read, write and search plaintext docs, while client-side AES-256-GCM encrypted docs stay opaque.

التثبيت

خطوات التثبيت موجودة في التوثيق أدناه. التوثيق

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. Doc Manager
  2. Talking to your docs through Claude
  3. Building the frontend
  4. Running with Docker
  5. TL;DR — containerd + Kaniko (homelab)
  6. Configuration reference
  7. End-to-end tests

Doc Manager

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
ToolWhat it doesAvailable in MCP_READ_ONLY
list_documentsList every doc with id, title, encrypted flag, attachment info, sizeyes
get_documentFetch one plaintext document by id; refuses encrypted onesyes
search_documentsCase-insensitive substring search over titles (always) and plaintext contentyes
get_attachmentFetch the file attached to a doc (filename, bytes, base64, UTF-8 if applicable)yes
create_documentCreate a new plaintext document; returns the new idno
update_documentReplace content (and optionally title) of a plaintext documentno
add_attachmentAttach a file (text or base64-encoded binary) to a doc; replaces any existingno
delete_documentDelete a document and all its blobs (main, title, attachment); irreversibleno
delete_attachmentDelete only the attachment of a document, leaving the document itself intactno

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):

     export OAUTH_PROVIDER=github
     export OAUTH_PUBLIC_BASE_URL=https://doc-manager.giuliohome.com
     export OAUTH_ALLOWED_USERS=giuliohome     # comma-separated GitHub logins
     # optional — disables create/update tools:
     export MCP_READ_ONLY=true

    OAUTH_ALLOWED_USERS is required — an empty allowlist refuses to start, so a misconfiguration cannot silently let any GitHub user in.

  3. Add the connector in Claude.ai — Settings → Connectors → Add custom connector, URL https://doc-manager.giuliohome.com/mcp, then Advanced settings → paste the GitHub OAuth App's Client ID and Client Secret. The first request triggers the OAuth dance: Claude.ai sees the 401 + WWW-Authenticate from /mcp, fetches our well-known metadata, walks you through github.com/login/oauth/authorize, and forwards the resulting bearer on every subsequent call. The server validates each request by calling https://api.github.com/user (5-min cache, SHA-256-hashed token key).

If OAUTH_PROVIDER is unset the endpoint replies 503 Service Unavailable, so the MCP surface is fully opt-in.


Building the frontend

cd frontend
npm i
npm run build
cd ..

Running with Docker

docker build -t giuliohome/doc-manager:latest .
export AZURE_STORAGE_ACCOUNT=youraccount
export AZURE_STORAGE_ACCESS_KEY=yourkey
export RUST_ROCKET_EXACT_ORIGIN=http://localhost:8080
# optional — enables the MCP endpoint:
export OAUTH_PROVIDER=github
export OAUTH_PUBLIC_BASE_URL=http://localhost:8080
export OAUTH_ALLOWED_USERS=your-github-login
docker run -p 8080:8080 \
  -e AZURE_STORAGE_ACCOUNT \
  -e AZURE_STORAGE_ACCESS_KEY \
  -e RUST_ROCKET_EXACT_ORIGIN \
  -e OAUTH_PROVIDER \
  -e OAUTH_PUBLIC_BASE_URL \
  -e OAUTH_ALLOWED_USERS \
  giuliohome/doc-manager:latest

TL;DR — containerd + Kaniko (homelab)

sudo mkdir /kcache
sudo ctr i pull gcr.io/kaniko-project/warmer:latest
sudo ctr run --net-host --rm --mount type=bind,src=$(pwd),dst=/workspace,options=rbind:rw --mount type=bind,src=/kcache,dst=/cache,options=rbind:rw gcr.io/kaniko-project/warmer:latest kaniko-warmer /kaniko/warmer --cache-dir=/cache --image=docker.io/rust:1-slim-bookworm --skip-tls-verify-registry index.docker.io --dockerfile=/workspace/Dockerfile

sudo ctr i pull gcr.io/kaniko-project/executor:latest
sudo ctr run --net-host --rm --mount type=bind,src=$(pwd),dst=/workspace,options=rbind:rw --mount type=bind,src=/kcache,dst=/cache,options=rbind:rw gcr.io/kaniko-project/executor:latest kaniko-executor /kaniko/executor -cache-dir=/cache --dockerfile=/workspace/Dockerfile --context=/workspace --no-push --skip-tls-verify --build-arg pkg=docs-app --tarPath=/workspace/doc-manager-latest.tar --destination=giuliohome/doc-manager:latest --cache=true --cache-repo=giuliohome/doc-manager:latest --no-push-cache

sudo ctr image import doc-manager-latest.tar
sudo ctr c create --net-host docker.io/giuliohome/doc-manager:latest doc-manager
sudo ctr t start doc-manager

Configuration reference

Env varRequiredPurpose
AZURE_STORAGE_ACCOUNTyesAzure Storage account name (container documents is auto-created)
AZURE_STORAGE_ACCESS_KEYyesStorage access key
RUST_ROCKET_EXACT_ORIGINyesCORS origin for the React frontend
OAUTH_PROVIDERno (enables MCP)github (Auth0 reserved for future)
OAUTH_PUBLIC_BASE_URLwith OAUTH_PROVIDERPublic base URL of this server, e.g. https://doc-manager.giuliohome.com
OAUTH_ALLOWED_USERSwith OAUTH_PROVIDERComma-separated GitHub logins; must list at least one user — empty refuses to start
MCP_READ_ONLYno (default false)When true/1/yes, hides create/update MCP tools
MCP_PUBLIC_INTROSPECTno (auto)Opens /mcp for unauthenticated tools/list only (calls are 403'd) so registries like Glama can probe. Auto-on when both AZURE_STORAGE_ACCOUNT and OAUTH_PROVIDER are unset; set 0 to force-disable.
MCP_STDIOno (default false)When true/1/yes (or pass --stdio), runs as a stdio MCP server (newline-delimited JSON-RPC on stdin/stdout) instead of starting the HTTP listener. Used by registries that wrap servers with mcp-proxy.

End-to-end tests

See the e2e repo.

الأسئلة الشائعة

ما هو Doc Manager؟

Personal document vault on Azure Blob Storage: read, write and search plaintext docs, while client-side AES-256-GCM encrypted docs stay opaque.

كيف أثبّت Doc Manager؟

اتبع خطوات التثبيت في توثيقه المعروض في هذه الصفحة وفي مستودعه.

هل Doc Manager مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون Doc Manager؟

ينشره giuliohome-org. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من القوائم المجتمعية awesome-mcp-servers ومستودع المشروع على GitHub. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.