Pair with Claude
Claude, working in the notes you actually own.
Point Claude at your Hillnote workspace and let it read, draft, and reorganize the plain-markdown files you keep — over MCP, the raw files, or Hillnote's built-in terminal. No exports, no API keys.
How Claude and Hillnote fit together.
You already think with Claude. Hillnote gives it a home to think in — a workspace of plain-markdown notes Claude can read, write, and reorganize, while everything stays a file you own.
It's all just files
Your workspace is plain markdown in a folder you own — nothing proprietary for Claude to import or sync around.
MCP gives Claude real tools
Through the Model Context Protocol, Claude gets about 33 tools to read, search, write, and reorganize — not just pasted text.
It stays yours
Connect over an OAuth sign-in or a local server, and revoke any time. The files never stop being yours, on your own disk.
Ask Claude across everything you've written.
Connect the workspace and Claude can search, read, and cite your whole knowledge base — answering from your own notes instead of guessing.
Let it edit the real files.
Your workspace is markdown in a folder, so Claude creates documents, rewrites sections, and reorganizes structure directly — no copy-paste, no export to reconcile.
Put Claude to work on a schedule.
Save a prompt as a routine and let a workspace event — a new document, a status change — set Claude going on its own, writing the result straight back to your notes.
Five ways to connect Claude.
Pick the path that fits how you work. The remote endpoint reaches your synced workspaces from anywhere — web or desktop; the local server, terminal, and raw files all work on the files on this machine.
Connect over
Model Context Protocol
~33 toolsThe richest connection — real tools, not just pasted text.
Nothing to install — Hillnote hosts the endpoint. You authorize with an OAuth sign-in.
Works the same in claude.ai on the web and in Claude Desktop. Claude signs in to Hillnote with OAuth — no API keys to paste.
- 1
In claude.ai or Claude Desktop, open Settings → Connectors → “Add custom connector.”
- 2
Paste the Hillnote endpoint shown below.
- 3
Connect and sign in to Hillnote — OAuth authorizes Claude, no keys.
- 4
Ask Claude to list your workspaces to confirm the connection.
Endpoint
https://hillnote.com/mcp
Run it in
Claude Code in the terminal
A CLI agent, right inside your workspace.
Hillnote has a real terminal docked to your workspace, already in the folder. Turn it on in Settings, then launch Claude Code with one click from the terminal toolbar — it operates on the files in front of you.
- 1
Turn the terminal on in Settings → Interface.
- 2
Open the docked terminal — it opens in your workspace folder.
- 3
Click the Claude button in the toolbar — nothing to type.
No setup
Raw markdown files
Your workspace is already just files.
- 1
Right-click a workspace or document and choose “Reveal in Finder / Explorer.”
- 2
Drag the file or folder into Claude, or paste its contents.
- 3
It works from the text directly — handy for a quick one-off, no server.
Through
A synced drive
Keep the folder where it can already see it.
Keep your workspace in a synced drive Claude can already read, and the documents are in reach without an extra step — it's just files in a folder.
Automate with
Routines on events
Put the AI to work on its own.
Beyond chat: a change in your workspace can fire a Claude routine automatically. There's no REST API to wire up — just events and the OAuth-secured connection.
A workspace event
New doc · comment · status change
Claude runs a routine
Your saved prompt, on the change
Written back
The result lands in the workspace
See Claude in a full setup.
Claude is even better alongside the rest of your stack. Each setup wires Hillnote and the tools that fit a kind of work — all on the same markdown files.
Solo Builder
One person. Every hat. One workspace.
Build this setup
Code
Ship software in a markdown-native flow.
Build this setup
Product
Spec, plan, and track in one place.
Build this setup
Writing
Draft, edit, and publish without leaving your words.
Build this setup
Research
Gather, synthesize, and cite what you find.
Build this setup
Dungeon Master
Prep a world. Run it loose.
Build this setupClaude questions, answered
Does this work with claude.ai, or only Claude Desktop?
Both. The remote MCP connection works the same in claude.ai on the web and in Claude Desktop — add the custom connector and sign in. The local server and the built-in terminal are for working on files on your own machine.
Do I need to paste an API key?
No. The remote connection authorizes with an OAuth sign-in scoped to your workspaces, and the local methods never leave your machine. There's no key to copy or leak.
Can Claude edit my files or only read them?
Both. Over MCP and through the built-in terminal, Claude can create, edit, rename, and reorganize documents directly — or you can connect read-only if you'd rather it just read. You can revoke any connection at any time.
Is there a public API I can call?
Not a separate REST API — MCP is the interface, with about 33 tools for reading and writing your workspace. For automation, save a routine that fires on a workspace event; it runs through the same OAuth-secured connection.
What is the built-in terminal?
A real terminal docked to your workspace, already in the workspace folder. Run Claude Code (or any CLI) there and it works on the exact files you're editing — no extra configuration.
What can Claude actually do once connected?
Search and cite across your notes, draft new documents in your voice, and split, merge, rename, and relink existing ones — about 33 tools spanning documents, search, databases, recipes, canvas, and slides.