Anything that enriches your agent’s context
If it can be written in Markdown and committed to Git, every assistant your team uses can read it.
Who it’s for: Anyone with knowledge worth keeping in one place and reading from every assistant.
The format is the only rule
Notedigit doesn’t care what the notes are about. Research, legal templates, a glossary, a reading list, recipes: if it is Markdown in a Git repository, it can be served.
Start with one repository
Connect a repository with the read-only deploy key Notedigit generates, assign yourself, and add its endpoint to your assistant as a custom connector. OAuth 2.1 discovery configures the rest.
Grow from there
Add repositories as new uses come up and assign each to the people who need it. Every repository has its own MCP endpoint and its own list of people who can read it.
How to structure the repository
- One topic per file and a clear title make anything searchable.
- Folders are just paths: the assistant can list them to see what is there.
- Plain Markdown is enough: headings, lists and links. No special format is needed.
Setting it up
-
Step 1: Put the notes in a private repository on any git host your server can reach over SSH.
-
Step 2: Connect it with the read-only deploy key Notedigit generates, and assign the people who should read it.
-
Step 3: Add the endpoint to your assistant. OAuth 2.1 discovery configures the rest.