Your notes, in your AI tools.
Parley Notes runs a remote MCP server. Claude, ChatGPT and other MCP clients can search and read a person's notes, with their permission.
REST API, version 1
NewRead notes, create notes from text or an audio link, and get a webhook the moment a note is ready. OAuth 2.0 and JSON. The Parley Notes integration for Zapier is built on it.
Read the API v1 referenceAdd it as a connector. Sign in and approve. That is all.
In Claude or ChatGPT
- Add a custom connector with the address https://app.parleynotes.com/mcp.
- Sign in to Parley Notes and approve the connection in the app.
- Ask about your meetings. The assistant searches and reads your notes.
What it can do
- It can only read. It cannot change, send or delete anything.
- Health notes are never included.
- End-to-end encrypted transcripts stay unreadable.
- Turn a connection off any time in Settings in Parley Notes.
Four tools. Search, read and list.
searchArguments: querySearch the person's notes by words and by meaning. Up to 10 notes, best first, each with an id for fetch. Health notes are never included.
fetchArguments: idRead one note in full: the summary, decisions, action items, open questions and other sections, the person's own notes, and the transcript unless it is end-to-end encrypted.
list_notesArguments: folder?, since? (YYYY-MM-DD), limit? (up to 50)The newest notes, optionally in one folder and from a date on. Newest first.
list_foldersArguments: noneThe person's folders, with how many of the newest notes are in each.
Standard OAuth. Found on its own by any MCP client.
The server follows the MCP specification (revisions 2025-11-25, 2025-06-18 and 2025-03-26). Clients discover sign-in through the well-known addresses, register themselves, and send the person to Parley Notes to approve.
| POST /mcp | The tools. JSON-RPC 2.0 over Streamable HTTP, one message per request, plain JSON answers. Needs a Bearer token. |
| GET /.well-known/oauth-protected-resource | Where to get a token for /mcp (RFC 9728). |
| GET /.well-known/oauth-authorization-server | The authorization server and its endpoints (RFC 8414). |
| POST /oauth/register | Dynamic client registration for public clients (RFC 7591). |
| GET /oauth/authorize | Starts sign-in. The person approves the client in the Parley Notes app. |
| POST /oauth/token | Exchanges a code, or a refresh token, for an access token. |
| POST /oauth/revoke | Revokes a token. |
Start with one meeting
and see where it goes.
Free to start on every device.
Plans and prices are on the pricing page.