Zenodot MCP Server Beta: Bring Your Library to the AI Tools You Use

Today we are opening the beta of the Zenodot MCP Server: a new way to connect your Zenodot Library to compatible AI clients.

MCP, or Model Context Protocol, gives AI tools a standard way to request useful context from another service. In this beta, that means MCP-enabled clients and connectors such as ChatGPT and Claude can search and read your current Zenodot Library while you remain in control of the connection. Availability and setup vary by product, so check the client’s own MCP instructions as well as Zenodot’s guide.

MCP access is for Pro users only

The Zenodot MCP Server is available only to linked Pro accounts. If you are on a Pro plan and your Zenodot account is linked, you can create an API key from Settings → MCP access in the app.

This is a beta release, so the feature may change and things may break while we learn from real use. Before connecting an account, read the Zenodot MCP documentation and the connection guide.

What this means for your Library

Your Library is useful because it keeps the things you have learned, noticed, and decided connected over time. MCP makes that knowledge available to compatible AI tools outside the Zenodot app—including supported connections in ChatGPT, Claude, and other MCP-enabled assistants.

For example, you could use a connected client to:

• search your Pages for a topic or question;
• open a Page when you need the full current body;
• browse Page and folder metadata; and
• follow explicit links and backlinks to trace related ideas.

The client can then use the context it retrieves to help with the work you are doing there. You do not need to copy and paste a collection of notes into every conversation, and you can keep Zenodot as the place where your knowledge is captured and maintained.

Read-only tools for now, write tools on the way

The beta currently only features read-only tools. MCP can read from your current Library, but it cannot change it. The server exposes Pages, folder metadata, and explicit Page links. Write tools are on the way, but they are not part of this beta. Chute Notes, Page snapshots, raw database fields, and Ask conversations are also outside the MCP surface.

That boundary is intentional. A connected AI client can help you find and make sense of what you have saved, while edits and other sensitive actions stay inside Zenodot’s existing product surfaces.

You stay in control of the connection

Connection access uses a user-generated API key. When you create one, choose an expiry and copy the full key—the key is shown only once. Each key is limited to the library:read scope, and you can revoke it independently from Zenodot Settings.

The key should be treated like a password. Only add it to a client you trust, do not paste it into prompts, and revoke it when you no longer want that client to access your Library. Zenodot also re-checks that the account is linked, has Pro access, and has a recent entitlement sync on each request. If Pro access ends, MCP requests are denied.

Start with the documentation

To connect the beta, open Zenodot and go to Settings → MCP access, create a key, then follow the step-by-step connection guide. You will need a compatible MCP client and the Zenodot server URL:

https://api.zenodotapp.com/mcp

The capabilities reference explains the four available tools, and privacy and access covers keys, scopes, and account boundaries in more detail.

We are excited to see how Pro users connect their Library to the rest of their thinking practice. This is an early step toward making Zenodot’s connected knowledge more useful wherever thoughtful work happens.

The Zenodot team