ContextBolt in VS Code + Continue · 3 minutes · Beginner

VS Code Continue MCP for Bookmarks (2026 Setup, 3 min)

Three minutes in Continue, and VS Code can search everything you saved.

Add to Chrome
Free extension · the AI connection is on Pro, $6/mo
Bookmarks MCP server for Claude, Cursor & Codex VS Code + Continue · 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 3 minutes.

  1. Connect your ContextBolt account Open the VS Code Extensions panel and install 'Continue', the open-source AI coding assistant. Continue supports MCP servers natively, so it can talk to ContextBolt directly. If you already use Continue, skip this step. 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: Add ContextBolt to Continue's config Open Continue's config file (Cmd/Ctrl+Shift+P then 'Continue: Open config.yaml'). Under mcpServers, add ContextBolt as a remote HTTP server pointing at https://api.contextbolt.app/mcp/YOUR_TOKEN. Save and reload VS Code. Older Continue versions on config.json need the mcp-remote npm bridge instead, covered in the FAQ.
  4. Personal-URL setup: Test the connection Open the Continue chat sidebar and ask 'Search my bookmarks for anything about API design'. Continue should call the ContextBolt MCP tool and return matching saves. If nothing happens, check the Continue logs panel for connection errors.

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

Then ask it something real.

“I'm refactoring this auth module. What did I save about session handling and JWT pitfalls?” Pull saved technical reference material into a refactor session. Continue searches semantically, so saved threads with different terminology (sessions, tokens, auth flows) all surface.
“Find my Reddit saves about Postgres performance tuning.” Reddit threads are often deep technical discussions. Filtering by platform brings back the long-form content rather than tweet-sized takes.
“I need to understand how others handle webhook retries. Search my bookmarks.” Use ContextBolt as a curated alternative to Stack Overflow. Your bookmarks are filtered for relevance once already, by you saving them.
“Pull all my saves about React server components from the last 3 months.” Time-boxed search. Useful for catching up on a topic you've been bookmarking but haven't sat down to read yet.

What it can do in VS Code + Continue.

  • Search bookmarks from the Continue sidebar in VS Code
  • Pull saved threads, articles, and discussions into chat context
  • Filter by source (web pages, Twitter/X, Reddit, LinkedIn) or keyword
  • Combine bookmark search with Continue's code understanding
  • Works in any VS Code-based editor (Cursor, VSCodium, GitHub Codespaces)
  • Save new bookmarks or search existing ones (no editing or deleting from the editor)

The longer story.

Continue is the open-source AI coding assistant for VS Code. It speaks MCP natively, so adding ContextBolt is one config change away from full bookmark search inside your editor.

Why this combination works

Most coding sessions involve looking things up. Library docs. Stack Overflow threads. That tweet someone posted about a clever pattern you saved last month. The looking-up pulls you out of flow.

Developers who save technical content end up with a personal reference library: the docs page that finally explained it, plus the threads and Reddit posts from Twitter, Reddit and LinkedIn. The problem is that this library lives in a browser tab while you’re coding in an editor. Every reference check is a context switch.

The Continue + ContextBolt integration kills that switch. Your saves are queryable from the same sidebar where you’re already chatting with Claude, GPT, or whichever model Continue is configured to use.

The VS Code + Continue MCP setup

Use https://api.contextbolt.app/mcp and complete the browser sign-in if your client supports remote MCP with OAuth. Enter your Pro account email and email code, then allow the connection. For a client that cannot complete that flow, use the personal-URL compatibility configuration shown here. Copy the full private URL from the extension under Settings, MCP Integration, Older clients and replace the example URL with it.

Three minutes if Continue is already installed. Open config.yaml (Continue: Open config.yaml in the Command Palette) and add the bookmarks server, replacing the entire https://api.contextbolt.app/mcp/YOUR_TOKEN example with your private URL from Settings → MCP Integration. Newer versions keep it under Older clients. Add the bookmarks server as shown.

mcpServers:
  bookmarks:
    type: http
    url: https://api.contextbolt.app/mcp/YOUR_TOKEN

Save, reload VS Code, open the Continue sidebar. Ask Continue to search your bookmarks. If the MCP connection is healthy, results appear inline in the chat. We tested this against Continue’s current and previous minor versions; the older one needed the mcp-remote bridge in the FAQ rather than the direct URL field.

VS Code + Continue MCP workflow patterns that earn the setup time

Reference lookups during refactors: “Search my bookmarks for anything about migrating from REST to gRPC.” Continue surfaces saved threads, articles, and Reddit posts on the topic without you opening a browser tab.

Pre-flight reading for new tasks: Before starting a task, ask Continue what you’ve saved about the area. You’ll often find you already collected the right reference material weeks ago.

Combining code context with saves: Continue understands the file you have open. Combine that with bookmark search: “I’m working on the rate limiter in src/middleware/. Do I have any saves about token bucket vs leaky bucket?”

When you wouldn’t use VS Code + Continue with MCP

If you never save anything worth coming back to, the integration adds nothing. ContextBolt earns its place when you’re actively saving docs pages, threads and posts as you browse Twitter or Reddit during downtime.

If you prefer command-line workflows, Claude Code gives you the same access from the terminal. Pick the surface that matches where you actually work.

Common questions.

Does this work in Cursor or VSCodium?

Yes. Cursor is built on VS Code and supports the Continue extension. VSCodium and GitHub Codespaces also work. The setup is identical: install Continue, add the ContextBolt MCP server to Continue's config. We have a dedicated Cursor integration page if you'd rather use Cursor's native MCP support directly.

Can Continue modify my bookmarks?

Continue can't modify or delete your bookmarks. As of the May 2026 update the server exposes a save_bookmark tool, so Continue can create new bookmarks in addition to searching and retrieving them. You can still save through the Chrome extension as normal; nothing in your existing library gets edited or removed.

What's the difference between Continue and Cursor's built-in chat?

Continue is open source and works in vanilla VS Code or any VS Code fork. Cursor has its own AI features built in. Both speak MCP. Use Continue if you want a free, model-flexible setup. Use Cursor if you prefer the native experience and don't mind paying for it.

Can I use my own LLM provider?

Yes. Continue supports OpenAI, Anthropic, Google, local Ollama models, and others. The ContextBolt MCP server is provider-agnostic: it works with whichever model Continue is configured to use, as long as the model supports tool calling.

How do I troubleshoot if the MCP connection fails?

Open Continue's logs panel (View > Output > Continue) and look for MCP-related errors. Three common causes: the extension is not on Pro, or its first sync has not finished (sync runs on its own once Pro is active); the token in the URL has been regenerated and the old one is still in the config (paste the latest from the extension settings); or your Continue version predates remote HTTP support, in which case use the mcp-remote bridge.

What if my Continue version doesn't support remote HTTP servers?

Use the mcp-remote npm bridge. Set "command": "npx" and "args": ["mcp-remote", "https://api.contextbolt.app/mcp/YOUR_TOKEN"] in Continue's config. The bridge runs locally and proxies requests to the hosted endpoint. Updating Continue removes the need for this.

Go deeper: ContextBolt in Cursor · ContextBolt in Claude Code · ContextBolt in Cline · Add Your Bookmarks to Claude Code via MCP · 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