searchLABSCO SUMMARY
Notes that carry their own instructions per folder.
This is a notes app with rules attached: instructions live on the container, so what an assistant does with a note depends on where the note is filed. That makes the folder structure do real work rather than just sorting, and it means one vault can hold work and personal material without them being handled the same way. Setup is OAuth in a browser, with nothing installed.
What it is
A hosted Markdown notes service whose MCP endpoint is a first-class way in, not an export. Notes live in containers that carry their own AI instructions, so the same vault can tell an assistant to behave differently in a work folder than in a personal one. Files attach to notes, and tags and links cross-cut the whole thing.
What you get
- Notes created, read, listed, updated and deleted, in Markdown
- Containers — the folders notes live in — created, read, listed and updated
- Per-container instructions read and rewritten, so behaviour follows the folder
- Files attached from an upload or from a URL, removed, and fetched back as a download URL
- Tags created and listed, and links between notes managed
- Teams listed and read, and a dashboard view of the whole account
Requirements
An account at hjarni.com, authorised over OAuth on first connection — no API key and nothing installed. Any client supporting Streamable HTTP connects to https://hjarni.com/mcp; adding it as a connector in the Claude or ChatGPT web apps requires those products' paid tiers.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Keeping what an assistant learns between sessions
The conclusions from one conversation are written as notes and read back in the next, so context survives a new chat instead of being pasted in again.
02
Making the assistant behave differently per project
Read and rewrite the instructions on a container, so notes filed under a client folder are handled by the rules that client needs without restating them each time.
03
Organising a vault that grew faster than its structure
Create the containers the material actually falls into, move notes into them, and add the tags that cut across folders.
04
Keeping source material with the note about it
Attach a file directly or pull it in from a URL, and get a download link back later — so the PDF behind a summary stays next to the summary.
05
Connecting notes that belong together
Manage the links between notes so a topic reads as a set rather than as scattered entries, and list the tags to see what threads already exist.
06
Seeing where the whole vault stands
Read the dashboard for the shape of the account, and the teams behind it when notes are shared rather than personal.
22 tools
Listed in project docs. Your client may show a different list.
notes-createnotes-getnotes-listnotes-updatenotes-deletecontainers-listcontainers-createcontainers-getcontainers-updatetags-listtags-createlinks-manageinstructions-getinstructions-updatefiles-attachfiles-attach_from_urlfiles-get_download_urlfiles-removedashboard-getteams-listteams-getBEFORE YOU INSTALL
What to know first
Tools you get
22 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
The documented client connects to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://hjarni.com/mcpMCP Clients
Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"hjarni": {
"url": "https://hjarni.com/mcp",
"type": "http"
}
}
}
