Connect Zernote to Claude

Query your user-interview transcripts and research notes from Claude via OAuth — no API keys needed for the Claude Connectors flow.

1. What you can do

List your research folders and browse interviews by folder
Read interview metadata and full transcripts (with pagination for long transcripts)
Search across your interviews with semantic search and get ranked matching fragments
Update interview notes when you explicitly ask Claude to save synthesis or action items

2. Prerequisites

An active Zernote account with at least one processed interview
A Claude account with Connectors support (Claude.ai, Claude Desktop, or Claude Code)

3. Custom connector (available today)

Zernote is not yet listed in the official Claude Connectors Directory. Until directory approval, connect Zernote as a custom connector by entering the MCP server URL manually:

Sign in to Zernote in your browser.
Open claude.ai → Settings → Customize → Connectors.
Choose Add custom connector (or equivalent manual-entry option).
Enter the MCP server URL: https://zernote.com/mcp
Click Connect and complete OAuth sign-in to Zernote. Review the requested permissions and approve access.
In a new chat, open the tools menu [+] → Connectors → toggle Zernote on.

Once Zernote is approved for the Connectors Directory, you will also be able to search for Zernote in the directory and connect with a one-click Connect button — no manual URL entry required. Both paths use the same OAuth authorization and grant access to the same tools.

4. Connect on Claude.ai (directory flow)

When Zernote appears in the Claude Connectors Directory:

Sign in to Zernote in your browser.
Open claude.ai → Settings → Customize → Connectors.
Search for Zernote → click Connect.
Complete OAuth sign-in to Zernote and approve access.
In a new chat: [+] → Connectors → toggle Zernote on.

5. Claude Code

claude mcp add --transport http zernote https://zernote.com/mcp

Then run /mcp, select zernote, and choose Authenticate to complete OAuth in your browser.

6. MCP endpoint and authentication (other MCP clients)

MCP endpoint: https://zernote.com/mcp
Transport: Streamable HTTP (POST)
Authentication: OAuth 2.0 with browser-based authorization and Dynamic Client Registration. There is no API key or service-account access method for MCP.
OAuth authorization server metadata: https://zernote.com/.well-known/oauth-authorization-server
OAuth protected resource metadata: https://zernote.com/.well-known/oauth-protected-resource/mcp

Each user authenticates individually. The connected client receives only the data in your own Zernote account.

7. OAuth scopes

Zernote uses granular OAuth scopes. During authorization, you may see the following permissions:

folders:read — Read your folders
interviews:read — Read your interviews
transcripts:read — Read interview transcripts
search:read — Search your interviews
notes:write — Write interview notes

If the connecting client does not request specific scopes, all five scopes are granted by default.

8. Tools reference

Tool	OAuth scope	Access	Description	Example prompt
`list_folders`	`folders:read`	Read	List folders available to the authenticated user. Supports pagination (`limit`/`offset`).	"What research folders do I have?"
`list_interviews`	`interviews:read`	Read	List interviews, optionally filtered by `folder_id`. Supports pagination (`limit`/`offset`).	"List interviews in folder X from last month"
`get_interview`	`interviews:read`	Read	Get interview metadata and truncated transcript preview.	"Summarize interview {id}"
`get_transcript`	`transcripts:read`	Read	Get full transcript text with speaker placeholders resolved. Large transcripts are returned in character windows (`limit`/`offset`).	"Pull quotes about onboarding from interview {id}"
`search_interviews`	`search:read`	Read	Semantic search across interview transcripts. Returns interviews ranked by relevance with matching text fragments.	"Find interviews mentioning pricing objections"
`write_note`	`notes:write`	Write	Update interview notes for the specified interview.	"Save these synthesis notes to interview {id}"

9. Permissions and data access

OAuth grants access only to your Zernote account data. The connected assistant reads or writes only when you prompt it in that chat. Zernote never shares your data with an AI assistant unless you complete OAuth authorization for that specific client. For full details on what data MCP connections can access, see section 7 of our Privacy Policy.

10. Troubleshooting

Connection fails or wrong Zernote account

Open an incognito or private browser window.
Sign in to Zernote with the correct account.
Sign in to claude.ai with the correct Claude account.
Disconnect and reconnect the Zernote connector.

Connector shows no tools

Go to claude.ai/customize/connectors (use the web UI even if you chat in Claude Desktop).
Disconnect Zernote, then click Connect again without refreshing the page.
Start a new chat and toggle the Zernote connector on.

Still stuck?

Email report@zernote.com with:

Which client you are using (Claude.ai, Claude Desktop, Claude Code, or another MCP client)
A screen recording of the connect steps
Browser console logs (Cmd+Option+I → Console on macOS; Ctrl+Shift+I → Console on Windows/Linux)

11. Disconnect and revoke access

To revoke access, go to Claude → Settings → Customize → Connectors → Zernote → Disconnect. OAuth tokens are revoked when you disconnect; Zernote stops serving your data to that client immediately.

12. Contact

Product support email: report@zernote.com

Product support: @sagotly

Last updated: 2026-07-03