C.W.K.
Stream
Lesson 06 of 08 · published

MCP Connectors — Pull Data In, Push Results Back

~14 min · cowork, mcp, notion, slack, google-drive

Level 0🌱 Novice
0 XP0/70 lessons0/11 achievements
0/120 XP to next level120 XP to go0% complete

Same MCP, different center of gravity

MCP in Cowork is structurally identical to MCP in Claude Code — same servers, same transports, same scopes. The difference is workflow. In Code you connect to GitHub, Sentry, Postgres for code-shaped jobs. In Cowork you connect to Notion, Google Drive, Slack, Linear, Airtable for content-shaped jobs.

The high-leverage Cowork MCP pattern is read → analyze → write back. Pull a Notion database into the working folder, run analysis on the local copy (cheap, fast, audit-able), then push results back via the same MCP — update properties, post comments, change statuses. The local round-trip is your audit trail; the remote is your system of record.

Code

Connect three Cowork-relevant servers·bash
# In a terminal (config persists for Cowork too)
claude mcp add --transport http notion  https://mcp.notion.com/mcp
claude mcp add --transport http gdrive  https://mcp.drive.google.com/mcp
claude mcp add --transport http slack   https://mcp.slack.com/mcp

# In Cowork (or Claude Code), authenticate OAuth ones:
/mcp
Read → analyze → write back·text
# Goal in Cowork:
"Read the product-feedback database in our Notion workspace.
 Process all 'Status: New' entries from the past 30 days.
 Categorize by theme and severity. Write
 /output/feedback-triage-2026-05.md. Then update the Status
 field on each processed item to 'Triaged' and set Team Tag."

# Cowork's execution:
# 1. MCP read  → local copy in /working/notion-snapshot.json
# 2. Analyze   → /output/feedback-triage-2026-05.md
# 3. MCP write → batch-update Status + Team Tag in Notion

External links

Exercise

Connect one read+write MCP server (Notion or Linear). Run a Cowork task that pulls some records, processes them, and writes results back. Verify the source-of-truth update happened cleanly. Save the local snapshot in /working/.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.