5 Personal Data Sources to Connect to Claude

Ask Claude a question and you get a smart, technically correct answer. Ask it a question about something you have been researching for six months, and you get the same smart, technically correct answer.

The problem is not capability. Claude knows a lot. The problem is that it does not know what you know.

Every conversation starts blank. No memory of the posts you have saved. No awareness of the documents you have written. No access to the decisions you have made or the topics you have been tracking for months. Generic input, generic output.

The Model Context Protocol (MCP) is the practical fix for this. It is an open standard created by Anthropic and now adopted by every major AI provider, including OpenAI, Google, and Microsoft. It lets you connect external data sources to AI tools once, and Claude can pull from them mid-conversation whenever relevant. No copy-pasting. No re-explaining context you have already explained.

The question is which data sources are actually worth connecting.

Not all personal data is equally useful as AI context. Some sources are dense with signal. Others are noise. This guide covers the five that are worth the setup time, starting with the most overlooked.

1. Your social bookmarks

This is the one most guides skip entirely. It is, in my view, the single most underrated personal data source you can add to Claude.

Every time you bookmark a tweet, save a Reddit post, or save a LinkedIn article, you make an active decision. You are saying: this is worth keeping. That signal is genuinely rare in a world where most content is passively scrolled past.

Your notes contain things you wrote. Your calendar contains appointments. But your bookmarks contain things you decided were worth saving from the stream of content you consumed. Over months and years, that collection becomes a curated knowledge base built around your actual interests and work areas.

The problem is accessing it. X added bookmark search in July 2024, but users report it is unreliable and frequently misses exact keyword matches. Reddit has no search at all for saved posts and enforces a hard 1,000-post cap before silently deleting the oldest saves. LinkedIn has no search for saved content whatsoever.

So the data exists. It is locked away.

ContextBolt is built specifically to fix this. Install the Chrome extension, visit your X bookmarks page once, and it intercepts the API responses that power that page and captures the full content of each bookmark. Reddit saved posts are captured automatically via a content script when you visit your saved content. LinkedIn saves are captured via an injected save button or a one-time bulk CSV import.

Every captured bookmark gets AI-tagged with a main topic and specific keywords, assigned by Claude Haiku during ingest. You get topic-clustered filtering in the extension dashboard and semantic search across your full collection by meaning, not just keywords.

Pro users (£4/month) get a personal MCP endpoint with four tools: search bookmarks by meaning, list all your topic clusters, retrieve bookmarks from a specific topic, and get your most recent saves.

Connect that endpoint to Claude Desktop or Claude Code and you can ask “what have I saved about pricing strategy?” and get an answer drawn from the specific content you curated over months, not from what the internet generally says about pricing.

The difference between those two answers is significant.

2. Your notes and documents

This is the source most people think of first, and rightly so. Your notes hold your thinking. Your documents hold your decisions, your research, and your processes.

If you use Notion, Notion’s official MCP server is available through Claude Desktop’s built-in Connectors menu. No JSON editing, no terminal. Open Settings in Claude Desktop, go to Connectors, add Notion, complete the OAuth flow. Under two minutes.

Once connected, Claude can search your pages and databases, retrieve specific documents, and read content from your workspace. When you ask about a project you have been working on, it can pull the relevant Notion pages before answering rather than asking you to describe what you have already written.

For Obsidian users, a community MCP server exists for local vaults. For Google Drive, the Connectors menu handles that too. For local files on your machine, the Filesystem MCP server ships bundled with Claude Desktop and gives Claude read access to whichever folders you specify.

The key question to ask yourself is: where does my most important active working knowledge actually live? Start with that source, not the neatest-looking one.

3. Your calendar

Knowing what you know is one layer of context. Knowing when you are is another.

A calendar-connected Claude can give you answers that account for your actual schedule. “How long will this realistically take?” becomes answerable against real availability rather than in a vacuum. “What should I prepare for tomorrow?” becomes a question it can address from your actual agenda rather than a generic template.

Claude Desktop’s Connectors menu includes Google Calendar as a built-in option. Setup takes under two minutes. You authorise read access, pick which calendars to include, and Claude can see your schedule from that point forward.

The most useful cases are meeting preparation and workload planning. Ask Claude to help you prepare for a meeting it can see on your calendar and it has something concrete to work with. Ask it whether you have bandwidth for a new project this week and it answers from actual data rather than asking you to describe your schedule.

Read-only access is enough for most of what makes this useful. Claude does not need to create calendar events to give better advice.

4. Your email inbox

Email is where real decisions live. Your inbox contains the actual conversations behind the things you are working on, the commitments you have made, and the threads that need following up.

Claude connected to Gmail can read threads, summarise long email chains, and draft replies in context. Not “draft a professional follow-up email about a project review” but “draft a follow-up to the conversation with Sarah about the Q3 budget discussion from last Tuesday.”

The Connectors menu in Claude Desktop handles Gmail alongside Google Calendar. The same OAuth flow, the same setup time.

One limitation worth knowing upfront: email is high volume and often low signal. Connecting your inbox adds a large amount of data, some of which is noise. The biggest wins come from specific threads where you need full context before drafting a reply or making a decision. A focused “summarise this thread” request outperforms “tell me about my emails this week” for most people.

5. Your project files

If you write code, your codebase is the highest-signal data source you own. Claude connected to a GitHub repository can read the actual code before suggesting changes, review pull requests with full context, and give advice grounded in what the codebase actually contains rather than generic best practices.

If you do not write code, local files still add clear value. The Filesystem MCP server lets you point Claude at a folder of documents, reports, or spreadsheets. When you ask it to help edit or analyse something, it reads the actual file rather than working from whatever you paste into the chat.

Setup for local files involves a small JSON edit: add the Filesystem server to your Claude Desktop configuration file and specify which paths to allow. Claude can then read anything in those paths. No coding required, and the Claude Desktop setup guide walks through it in under five minutes.

How the five sources compare

How to pick where to start

Do not connect all five at once. More sources add noise before they add signal. Claude has to decide which source is relevant to each question, and that decision gets harder when everything is connected simultaneously.

The right approach is sequential.

Pick the source that holds your most active, highest-stakes knowledge today. If you work in code, start with filesystem or GitHub. If you are a knowledge worker, start with Notion or Google Drive. Connect it and use it for two weeks before adding anything else.

Add your bookmarks early, regardless of what else you start with. This is the one case where timing matters more than sequence. Bookmarks accumulate passively once ContextBolt is installed. A collection built over four weeks is meaningfully more useful than one you start building after four weeks of delay. The time to start is now, not after you have set up everything else.

Calendar and email add the most value for specific tasks: scheduling, meeting preparation, drafting context-aware replies. They are not as universally high-signal as notes and bookmarks. Add them once your first source is working reliably.

Why this matters

Context engineering is the skill of shaping what an AI agent knows before it answers your question. The right context turns a generically capable model into a tool that feels like it actually understands your work.

None of these five sources requires technical knowledge to set up. The most involved is bookmarks, and that takes less than five minutes with ContextBolt installed and the MCP endpoint configured.

The difference in answer quality is real. Generic Claude is impressive but impersonal. It draws on vast training data and gives you statistically common answers. Context-connected Claude draws on your documents, your schedule, your research. The answers reflect your specific situation rather than the average situation.

That is the version worth building toward. One source at a time.

ContextBolt captures your X/Twitter, Reddit, and LinkedIn bookmarks automatically via a Chrome extension and stores the full content locally on your device. Free tier includes 150 bookmarks with AI tagging, topic clustering, and semantic search. Pro (£4/month) adds unlimited bookmarks, encrypted cloud sync, and a personal MCP endpoint so your entire curated collection is searchable inside every Claude conversation.