Plug Claude Into the Rest of Your Stack

A Claude with no connectors is a very smart person locked in a room with no windows.

You can slide notes under the door all day. It will write you excellent replies about a business it has never seen. The upgrade happens when you hand it keys to the rooms where your work actually lives, and that upgrade takes about twenty minutes.

What MCP is, in one breath

The bridge is called MCP, which stands for Model Context Protocol. It's basically a standard plug that lets Claude read (and, if you allow it, write to) the apps you already use: email, calendar, project management, CRM, design files. Anthropic built it, other AI tools adopted it, and you never have to think about the acronym again after this paragraph.

Step 1: Connect where the work lives

Open Claude, go to Settings, then Connectors. You'll see a directory of tools you can add.

Mine are Gmail, Google Calendar, Google Drive, ClickUp, Figma, and Slack. Those six cover about 95% of how L12 actually runs. If your stack is Outlook, Notion, and Asana, connect those instead. The principle is the same: connect the tools where the real work lives, not the ones that look impressive.

Three connectors is plenty for week one. Email, calendar, and wherever your tasks live. Add more when you notice Claude guessing about something a connector would let it check.

Step 2: Set permissions like a manager, not a fan

When you grant access, Claude asks for read or write permission per tool. This is the part people click through, and it's the part that matters most.

• Keep most tools read-only. Claude can see your calendar without being able to move your meetings.
• Give write access only where you want drafting. For me that's email and Slack. Claude drafts, I review, I send.
• Never auto-send. The point of having an assistant is that you stay in the loop on what leaves the building.

Step 3: Run the three weekly prompts

Connectors are plumbing. These three prompts are the water. All three used to cost me real hours.

Morning email triage. Every morning Claude runs this: "Go through my inbox. Flag what needs my attention. Archive the junk. Draft replies to anything I owe a response on, but don't send." I review the drafts, edit the ones that need it, and send the rest. Roughly an hour back per day.

The cross-tool weekly digest. Once a week: "Summarize my Slack, email, and ClickUp from the last week. What's the team working on? What's blocked on me? What's slipping?" This is the read I wish I could write for every founder I know. Visibility without the meeting.

Sunday planning. Before the week starts: "Go through my calendar for the week, my outstanding ClickUp tasks, my unread Slack, and my flagged email. Tell me what should be on my plan, where to put focus time, and which meetings I should cancel or hand off." I review, decide, and ship the week.

Copy these verbatim, swap in your tools, and adjust after a week of watching what comes back.

The one rule

Garbage in, garbage out. Claude is a context machine, and the connectors decide what context it gets. A Claude wired into a chaotic inbox and an abandoned project board will faithfully summarize chaos.

So do one honest pass first: archive the dead email, close the stale tasks, name the channels something a stranger could parse. Twenty minutes of cleanup makes every prompt above noticeably sharper.

Then let it read the room you just cleaned.