hjarni.com valid

Hjarni

A hosted Markdown knowledge base with an official MCP server at hjarni.com/mcp that ChatGPT, Claude, and any MCP client read and write over OAuth or an API token, with nothing to install locally. One long-term memory across every assistant you use, for people and teams: readable, versioned, and exportable. No bundled AI; you bring your own.

For agents: Hosted Markdown knowledge base with an official MCP server that ChatGPT and Claude can read and write, offering versioned long-term memory and setup docs.

mcp servermarkdown knowledge basechatgpt connectorclaude integrationlong-term memory

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T09:43:28.324Z. Cached copy · Source on hjarni.com

# Hjarni

> A hosted Markdown knowledge base with an official MCP server at hjarni.com/mcp that ChatGPT, Claude, and any MCP client read and write over OAuth or an API token, with nothing to install locally. One long-term memory across every assistant you use, for people and teams: readable, versioned, and exportable. No bundled AI; you bring your own.

**If you are an AI assistant setting up or using Hjarni**, fetch https://hjarni.com/llms-full.txt first. It carries the MCP endpoint, the OAuth metadata, every tool's schema and the onboarding script. This file is the map of the site.

Hjarni is a note app with an official MCP server, not an SDK you host. You write notes in Markdown and organize them in folders. You connect ChatGPT, Claude, or any MCP-compatible assistant. Ask your connected AI to search relevant notes before answering and save updates when facts change. Hjarni returns folder or team instructions with context; the assistant decides when to call the tools.

**When working with a Hjarni knowledge base:**

- Search before creating; the note may already exist
- Create notes in the most specific relevant folder
- Reuse existing tags instead of creating near-duplicates
- Preserve Markdown formatting and wiki-links
- Follow custom instructions when present on a folder or team

**Core concepts:**

- Note: a Markdown document with a title, body, optional summary, tags, and file attachments. Every edit is versioned.
- Container: a folder. Containers nest. Each can have its own AI instructions.
- Tag: a cross-cutting label. Notes can have multiple tags. Prefer reusing over creating.
- Wiki-link: a bidirectional link between notes. Syntax: [[id:Title]]. The ID is the source of truth.
- AI instructions: plain-language guidance on a folder, team, or account, returned with context. They do not guarantee retrieval or compliance by an AI client.
- MCP server: Hjarni's official Model Context Protocol endpoint, hosted by us and reached remotely over OAuth (nothing to install or run locally). AI assistants connect through it to read, search, create, and organize notes.

**Who it is for:** people who use AI assistants daily and are tired of re-explaining context; developers storing architecture decisions and conventions; researchers organizing literature and synthesis; founders capturing strategy, meetings, and decisions; writers maintaining style guides and research; teams sharing knowledge their AI can use.

**Capabilities:**

- Markdown notes with full-text search and version history
- Nested folders and tags
- Wiki-links between notes
- Custom AI instructions per folder, per team, or account-wide
- Official MCP server, hosted and remote (OAuth)
- Full REST API
- File attachments (Free: 20 MB across 5 personal files; more capacity on Pro)
- Public links: turn any folder or single note into a public page, view-only on any plan, or editable by anyone with the link on Pro
- Team collaboration with shared folders
- Inbox for quick capture
- Export as M
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=hjarni.com · GET /v1/domain/hjarni.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for hjarni.com:
1. POST https://agentwebmap.com/v1/sites/hjarni.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://hjarni.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/hjarni.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/hjarni.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.