Notedigit is a secure, OAuth-authenticated MCP server for a private Git repository of Markdown notes: connect a repo with a read-only deploy key and any MCP-capable AI assistant can search and read the notes, with per-user access control and a full audit trail. Content is never stored; repositories are cloned on demand and pruned after idle.
A private Git repo in. A secure MCP server out.
Notedigit turns a private Git repository of Markdown notes into a secure, OAuth-authenticated MCP server that your AI assistant — any MCP client — can read.
Read-only · OAuth 2.1 · Every request logged
git@github.com:org/handbook.git
deploy key
/mcp/9f2c…e41a
14:02:11 claude maria@team search {"query":"incident runbook"} ok 84ms
Why this exists
Pasting docs into chat
It doesn't scale past a few files, and every paste is context you can't take back. Nobody knows what left the building.
Broad integrations
A drive or wiki connector exposes far more than the docs you meant to share. Most offer no per-user access control and no record of what was read.
Notedigit
The middle ground: one repo, three read-only tools, per-user assignment, and an audit trail of every call. Nothing else is reachable.
One repo → one MCP endpoint
Point Notedigit at a repo; it exposes a per-repository URL any MCP client can connect to.
OAuth, not shared secrets
Clients authenticate with OAuth 2.1; only users explicitly assigned to a repository may read it.
Nothing is retained
The repo is cloned on demand and the clone is removed once the session goes idle — the server holds no copy between requests.
Full traceability
Every request records the client, the user, and the exact tools it called.
How it works
-
Connect a repo. Notedigit generates an ed25519 deploy key in-app; you add the public half to the repo and run a connection check before the repository goes live.
-
A client adds the repository URL as a custom connector. OAuth discovery and Dynamic Client Registration configure the rest; the user signs in and approves.
-
A request arrives. The repo is cloned on demand into an ephemeral bare mirror — shallow, single-branch, no working tree of plaintext files.
-
Read-only tools run. Every call is logged with the client, the user, the tool, and its arguments.
-
Idle clones are pruned after about 15 minutes. Nothing lingers.
The whole tool surface
search
Keyword search across notes
read_file
Fetch one note by path
list_files
Browse note paths, optional prefix
All read-only. Write tools don't exist.
Security model
OAuth 2.1 only
Authorization-server discovery and Dynamic Client Registration. No shared bearer tokens to leak or rotate.
Per-user repository assignment
A user can read a Markdown repository only if explicitly assigned to it. Access is granted per person, per repository.
Ephemeral bare mirrors
Clones are bare, shallow, single-branch, and pruned after idle. Content lives only in the git object database, never as plaintext files on disk.
Encrypted secrets
SSH keys and repo URLs are encrypted at rest. Private keys are never displayed and never touch temp files; they're passed to git in-memory per operation.
Full audit trail
Sessions and tool calls capture client, user, IP, tool, arguments, status, and duration. Browse and filter by repository, user, and date.
Rate limiting
Requests are rate-limited per token and per IP.
"AI can read our docs, and we can see exactly what it touched."
Our own company Markdown repository is served to our AI assistants through Notedigit. The product runs on its own knowledge base.
Built by Well Digit, the team behind Aviadigit and the AI-layer consultancy.
For teams
One team, one home
Each account has one team. The team owns the Markdown repositories, the deploy keys, the members, and the subscription.
Invitations and roles
Invite members by email; an invitation reserves a seat and expires after 7 days. Roles are Owner, Admin, and Member.
Per-repository access
Repository access is assigned per user. Joining the team grants nothing by itself.
Sign-in security
Password plus two-factor with TOTP and recovery codes. Passkeys are supported.
Pricing
Every plan starts with a 7-day free trial. No card required.
Cancel anytime. Your Markdown repositories pause; your data is kept.
FAQ
Which AI assistants work with it?
Any MCP client. Add the repository URL as a custom connector — OAuth discovery configures the rest, and you sign in with your Notedigit account. Client-specific steps are on the use cases page.
Which git hosts are supported?
Any host that accepts an SSH key for repository access. Notedigit generates the keypair; you add the public key to the repo.
Is my content stored on your servers?
No. Repos are cloned on demand as bare mirrors, served from git object storage, and pruned after about 15 idle minutes. No copy is held between sessions.
How fresh is the content?
Each session serves from an on-demand clone. While a clone is warm, changes on the git host appear after the idle prune — within minutes, not instantly.
Can the AI modify my notes?
No. The server exposes three read-only tools: search, read a file, list files. Write tools don't exist.
What can I see about AI access?
Every session and tool call: which client, which user, which tool, its arguments, status, and duration — filterable by repository, user, and date.
What file types are served?
Markdown.
What happens if I cancel?
Your Markdown repositories and MCP access pause; settings and billing stay available and your data is kept. Reactivate to pick up where you left off.