你的上下文大多不在对话框里 —— 在 Gmail、Drive、Slack、Notion、Linear。这一章你只连一个（连之前先想清楚它能看到什么），然后问一个必须跨源才答得了的真问题，最后回去看一眼它现在能看到你哪些东西。Most of your context isn't in the chat box — it's in Gmail, Drive, Slack, Notion, Linear. Here you connect exactly one (after deciding what it may see), ask a real question that can only be answered across sources, then go back and look at what it can now see of yours.
你的上下文大多不在对话框里。它在你的 Gmail、Drive、Slack、Notion、Linear 里 —— 你每次都得先去那边复制一段，再回到 Claude 粘上。Connectors 就是为了省掉这一趟。Most of your context isn't in the chat box. It's in your Gmail, Drive, Slack, Notion, Linear — and each time you go copy a chunk there and paste it back into Claude. Connectors exist to save that trip.
— I
背后是 MCP，前面是两条路MCP Underneath, Two Roads on Top.
连接器让 Claude 直接读你别处的数据，不用你来回搬。Connectors let Claude read your data elsewhere, without you shuttling it back and forth.背后是 MCP，一个把 AI 接到「数据所在系统」的开放标准。1注 1Note 1Anthropic · Introducing the Model Context Protocol —— MCP 是连接 AI 与数据所在系统的开放标准，Connectors 即建立在它之上。Anthropic · Introducing the Model Context Protocol — MCP is the open standard for connecting AI to where data lives; Connectors are built on it.你不必懂协议 —— 在连接器目录里浏览、连上一个应用，Claude 之后就能直接读它；每个条目都标了它能读什么、能写什么。3注 3Note 3Claude 帮助中心 · 预置网页连接器 —— 可连接的应用在连接器目录（Connectors Directory）浏览，每个条目标明读写能力与可用范围；Team / Enterprise 的 Owner 可以按动作限制某个已连服务在全组织内能做什么，也能把经过域名验证的连接器限定给企业账号。截至 2026-08。Claude Help Center · Pre-built web connectors — browse connectable apps in the Connectors Directory, where each entry lists its read/write capabilities and availability; Team / Enterprise Owners can limit which actions a connected service may take across the organization, and can restrict verified-domain connectors to enterprise accounts. As of 2026-08.Underneath is MCP, an open standard that wires AI to the systems where data lives.1注 1Note 1Anthropic · Introducing the Model Context Protocol —— MCP 是连接 AI 与数据所在系统的开放标准，Connectors 即建立在它之上。Anthropic · Introducing the Model Context Protocol — MCP is the open standard for connecting AI to where data lives; Connectors are built on it. You don't need the protocol — browse the Connectors Directory, connect an app, and Claude can read it directly afterward; every entry lists what it can read and what it can write.3注 3Note 3Claude 帮助中心 · 预置网页连接器 —— 可连接的应用在连接器目录（Connectors Directory）浏览，每个条目标明读写能力与可用范围；Team / Enterprise 的 Owner 可以按动作限制某个已连服务在全组织内能做什么，也能把经过域名验证的连接器限定给企业账号。截至 2026-08。Claude Help Center · Pre-built web connectors — browse connectable apps in the Connectors Directory, where each entry lists its read/write capabilities and availability; Team / Enterprise Owners can limit which actions a connected service may take across the organization, and can restrict verified-domain connectors to enterprise accounts. As of 2026-08.顺手分清两类，免得混淆。网页连接器（远程 MCP）跑在对方服务器上、跨客户端通用，你在 Claude、Cowork、桌面端和手机上连的是同一个；桌面扩展（本地 MCP）装在 Claude 桌面端、跑在你这台机器上，能碰本地文件和工具 —— 权限更深，也更该谨慎。5注 5Note 5Claude 帮助中心 · 桌面扩展与网页连接器怎么选 —— 网页连接器是远程 MCP，跨客户端通用；桌面扩展是本地 MCP，装在 Claude 桌面端、跑在本机，能碰本地文件与工具。截至 2026-08。Claude Help Center · When to use desktop and web connectors — web connectors are remote MCP, shared across clients; desktop extensions are local MCP, installed in Claude Desktop and running on your machine, able to touch local files and tools. As of 2026-08.这一章讲前者；后者用同一把尺子（能只给读就别给写），但风险更高。One pair worth keeping straight. A web connector (remote MCP) runs on the provider's servers and is shared across clients — what you connect in Claude, Cowork, desktop, and mobile is the same one. A desktop extension (local MCP) installs into Claude Desktop and runs on your own machine, able to touch local files and tools — deeper access, more to be careful about.5注 5Note 5Claude 帮助中心 · 桌面扩展与网页连接器怎么选 —— 网页连接器是远程 MCP，跨客户端通用；桌面扩展是本地 MCP，装在 Claude 桌面端、跑在本机，能碰本地文件与工具。截至 2026-08。Claude Help Center · When to use desktop and web connectors — web connectors are remote MCP, shared across clients; desktop extensions are local MCP, installed in Claude Desktop and running on your machine, able to touch local files and tools. As of 2026-08. This chapter is the former; the latter takes the same ruler (grant read-only when you can) at higher stakes.
— II
动手：连一个，然后验一次Do It: Connect One, Then Verify It.
连接器的清单很长，值得你连的没几个。The connector list is long; the ones worth connecting are few.
01
列出你每天都翻的三个数据源，只连最信任的那一个List the three sources you check daily, connect only the one you trust most
多半是 Gmail / Google Drive，或者 Slack、Notion、Linear 这类你整天开着的。别一上来把目录连满 —— 每连一个数据源，就多一份权限、多一处它能看到的东西。Free 档自定义连接器限 1 个，这反而是个好默认。Usually Gmail / Google Drive, or the Slack, Notion, Linear you keep open all day. Don't fill the directory on day one — every source you connect adds a permission and one more place it can see. Free allows one custom connector, which turns out to be a good default.
02
连之前，先在目录页读清它能读什么、能写什么Before connecting, read what it can read and what it can write
连接器不只是只读 —— 它既能读，也能写回：在 Linear 建 issue、在 Slack 发消息都行。连之前就该看清是「读」还是「读写」。能只给读的场景，就只给读。Connectors aren't read-only — they read and also write back: open a Linear issue, send a Slack message. Know which before you connect. Where read-only is enough, grant read-only.
03
问一个必须跨源才答得了的真问题Ask a real question that can only be answered across sources
这一步是验收，别用「帮我看看今天的邮件」这种 —— 那不需要跨源。要问的是「某客户这季度在邮件和文档里答应过什么」这类：答案不在任何单一一封邮件里，必须跨着找、还要合起来。This is the verification step, so don't use 'summarize today's email' — that doesn't span anything. Ask something like 'what did this client commit to across email and docs this quarter': the answer isn't in any single message, so it has to search across and then combine.
04
抽查两条出处，然后回去看权限Spot-check two sources, then go look at the permission
点开它给的两条出处，确认确实支持那句话。然后回 Customize > Connectors，看一眼它现在能看到你哪些东西 —— 这一眼很多人从来没看过，而它是这一章真正的产出。Open two of the sources it cited and confirm they support the sentence. Then go back to Customize > Connectors and look at what it can now see of yours — a glance most people never take, and the real deliverable of this chapter.
提示词Prompt跨源取数 · 本章要存下的句式Cross-source retrieval · the phrasing to keep
在我的<数据源 A>和<数据源 B>里找：<一个跨来源的问题>。
范围：限定<时间段 / 发件人 / 文件夹>，别翻无关的。
给我：<一句话结论 + 出处（邮件主题或文件名）>，每条能点回原件。
没找到的就说没找到，别用常识补 —— 我要的是这些源里真有的东西。
只读：别发信、别改文档、别建任务，除非我明说。In my <source A> and <source B>, find: <a cross-source question>.
Scope: limit to <a date range / sender / folder>; don't trawl the unrelated.
Give me: <a one-line answer + the source (email subject or file name)>, each clickable back to the original.
If you can't find something, say you couldn't — don't fill the gap from general knowledge. I want what's actually in these sources.
Read-only: don't send, edit, or create anything unless I say so.
在我的 Gmail 和 Drive 里找：Acme 这个客户在 Q2 的邮件和会议纪要里答应过哪些交付。
范围：限定 4–6 月、与 @acme.com 往来、以及 Drive 里「Acme」文件夹，别翻无关的。
给我：一句话结论 + 出处（邮件主题或文件名），每条能点回原件。
没找到的就说没找到，别用常识补 —— 我要的是这些源里真有的东西。
只读：别发信、别改文档、别建任务，除非我明说。In my Gmail and Drive, find: what deliverables the client Acme promised across Q2 emails and meeting notes.
Scope: limit to April–June, correspondence with @acme.com, and the 'Acme' folder in Drive; don't trawl the unrelated.
Give me: a one-line answer + the source (email subject or file name), each clickable back to the original.
If you can't find something, say you couldn't — don't fill the gap from general knowledge. I want what's actually in these sources.
Read-only: don't send, edit, or create anything unless I say so.
那句「没找到的就说没找到」是这段模板里最值钱的一行。连上数据源之后最危险的失败模式不是它读不到，是它用常识把读不到的那部分补得天衣无缝 —— 你看着一份「有出处」的答案，其中两条其实是它想出来的。The line 'if you can't find something, say you couldn't' is the most valuable one in that template. The dangerous failure mode after connecting a source isn't that it can't read something — it's that it patches the unreadable part from general knowledge so seamlessly you can't see the seam: you're looking at a sourced answer in which two claims were invented.
— III
让它动手：把动作说成命令Make It Act: Phrase the Action as a Command.
连了能写的连接器，就别只让它「建议」。Once you've connected a connector that can write, don't let it merely 'suggest.'把动作说成命令，它才真去做 —— 这正是第 2 章那套「说该做什么，别问能不能」。4注 4Note 4Claude API Docs · Prompting best practices —— 要它动手就把动作说成命令；别硬催工具（新版模型本就爱调工具，过度强调反而乱调）。截至 2026-08。Claude API Docs · Prompting best practices — phrase actions as commands to make it act; don't over-push tools (current models already lean toward tool calls, and over-emphasis misfires them). As of 2026-08.Phrase the action as a command and it actually acts — Chapter 2's rule again: state what to do, don't ask 'could you.'4注 4Note 4Claude API Docs · Prompting best practices —— 要它动手就把动作说成命令；别硬催工具（新版模型本就爱调工具，过度强调反而乱调）。截至 2026-08。Claude API Docs · Prompting best practices — phrase actions as commands to make it act; don't over-push tools (current models already lean toward tool calls, and over-emphasis misfires them). As of 2026-08.
只是建议Just a suggestion
你能不能在 Linear 里给这个 bug 建个 issue？Could you maybe open a Linear issue for this bug?
直接动手Just do it
在 Linear 的 Web 项目里建一个 issue：标题用这条报错，正文贴复现步骤，优先级 High。建完把链接给我。Open an issue in the Linear Web project: title it with this error, paste the repro steps in the body, priority High. Give me the link when it's done.
写操作的边界不该靠你每次记得说，该靠设置。Team / Enterprise 的 Owner 可以按动作限制某个已连服务在全组织内能做什么 —— 比如「可以搜索并总结邮件，但不能发信」「可以读 Google Drive，但不能新建或编辑文档」。2注 2Note 2Claude 帮助中心 · 预置网页连接器（remote MCP）—— 网页连接器对 Claude、Cowork、Claude 桌面端与移动端的全部用户开放；连接器可读可写（例如允许搜索并总结邮件但禁止发信、允许读 Google Drive 但禁止新建或编辑文档）；在 Customize > Connectors 查看权限、改设置或断开；自定义连接器 Free 档限 1 个。截至 2026-08。Claude Help Center · Pre-built web connectors (remote MCP) — web connectors are available to all users across Claude, Cowork, Claude Desktop, and mobile; connectors both read and write (for example, allow Claude to search and summarize email but prevent it from sending messages, or read Google Drive but not create or edit documents); review permissions, change settings, or disconnect under Customize > Connectors; Free is limited to one custom connector. As of 2026-08.个人账号没有这一层，所以你的写操作边界只能写在提示里；那就把它写进第 4 章那个 Project 的指令，别每次现打。The boundary on writes shouldn't depend on you remembering to say it each time — it should live in settings. Team / Enterprise Owners can limit, per action, what a connected service may do across the organization — 'search and summarize email but never send,' 'read Google Drive but never create or edit documents.'2注 2Note 2Claude 帮助中心 · 预置网页连接器（remote MCP）—— 网页连接器对 Claude、Cowork、Claude 桌面端与移动端的全部用户开放；连接器可读可写（例如允许搜索并总结邮件但禁止发信、允许读 Google Drive 但禁止新建或编辑文档）；在 Customize > Connectors 查看权限、改设置或断开；自定义连接器 Free 档限 1 个。截至 2026-08。Claude Help Center · Pre-built web connectors (remote MCP) — web connectors are available to all users across Claude, Cowork, Claude Desktop, and mobile; connectors both read and write (for example, allow Claude to search and summarize email but prevent it from sending messages, or read Google Drive but not create or edit documents); review permissions, change settings, or disconnect under Customize > Connectors; Free is limited to one custom connector. As of 2026-08. Personal accounts don't have that layer, so your write boundary can only live in the prompt — which means it belongs in the Project instruction from Chapter 4, not retyped every time.
— IV
换个域，先连哪一个Which One to Connect First, by Field.
先连云盘或笔记（Drive / Notion）。第一个跨源问题这样问：「我在 X 这个课题上，笔记里已经记过哪些结论，哪几条互相矛盾？」—— 这个问题只有跨越你所有笔记才答得了，而且矛盾那部分你自己心里有数，正好用来验它。别第一个连引用管理工具，那类问题太窄，验不出它的取数能力。Start with a drive or notes app (Drive / Notion). Ask this as the first cross-source question: 'On topic X, which conclusions have I already recorded in my notes, and which of them contradict each other?' — only spanning all your notes answers it, and you already have a sense of where the contradictions are, which is exactly what makes it a good test. Don't start with a reference manager; those questions are too narrow to test retrieval.
先连邮箱。第一个问题问「某个客户从第一封邮件到现在，报价变过几次、每次为什么」—— 答案散在十几封邮件里，你自己翻要二十分钟。验收标准很硬：报价的每一次变动都要能点回一封具体的邮件。这一栏是全书里连接器省时最明显的地方。Start with email. Ask: 'for this one client, how many times has the quote changed since the first message, and why each time' — the answer is scattered across a dozen emails and would take you twenty minutes by hand. The bar is hard: every change in the quote must click back to a specific message. This is the field where a connector's time saving shows up most clearly.
先连云盘，并且只给读。第一个问题问「这三个月的对账表里，哪些条目在两份文件之间对不上」。这一栏要特别小心一件事：财务类问题一旦让它「补全」，错误会以看起来很专业的形式出现。所以取数句式里那句「没找到就说没找到」在这一栏是必须的，不是可选的。Start with the drive, and grant read-only. First question: 'across these three months of reconciliation sheets, which line items disagree between the two files?' One thing needs extra care in this field: the moment you let it 'fill in' a financial gap, the error arrives wearing a very professional face. So the 'say you couldn't find it' line isn't optional here — it's mandatory.
先连团队沟通工具（Slack）或任务系统（Linear / Jira）。第一个问题问「上周有哪些事被提出来、但至今没有人认领」—— 这是管理者每周都在人肉做的事。它答完之后，你手上就有了一个每周可以重跑的句式；第 8 章会把这个句式挂上定时，变成一个每周一自动出现在你面前的清单。Start with team chat (Slack) or the tracker (Linear / Jira). Ask: 'what was raised last week that nobody has picked up since?' — the thing every manager does by hand every week. Once it answers, you're holding a phrasing you can re-run weekly; Chapter 8 puts that phrasing on a schedule so the list shows up in front of you every Monday on its own.
四个「第一个该连的」建议。共同点：都选那个你每天都要打开、并且里面的东西你已经很熟的源 —— 熟悉是唯一能让你看出它答错了的东西。Four suggestions for 'the first one to connect.' What they share: each is a source you open daily and whose contents you already know well — familiarity is the only thing that lets you notice a wrong answer.
— V
边界：能连不等于该连Boundaries: Can Connect Isn't Should Connect.
同一份资料进 Claude 有四条路，连接器只是其中一条 —— 而且常常不是最合适的那条：The same material can reach Claude four ways, and a connector is only one of them — often not the right one:
你的资料Your material
走这条Route
为什么Why
这次用一下的几个文件A few files for this one time
直接上传到对话Upload to the chat
一次性，用完就算，不必留存One-off; done when done, nothing to keep
一件长期事反复引用的固定材料Fixed material a long-term thing cites again and again
Project 知识库（第 4 章）Project knowledge base (Ch. 4)
钉在工作区、会被检索，不必每次重传Pinned, retrieved on demand, no re-upload
活的、常变的数据（邮件、任务、文档）Live, changing data (mail, tasks, docs)
连接器（远程 MCP）Connector (remote MCP)
Claude 直接读源头，还能回写Claude reads the source directly, and can write back
本机的文件与工具Local files and tools
桌面扩展（本地 MCP）Desktop extension (local MCP)
跑在你机器上，权限最深、最该谨慎Runs on your machine — deepest access, most caution
连了不用，比不连更糟Connected and unused is worse than not connected
权限一直挂着，收益是零。三周没用过的连接器，去 Customize > Connectors 断掉 —— 断了随时能连回来。The permission stays live and the return is zero. Any connector you haven't used in three weeks: disconnect it under Customize > Connectors — you can always reconnect.
它读到的东西会进对话记录What it reads enters the transcript
跨源问答意味着那些邮件正文、文档片段会出现在这段对话里。涉及敏感内容的，用隐身对话问（第 4 章），或者干脆自己去翻。A cross-source answer means those email bodies and document excerpts now live in this conversation. For anything sensitive, ask in an Incognito chat (Chapter 4) — or just go look it up yourself.
写操作先在低风险的地方试Try writes somewhere low-stakes first
第一次让它写，选一个你能一键撤销的动作（建一个 issue、存一个草稿），别选发信。它写歪一次你就知道该给它多少绳子了。The first time you let it write, pick an action you can undo in one click (open an issue, save a draft) — not sending. One crooked write teaches you how much rope to give it.
自定义连接器越过了这本书Custom connectors are past this book
接你公司内部 API 的那种自定义连接器，已经进了开发者地界。这本书不展开 —— 但你在这一章养成的那把尺子（能只给读就别给写）在那边同样成立。A custom connector wiring your company's internal API crosses into developer territory. This book doesn't go there — but the ruler you built here (grant read-only when you can) holds just as well over there.
— VI
收束 · 本章验收Sign-off.
列出了每天都翻的 3 个数据源，只连了其中最信任的 1 个。Listed the 3 sources you check daily and connected only the one you trust most.
连之前在目录页确认过它能读什么、能写什么。Checked in the directory what it can read and what it can write, before connecting.
问了一个只有跨源才答得了的真问题，而不是「总结一下今天的邮件」。Asked a real cross-source question, not 'summarize today's email.'
抽查了两条出处，确认它们真的支持那句话。Spot-checked two sources and confirmed they support the sentence.
回 Customize > Connectors 看过一眼它现在能看到你哪些东西。Went to Customize > Connectors and looked at what it can now see of yours.
那条跨源取数句式（含「没找到就说没找到」）存下来了。Saved the cross-source phrasing, including the 'say you couldn't find it' line.
能连进来的数据很多，
该连的没几个.
Plenty of data can connect,
few should.
Aklman Library
— 讨论Discussion
讨论Discussion.
评论区初始化中…Initializing comments…
01 / 01
没有匹配结果No matches.
换个关键词，或按 Esc 回到页面Try another keyword, or press Esc to return
