ContextBolt in n8n · 15 minutes · Advanced

n8n MCP for Bookmarks: Automate Saved Content (2026 Guide)

Wire your saves into scheduled workflows: weekly digests, auto-routing, AI triage.

Add to Chrome
Free extension · the AI connection is on Pro, $6/mo
Bookmarks MCP server for Claude, Cursor & Codex n8n · ContextBolt connected example library
What did I save about rate limiting?
Used search_bookmarks
Token buckets beat fixed windows for bursty trafficX · @dan_abramov
How we rate limit 40k req/s on one boxReddit · u/pgstash
Rate limiting is a product decision, not a configPriya Patel
Searched 847 saves across X, Reddit and LinkedIn

5.0 on the Chrome Web Store Trusted by 300+ users across the globe
WORKS WITH

It connects in 15 minutes.

  1. Connect your ContextBolt account n8n doesn't speak MCP natively yet. Install the community node 'n8n-nodes-mcp' from the community nodes registry. This adds an MCP Client node that can talk to any MCP server, including ContextBolt's. For OAuth, add https://api.contextbolt.app/mcp and complete sign-in with your Pro account email and email code, then allow access. If your client cannot complete OAuth, follow the personal-URL compatibility steps on this page. Get that private URL from the extension under Settings, MCP Integration, Older clients. Use one connection method.
  2. Personal-URL setup: Copy your private MCP URL Open the ContextBolt extension, then Settings, MCP Integration. Newer versions keep it under Older clients. You need an active Pro account. Copy the full private URL, not just the token at its end. Wherever an example shows https://api.contextbolt.app/mcp/YOUR_TOKEN, replace that entire example URL with your copied URL. Keep it private.
  3. Personal-URL setup: Configure the MCP Client node in n8n Add the MCP Client node to a workflow. Set the transport to HTTP and the server URL to the full private URL you copied from ContextBolt Settings under MCP Integration. Test the connection: the node should list the five ContextBolt tools (search_bookmarks, list_clusters, get_cluster_bookmarks, get_recent_bookmarks, and save_bookmark).
  4. Build your first workflow Create a Schedule trigger (e.g. weekly), connect it to the MCP Client node calling search_bookmarks, then chain output to whatever destination you want: Slack, email, Notion, Airtable. Save and activate the workflow.

The guide covers every client and the compatibility options. How the connection works

Then ask it something real.

“Weekly digest: search bookmarks tagged 'AI' from the last 7 days, summarize with an AI node, send to Slack channel.” Standard weekly knowledge digest. Schedule trigger fires Monday 9am, MCP node retrieves recent saves, OpenAI/Anthropic node summarizes, Slack node posts. Total runtime under 30 seconds.
“Auto-route saves: when a new bookmark mentions 'competitor', append it to a Notion 'Competitive Intelligence' database row.” Automation pattern for tracking competitors. Use a poll trigger checking ContextBolt for new saves matching keywords, then write to Notion via Notion node. Replaces manual triage.
“Build a daily standup: list bookmarks I saved yesterday, group by topic, post the list to my personal Slack DM.” Personal accountability flow. Useful for solo founders or researchers who want a daily reminder of what they've been reading.
“Cross-post: when I save something on Twitter, automatically draft a quote-tweet in Buffer's queue for review.” Content workflow. ContextBolt detects the new Twitter save, n8n routes it to the Buffer node with a draft caption. You review in Buffer before publishing.

What it can do in n8n.

  • Schedule recurring queries against your bookmark collection
  • Trigger workflows when new bookmarks match certain keywords
  • Combine ContextBolt search with AI summarization nodes
  • Route saves to Slack, email, Notion, Airtable, or any n8n integration
  • Build content pipelines without writing backend code
  • Run workflows unattended on a schedule, no Claude Desktop required

The longer story.

n8n is the automation platform of choice for people who want Zapier-style workflows without per-task pricing or vendor lock-in. The community MCP node makes ContextBolt available to any n8n workflow. That unlocks scheduled and triggered automation around your saved content, beyond what an interactive AI client can do. This guide covers the ContextBolt-specific setup; for a standalone overview of the n8n MCP server, see our directory listing.

What unattended automation enables

Most ContextBolt workflows are interactive: you ask Claude something, Claude searches your bookmarks, Claude responds. That model breaks down when you want recurring or background work.

A few patterns that only make sense as scheduled automation:

  • Weekly knowledge digest: Every Monday at 9am, gather everything you saved in the last 7 days, summarize it by topic, post to your Slack DM. Forces you to review your saves rather than letting them pile up.
  • Smart routing: New save mentions a competitor? Append it to your competitive-intelligence database. New save about a current project? Tag it in Notion. None of this requires you to open Claude Desktop.
  • Time-boxed audits: End of every quarter, list your most-saved topics, top sources, and any saves you flagged as important but never followed up on.

These aren’t conversational. They run on a schedule. n8n is the right shape for them.

n8n MCP setup gotchas

The community MCP node has been stable but has rough edges. Three things we ran into when wiring up our own automations:

  • Token in the URL: ContextBolt’s endpoint embeds the token in the path itself (/mcp/YOUR_TOKEN), so the URL counts as a secret. Store it in an n8n credential rather than hardcoding it inline, and never echo the workflow URL into a Slack or email node.
  • Rate limiting: ContextBolt’s MCP server caps each Pro account at 200 calls per hour. A workflow that polls every minute will run into the limit fast. Set sensible intervals (every 15+ minutes is plenty for personal automation).
  • Tool naming: ContextBolt exposes six tools today: the read tools search_bookmarks, list_clusters, get_cluster_bookmarks, get_recent_bookmarks and export_bookmarks, plus the write tool save_bookmark. The full list is also available by hitting the MCP node’s Tools tab rather than hardcoding names, which protects you from future renames.

Where n8n MCP fits in the stack

For knowledge workers doing literature review or competitive research, n8n handles the boring parts: collecting, routing, summarizing, notifying. You focus on the synthesis.

For solo founders, the weekly-digest workflow alone justifies the setup time. You stop “saving and forgetting” because the digest forces you to look at what you saved and decide which items deserve action.

For teams, the routing patterns are useful: when a team member saves something about pricing, it lands in the team’s Notion table automatically. ContextBolt is single-user today, so this works best when the team uses n8n to consolidate from multiple ContextBolt accounts (each user runs their own MCP node and writes into a shared destination).

When n8n MCP is overkill

If you save fewer than ~10 items per week, n8n is too much machinery. Stick with the interactive Claude Desktop bridge or just use the ContextBolt extension popup directly.

If you don’t already use n8n, don’t adopt it just for this integration. Self-hosting n8n is non-trivial and n8n Cloud has its own learning curve. The MCP bridge through Claude Desktop covers most personal workflows.

Common questions.

Why use n8n instead of the Claude Desktop MCP bridge?

Claude Desktop is interactive: you ask, Claude does. n8n is unattended: workflows run on a schedule or trigger without you being present. Use n8n when you want recurring tasks (weekly digests, smart routing, scheduled audits) that should happen even when you're not at your machine.

Do I need to self-host n8n?

No. n8n Cloud works fine. Self-hosting gives you tighter control over MCP node installation and credentials, and avoids the n8n Cloud usage limits if your workflows run frequently. Both options support community nodes.

Is the n8n MCP node official?

It's a community node, not maintained by n8n itself. Quality is generally good but watch the GitHub repo for updates. If the node breaks after an n8n upgrade, check whether a new version has been published before relying on it for production workflows.

What's the rate limit on ContextBolt's MCP server?

Pro accounts get reasonable limits for personal use: hundreds of search calls per day. If you build a workflow that hammers the server (e.g. polling every 30 seconds), you'll hit throttling. Schedule sensible intervals (every 15+ minutes is usually fine for personal automation).

Can n8n write to my ContextBolt collection?

Yes, as of the May 2026 server update (v1.2.0). The MCP server added a save_bookmark tool alongside the four read tools, so a workflow can create new bookmarks: pass a URL and the content, plus optional title, author, and tags. The read tools (search, clusters, recent) are unchanged, and there is still no way to edit or delete existing bookmarks, so a misfiring workflow can add saves but can't modify or wipe your library. You can also still capture through the browser extension as normal.

Go deeper: ContextBolt in Claude Desktop · ContextBolt in Notion · ContextBolt in ChatGPT · How to Turn Your Bookmarks into a Second Brain · What Is MCP? AI Protocol Explained · all integrations

Give your AI
your library.

Free up to 150 bookmarks. Pro adds the AI connection, unlimited bookmarks, export and sync, for $6 a month.

Add to Chrome See everything ContextBolt does