Disclosure up front: I work at Slashy. This is about an MCP server we ship, so flag as self-promo if that’s the rule. TL;DR — wired Claude Code into my real inbox, calendar, and people-research stack through one MCP server. It drafts/sends/schedules email, books and reschedules meetings, and pulls LinkedIn + last-thread context before a call. No copy-paste, no API keys. Slashy Email Client MCP, OAuth 2.1 with PKCE, free to try, also works in Claude Desktop, Cursor, Codex. Why I did this Same dumb loop probably 20x a day — ask Claude Code to draft a reply in the terminal, copy it into Gmail, jump to Calendar to check if I’m even free, alt-tab to LinkedIn to remember who the person actually is, come back, send. Claude Code had all the language, none of the context, and zero ability to actually do anything to my week. Felt absurd that a thing reasoning about my repo couldn’t see my inbox. So I stopped treating Claude Code as just a coding agent and gave it the rest of my desk. What it actually does Once the MCP is connected, in plain chat:
- Email — draft, send, reply, schedule-send, label, attach files, all on my real account
- Calendar — create events, check availability, propose meeting times that don’t collide
- Research — enrich a lead with LinkedIn / company / recent news, and pull attendee profiles + prior email history before a meeting
- Scheduled workflows — “every Monday 8am, summarize unread from these people” becomes a standing trigger, not a thing I rerun Not an autopilot. It drafts and proposes, I approve. The judgment stays with me — it just kills the tab-switching tax. The part I didn’t expect to work Meeting prep. “what’s my 2pm and who am I talking to” → calendar event + the attendee’s background + our last email thread, in one answer, before I’ve opened a single tab. That single move is most of why I haven’t gone back. The bit that compounds — memories This is the one I didn’t get at first. Slashy MCP has a memory store Claude can read from and write to across sessions. So things like “Sarah’s my CFO, always loop finance@ on revenue threads,” “drafts to investors stay short and lowercase,” “auto-archive anything from that one vendor that won’t stop emailing” — I tell it once and it just keeps doing it. No prompt scaffolding, no rules file I have to maintain. A week in, my drafts started sounding like me without me feeding it samples each time. A month in, it knew enough about who’s who in my world that “draft a reply to that thread from the design lead” worked without me clarifying which design lead. The email/calendar tools are the headline, but memories are why I haven’t churned. Quick start OAuth 2.1 with PKCE, no API keys to paste. Claude Code is a single claude mcp add then a browser login. I also dropped the Slashy skill/rules file in so Claude Code reaches for it automatically whenever I mention email, calendar, research, or scheduling — instead of me naming the tool every time. That’s the bit that made it actually stick day-to-day. Where it is Overview + setup: https://help.slashy.com/how-to-guides/slashy-mcp-overview Happy to answer anything about the trigger/scheduled-workflow setup, memories vs. CLAUDE.md / a static rules file, how the OAuth flow feels vs the API-key MCPs, or the auto-skill trick that makes Claude Code pick the right tool unprompted. Roasts welcome. submitted by /u/penguinothepenguin
Originally posted by u/penguinothepenguin on r/ClaudeCode