MCP Setup - Nestornotes Docs

Use MCP when your agent client supports remote tools with browser-based OAuth or custom request headers.

https://nestornotes.com/mcp

MCP exposes your authenticated Nestornotes knowledge base as tools for collections, knowledge items, tag discovery and filtering, source content reads, RSS/YouTube/X/LinkedIn/podcast subscription list/detail discovery and management, website monitors and change reports, automated newsletter signup, credits, usage, and search. Dedicated source detail tools expose metadata and the available health, fetch, availability, or resolution diagnostics for each subscribed source. Article detail reads include the stored article content and MHTML storage path. A successful subscribe_to_newsletter result means the signup automation started, not that the external newsletter confirmed the subscription.

When your MCP client supports OAuth, connect to the server URL above and complete the Nestornotes authorization flow in the browser. The hosted server supports Supabase OAuth 2.1 dynamic client registration, so clients such as Claude and ChatGPT should not require you to paste a separate OAuth Client ID. OAuth tokens receive read-only advertised scopes; profile-owned mutation routes exposed by MCP, including knowledge flags, tags, RSS/YouTube/X/LinkedIn/podcast subscriptions, website monitors, and newsletter signup automation, also accept the authenticated Supabase session.

OAuth-capable clients discover the server through these public protected-resource metadata URLs:

https://nestornotes.com/.well-known/oauth-protected-resource
https://nestornotes.com/.well-known/oauth-protected-resource/mcp

Both advertise https://nestornotes.com/mcp as the protected resource and Supabase Auth as the authorization server. They do not advertise Nestornotes API scopes as OAuth scopes because Supabase OAuth Server only accepts its supported identity scopes; Nestornotes grants read-only effective API scopes after validating the Supabase access token.

If a client asks you to manually add an OAuth Client ID, the Supabase project likely needs OAuth 2.1 Server, Dynamic Client Registration, and the /oauth/consent authorization path enabled.

For clients that cannot use OAuth but can send custom headers, use a Nestornotes API key:

Authorization: Bearer nn_live_<prefix>_<secret>

Create API keys from Settings -> API keys inside the app. API-key authentication keeps the full scoped API tool surface, including knowledge flag updates, tag mutations, RSS/YouTube/X/LinkedIn/podcast subscription changes, website monitor changes, and newsletter signup automation when the key has the corresponding write scopes.

Website monitoring tools use snake_case arguments and call the website API:

create_website_monitor (websites:write)
list_website_monitors
get_website_monitor
update_website_monitor (websites:write)
delete_website_monitor (websites:write)
list_website_changes
get_website_change

Client-specific setup guides:

For clients that do not support remote MCP or OAuth, use API v1 with API keys or the Nestornotes CLI.