Notedigit and GitMCP
GitMCP turns public GitHub repositories and GitHub Pages sites into a documentation source for AI assistants, free and without signing in. Notedigit does a similar job for the repositories you cannot make public: your team’s private Markdown, on any git host, behind a sign-in.
Checked against GitMCP’s own pages on . Sources are listed below.
At a glance
| Aspect | Notedigit | GitMCP |
|---|---|---|
| What it serves | NotedigitMarkdown notes from one private Git repository per endpoint | GitMCPDocumentation and code search for a GitHub repository or GitHub Pages site |
| Private repositories | NotedigitYes, through a read-only deploy key | GitMCPDocumented for public repositories only |
| Git hosts | NotedigitAny host your server reaches over SSH | GitMCPGitHub |
| Where it runs | NotedigitYour own server | GitMCPHosted at gitmcp.io, or self-hosted |
| Sign-in and access | NotedigitOAuth 2.1 or access tokens, per user and per repository | GitMCPNo sign-in; per-user access control is not documented |
| Audit log of AI calls | NotedigitEvery session and tool call, with user, client, tool and arguments | GitMCPNot documented; the README says queries are not stored |
| Price and license | NotedigitOne-time license from €149, with source access; no per-user pricing | GitMCPFree, Apache-2.0 |
When GitMCP is the better choice
- The documentation you want assistants to read is already public on GitHub.
- You want something free that works without accounts or a server of your own.
When Notedigit fits
- The notes are private — a company handbook, client projects, decisions — and must stay that way.
- Different people should see different repositories, and you need a record of what each assistant read.
- Your repositories live on GitLab, Bitbucket or your own git server.
Sources
Products change. If something here is out of date, tell us at contact@welldigit.com and we will correct it.