You might have seen memes saying that if you receive an email with perfect grammar, punctuation, and clean formatting, it was probably written by AI. As much as this pains me as a writer whose career depends on writing, I'm well aware that one of the biggest use cases of AI since the day OpenAI publicly launched ChatGPT in 2022 remains surface-level tasks like writing emails.

Now, I'm not one to say that there's anything wrong with that. However, a lot has changed between November 2022 and today. LLMs have gotten exponentially smarter, the number of tools we have access to has exploded, and the way these models can interact with our systems has fundamentally shifted. That’s exactly why connecting Claude to my local files and tools completely changed how I use it.

AI tools can now actually do things for you

The days of it just writing your emails are over

For a fairly long time (at least long in the context of how fast AI moves), the way public-facing AI tools worked was you'd ask a question, and they'd spit out an answer. Want to write an email? Open your inbox, copy the email, paste it into an AI chatbot's window, wait for a response, copy the response, and then head back to your inbox to paste the response.

Now, the difference is that AI tools can directly jump between tools and actually take action for you. The first time the majority of users experienced this firsthand was with agentic AI browsers. I've been testing these agentic workflows since the beginning, and the vast majority of them felt… very disconnected. The outputs were often disappointing, you'd need to constantly step in, and the whole experience just felt frustrating.

Claude's implementation is the only time that connecting it to my external tools has actually made a meaningful difference.

Claude Cowork lets it access all your local files

No more uploading files one by one into a chat window

You know how an assistant you hire makes sure all your files are organized and aren't a disaster at all times? When I think of a digital assistant, that's exactly the kind of tasks I'd want it to handle. Rather than simply telling me how to do it, I'd want it to go ahead and organize my chaotic downloads folder, clean up my overflowing desktop, or sort through months and months worth of files I've been meaning to organize. These are exactly the kind of tasks Claude Cowork can handle.

Cowork is a Claude feature that's currently available as a research preview for paid plans. It brings Anthropic's viral developer feature, Claude Code's, agentic capabilities to non-technical users who aren't comfortable working within a terminal environment. The feature essentially lets you describe anything you'd like to do, and then Claude completes the work for you automatically.

Cowork runs directly on your computer, meaning you can give it direct access to your local files. When a task is underway, Claude clearly breaks it down into sub-tasks and then displays its progress in a step-by-step view so you can follow along and see exactly what it's doing at every stage. It also explicitly asks for your permission before permanently deleting any files.

While it hasn't been too long since Claude launched Cowork, it's quickly turned into my favorite feature. I regularly use it to organize my laptop, and it never fails to deliver. More impressively, I recently used it to free up over 60 GB of storage! I've had this MacBook for over 3 years now, and I've not once bothered to clean it up myself. This is exactly the kind of task I'd have outsourced to an assistant. Now, I finally can!

You can also use Cowork to do all sorts of file management tasks like renaming thousands of files with consistent formatting, converting files in bulk, scanning through your documents to find and flag duplicates, and more. It’s also an excellent way to find patterns and connections across all your documents, and query them without having to manually open and sift through everything yourself.

Connecting Claude to your daily tools takes it to another level

No more copying and pasting between five tabs

Beyond using Cowork to connect Claude to your local files, there are a few ways you can connect the tool to the tools you rely on daily. This includes Connectors, MCP servers, and the Claude in Chrome extension. I believe Connectors are the simplest route since they only take a few clicks to set up.

Connectors are pre-built integrations vetted by Anthropic that let Claude connect directly to tools like Gmail, Google Calendar, Notion, Slack, Figma, Canva, and more. Once you've authenticated the tool and granted the necessary permissions, Claude can directly retrieve information from the respective tool and even go ahead and make changes. For instance, I regularly ask Claude to go through my email inbox, find press releases I've received recently, and organize them into my Notion database.

Depending on the tools you use daily, these integrations let you do a range of tasks using natural language. You could ask Claude to check your Google Calendar for scheduling conflicts and move meetings around depending on availability, summarize your Slack messages, and whatnot. The point is that you're describing what you want done in plain English, and Claude handles the back-and-forth between tools.

MCP servers are another excellent way to fit Claude right into your workflow. While Anthropic officially has Connectors for a lot of tools, there are thousands more that don't have one yet. MCP servers solve that. MCP is an open standard that lets anyone build a connection between Claude and a third-party tool. For instance, Claude doesn't have a Connector for NotebookLM, so I found an MCP server for the tool on GitHub. Once they're set up, they work just like Connectors and allow Claude to read data from the tool and interact with it directly.

Stop using AI just like a chatbot

The days of using AI as a Google Search replacement are long, long gone. With features like Cowork and Connectors, AI has turned into something that can actually go ahead and take repetitive tasks off your plate and do them for you. So, if you aren't exploring such workflows, you're leaving a lot on the table.