How it works
From a repository on your git host to an answer in your assistant: six stops, all on a server you control.
-
Step 1: Install it on your server
Notedigit ships as one Docker image and a small Compose kit. One install command creates your team and your owner account; HTTPS is set up automatically.
- Docker Compose
- Your own VPS
- We help you install
-
Step 2: Connect the repo
Add the repository’s SSH address. Notedigit generates a read-only deploy key for it; you add the public key on your git host and run Check connection.
- Any git host over SSH
- Read-only deploy key
-
Step 3: Assign your people
Invite people by email and give each of them the repositories they should read, or open a repository to the whole team.
- Invitation-only accounts
- Per-user or whole-team access
-
Step 4: Add the MCP to any client
Each repository has its own MCP endpoint. Add it to Claude, ChatGPT or your IDE as a custom connector and sign in with OAuth 2.1; custom agents use a personal access token.
- OAuth 2.1
- Personal access tokens
-
Step 5: The assistant reads
Three read-only tools: search, read_file, list_files. Only Markdown is served. The repository is cloned when an assistant starts reading and the clone is deleted after 15 minutes without activity.
- Read-only
- Markdown only
- Fresh from your branch
-
Step 6: Everything is on the record
Every session and every tool call is logged: client, user, tool, arguments, status and duration. Filter by repository, person or date.
- Full audit log
- Kept on your server
The short answers
- What leaves your server
- Only the notes an assistant asks for, sent to that assistant. Nothing is sent to us.
- What the assistant can change
- Nothing. Write tools don’t exist; your repository changes only through your own commits.
- How fresh the answers are
- A new session reads the branch as it is on your git host.
- Who can read a repository
- The people you assign to it, or your whole team if you open it up, each signed in with their own account.