Connect Jotpile to your AI

Your notes, from the chat you already use.

Jotpile is a Model Context Protocol (MCP) server. Connect it once, and your AI assistant can save, find, organise and link your notes for you, from inside the conversation.

In plain terms: you tell Claude "save this to Jotpile" and it is there, with a link to open it. Later you ask "what did I write about the cabin?" and it reads your notes back to you.

Every client needs the same address:

https://jotpile.app/api/mcp

You need a Jotpile account (email or Google sign-in, no card needed). Nothing else.

Claude

claude.ai on the web, Claude Desktop and the Claude mobile apps share one connection: add it once and it is there in all of them.

In Claude, open Settings > Connectors and choose Add custom connector.
Name it Jotpile and enter the address above.
Claude opens Jotpile's sign-in, then an approval screen. Check that it says your approval goes to claude.ai, and approve.
In any chat, try "how many notes do I have in Jotpile?" to confirm.

On a Team or Enterprise plan, an owner may need to add the connector for the organisation first.

Claude Code

Run claude mcp add --transport http jotpile https://jotpile.app/api/mcp
In a session, run /mcp, pick Jotpile and sign in. The approval screen will say it goes to a program on your computer (localhost): that is Claude Code, and it is expected.

ChatGPT

In ChatGPT's settings, open the connectors (or apps) section. The exact labels move between releases, and custom connectors may need developer mode switched on.
Create a connector with the address above, and choose OAuth as the authentication.
ChatGPT opens Jotpile's sign-in. Approve the connection.

Other MCP clients

Any client that supports remote MCP servers with OAuth needs only the address: it will find the sign-in by itself. For one that cannot do OAuth, create a personal access token in Settings > Integrations and send it as Authorization: Bearer <token>. A token is shown once, does not expire, and can be revoked on the same page.

What it can do

Find: search, and list by notebook, tag, date, reminder, or whether a note has an image or a file.
Write: create and edit notes, pin, archive, trash and restore them.
Organise: notebooks, tags and colours, one note at a time or in bulk.
Link: link notes to each other, and see what links back.
Remind: set and clear reminders.
Undo: read a note's edit history and restore an earlier version.

Every note it hands back comes with its link, so you can open it in Jotpile in one click. It cannot upload images or files; those stay in the app. Trashed notes can be restored for 30 days, and only emptying the trash deletes for good.

Example prompts

"Save this as a note in Jotpile, in my Trips notebook"
create_note with the text, then move_to_project. You get the note's link back.
"What did I write about the roof box?"
search_notes, then get_note on the best match to read it in full.
"Tag everything from last week about the cabin with 'cabin'"
list_notes over the last week, then bulk_add_tag on the ones that fit.
"Remind me about the packing list on Friday morning"
set_reminder on that note. It arrives as a notification on the devices where you turned them on.
"Which notes link to my budget note?"
get_backlinks, with a link to each note that mentions it.

Your data

A connected assistant acts only on your own notes, and only after you approve it on Jotpile's own screen.
You can see every connected assistant, and disconnect any of them, in Settings > Integrations.
Access tokens are stored as hashes, never in readable form. Your notes are stored in the EU.
What the assistant's provider does with what it reads is governed by that provider's own policies. Ours is in the privacy policy.

Troubleshooting

"Couldn't reach the MCP server": Check the address is exactly https://jotpile.app/api/mcp, including /api/mcp.
The sign-in window closes or loops: Allow pop-ups for the assistant's site, and sign in to Jotpile in the same browser.
It asks you to sign in again: A connection made before 28 September 2026 asks once more when its token runs out. Connections made since then renew themselves.
New tools do not show up: Assistants cache the tool list. Start a new conversation, or disconnect and reconnect.

Still stuck? Write to inbox@jotpile.app.

For developers

Endpoint: https://jotpile.app/api/mcp, Streamable HTTP, JSON-RPC 2.0. POST for messages (batches up to 20); a GET with Accept: text/event-stream returns a stream that closes at once, since the server is stateless and pushes nothing.
Protocol revisions: 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05.
Authorization: OAuth 2.1 with dynamic client registration at /oauth/register, PKCE S256 required. Access tokens last 30 days; refresh tokens rotate on use and last 90 days from the last refresh. Unauthenticated calls get 401 with WWW-Authenticate: Bearer resource_metadata=....
Discovery: /.well-known/oauth-protected-resource (also under /api/mcp) and /.well-known/oauth-authorization-server.
Tools: Every tool carries a title and declares whether it only reads, and whether a write is destructive. The full list is in llms.txt, or ask the server with tools/list.
Limits: 300 writing calls per user per 5 minutes; 20 client registrations per IP per hour; request bodies up to 2 MiB; list_notes returns up to 200 per call; bulk tools take up to 500 ids.