لێهاتووییەکان و MCP

Official, Google-hosted, and permission-inheriting rather than a separate program with its own access: a meaningfully lower-risk pattern than installing a third-party script. Still in Google's Developer Preview as of verification, and requires a Claude Enterprise, Pro, Max, or Team plan. It adds no limits of its own, so it hands Claude read access to whatever your Google account can already see. Review your Drive's sharing settings before connecting.

Same official, Google-hosted, permission-inheriting pattern as the Drive server above, and the same caveats: Developer Preview status, a paid Claude plan, and your organisation's own Google sharing settings are what actually control exposure.

Same official, Google-hosted, permission-inheriting pattern as the Drive server above. Check any formula-driven output before other people make decisions from it.

Same official, Google-hosted, permission-inheriting pattern as the Drive server above. Keep photos of identifiable people and exact locations out of a deck that will be shared beyond your organisation.

Same official, Google-hosted, permission-inheriting pattern as the Drive server above. An event title is an easy place for a real name or location to end up by accident, so write calendar entries as if a wider audience will eventually see them.

Same official, Google-hosted, permission-inheriting pattern as the Drive server above, but a mailbox is one of the most sensitive things an assistant can be given. Connect it only from an account that carries no witness or case correspondence, and read every draft before it is sent.

Same official, Google-hosted, permission-inheriting pattern as the Drive server above. Treat anything it can read as visible to everyone else who can already see that Chat space.

Featured in Claude's own official plugin directory (claude.com/plugins), so it met Anthropic's review bar for that listing. Invite the bot only into channels you intend Claude to see, and never a channel used for sensitive source coordination.

Built and published by Figma itself, and listed in both Claude's official plugin directory and GitHub's MCP registry. Low risk for design files. Do not put a beneficiary's photo or real name into a design file you expose this way.

Published by Airtable under an MIT licence, from Airtable's own GitHub organisation. Scope the access token to only the bases Claude actually needs, especially if any base holds beneficiary or donor personal data.

Published by Notion under an MIT licence, from Notion's own GitHub organisation. Scope the integration token to specific pages rather than your whole workspace, especially if any part of that workspace holds sensitive material.

Published by Microsoft itself and listed on GitHub's official MCP registry. The base converter runs on your machine. The optional vision-based OCR plugin does not: it sends images to whichever AI model you configure for that step, so only enable it once you know which model that is.

Published by DeepL under an MIT licence, from DeepL's own GitHub organisation. Text sent through it is still subject to DeepL's free-versus-paid data policy, described in the DeepL tool catalogue entry. Use a paid DeepL key for anything sensitive, not the free tier.

Published by Deepgram under an MIT licence, from Deepgram's own GitHub organisation. Unlike Whisper on your own computer, this sends audio to Deepgram's servers. Do not use it to transcribe an interview or testimony recording: use the offline whisper-local entry in the tool catalogue for that.

Not vendor-official, a community project. It is listed on GitHub's official MCP registry, a review-gated directory, and had around 330 GitHub stars as of verification, indicating real independent use. Running locally is genuinely lower-risk than a cloud OCR service for sensitive images, but as with any community server, read what it actually does before running it on a machine that also holds case files.

A reference server maintained under the official Model Context Protocol project. Your search queries leave your machine for Brave's servers, so never phrase a search around a witness name or an exact location you are trying to protect.