Three Ways to Let Cowork Read Your Calendar and Inbox: Connector, Claude in Chrome, or a File Export, Tried Narrowest First
There are three ways to let Cowork read a calendar or inbox: a connector, Claude in Chrome, or a file export. I choose by how little each one can touch, and I'll share the prompt template I hand over.
I Sorted 32 Connector Tool Names Into Read, Write and Delete — Four Wouldn't Sort by Name
I wrote a small script that sorts the tool names of my Cowork connectors into read, write and delete by verb. The first pass left nine undecided, the fix left four, and here is how I now set approvals.
When a Connector Starts Slowing Down at Night: A Health-Aware Circuit Breaker for Solo Automation
Seeing connector errors and latency is only half the job — the other half is deciding when to route around them. This is my implementation of a circuit breaker that opens on error rate and p95, with runnable Python and notes on wiring it into nightly jobs.
A connector failed for two nights and I never noticed — instrumenting my solo setup after observability went to public beta
The week connector observability hit public beta, I realized my one-person operation had no view into errors or latency. Here is how I wrapped my MCP connector calls in a thin meter and started reviewing it weekly.
Keep MCP Connector Authorization in One Place — A Solo Dev Design That Survives Growing Integrations
When Claude chat, Claude Code, and Cowork each configure the same MCP connector separately, their authorization drifts apart and breaks silently. Here is how to borrow the managed-connector idea of 'provision once, reuse everywhere' as an indie developer.
Connect Cowork Connectors by Separating Read Access from Write Access
A practical first pass at Cowork connectors for Canva, Figma, Slack, Asana, Google Drive and GitHub: how to connect, how MCP Apps differ, where I draw the line between reading and writing, and when Claude in Chrome is the fallback.