llms.txt@14-Connectors · git:20261001.bf1f66b · 2026-10-01 · sha256 92b9702719657afc

llms.txt@14-Connectors git:20261001.bf1f66bF

Immutable. This exact content never changes and is served at /api/v1/blob/92b9702719657afc.

# Connectors

> Every page below, concatenated. Each section gives the page title, its upstream source and its path in this repository.

---

## Using the GitHub integration | Claude by Anthropic

Source: https://support.claude.com/en/articles/9945670-using-the-github-integration
Path: 14-Connectors/9945670-using-the-github-integration.md

# Using the GitHub integration

Explore how the GitHub integration can enhance your development process with Claude.

Engineering

Claude.ai

Watch time

min

[Copy link](#)
https://claude.com/resources/tutorials/using-the-github-integration

## Related tutorials

[Using Claude Design for prototypes and UX](https://support.claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux)

Using Claude Design for prototypes and UX

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux)

Tutorial

[What is Claude Managed Agents?](https://support.claude.com/resources/tutorials/what-is-claude-managed-agents)

What is Claude Managed Agents?

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/what-is-claude-managed-agents)

Tutorial

[Using Claude Code Remote Control](https://support.claude.com/resources/tutorials/using-claude-code-remote-control)

Using Claude Code Remote Control

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/using-claude-code-remote-control)

Tutorial

[Troubleshooting skills](https://support.claude.com/resources/tutorials/troubleshooting-skills)

Troubleshooting skills

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/troubleshooting-skills)

Tutorial

[Homepage](https://claude.com)

Homepage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Write

[Button Text](#)

Button Text

Learn

[Button Text](#)

Button Text

Code

[Button Text](#)

Button Text

Write

- Help me develop a unique voice for an audience

Hi Claude! Could you help me develop a unique voice for an audience? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

Please execute the task as soon as you can—an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!

- Improve my writing style

Hi Claude! Could you improve my writing style? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

- Brainstorm creative ideas

Hi Claude! Could you brainstorm creative ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

Learn

- Explain a complex topic simply

Hi Claude! Could you explain a complex topic simply? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

- Help me make sense of these ideas

Hi Claude! Could you help me make sense of these ideas? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

- Prepare for an exam or interview

Hi Claude! Could you prepare for an exam or interview? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

Code

- Explain a programming concept

Hi Claude! Could you explain a programming concept? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

- Look over my code and give me tips

Hi Claude! Could you look over my code and give me tips? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

- Vibe code with me

Hi Claude! Could you vibe code with me? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to— like Google Drive, web search, etc.—if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

- Write case studies

This is another test

- Write grant proposals

Hi Claude! Could you write grant proposals? If you need more information from me, ask me 1-2 key questions right away. If you think I should upload any documents that would help you do a better job, let me know. You can use the tools you have access to — like Google Drive, web search, etc. — if they’ll help you better accomplish this task. Do not use analysis tool. Please keep your responses friendly, brief and conversational.

Please execute the task as soon as you can - an artifact would be great if it makes sense. If using an artifact, consider what kind of artifact (interactive, visual, checklist, etc.) might be most helpful for this specific task. Thanks for your help!

- Write video scripts

this is a test

[Anthropic](https://www.anthropic.com/)

Anthropic

Products

- Claude

[Claude](https://support.claude.com/product/overview)
Claude

- Claude Code

[Claude Code](https://support.claude.com/product/claude-code)
Claude Code

- Claude Code for Enterprise

[Claude Code for Enterprise](https://support.claude.com/product/claude-code/enterprise)
Claude Code for Enterprise

- Claude Cowork

[Claude Cowork](https://support.claude.com/product/cowork)
Claude Cowork

- @Claude

[@Claude](https://support.claude.com/product/tag)
@Claude

- Claude Design

[Claude Design](https://support.claude.com/product/design)
Claude Design

- Claude Science

[Claude Science](https://support.claude.com/product/claude-science)
Claude Science

- Claude Security

[Claude Security](https://support.claude.com/product/claude-security)
Claude Security

- Download app

[Download app](https://support.claude.com/download)
Download app

- Pricing

[Pricing](https://support.claude.com/pricing)
Pricing

- Log in

[Log in](https://claude.ai/login)

Features

- Claude in Chrome

[Claude in Chrome](https://support.claude.com/claude-in-chrome)
Claude in Chrome

- Claude for Microsoft 365

[Claude for Microsoft 365](https://support.claude.com/claude-for-microsoft-365)
Claude for Microsoft 365

- Skills

[Skills](https://support.claude.com/skills)
Skills

Models

- Mythos

[Mythos](../15-Claude-AI-Features/claude-mythos.md)
Mythos

- Fable

[Fable](../15-Claude-AI-Features/claude-fable.md)
Fable

- Opus

[Opus](https://support.claude.com/en/15-Claude-AI-Features/claude-opus-4-6-anthropic.md)
Opus

- Sonnet

[Sonnet](https://support.claude.com/en/15-Claude-AI-Features/claude-sonnet-4-6-anthropic.md)
Sonnet

- Haiku

[Haiku](https://support.claude.com/en/15-Claude-AI-Features/claude-haiku-4-5-anthropic.md)
Haiku

Solutions

- AI agents

[AI agents](https://support.claude.com/solutions/agents)
AI agents

- Code modernization

[Code modernization](https://support.claude.com/solutions/code-modernization)
Code modernization

- Coding

[Coding](https://support.claude.com/solutions/coding)
Coding

- Customer support

[Customer support](https://support.claude.com/solutions/customer-support)
Customer support

- Cybersecurity

[Cybersecurity](https://support.claude.com/solutions/cybersecurity)
Cybersecurity

- Enterprise

[Enterprise](https://support.claude.com/solutions/enterprise)
Enterprise

- Financial services

[Financial services](https://support.claude.com/solutions/financial-services)
Financial services

- Government

[Government](https://support.claude.com/solutions/government)
Government

- Healthcare

[Healthcare](https://support.claude.com/solutions/healthcare)
Healthcare

- Higher education

[Higher education](https://support.claude.com/solutions/education)
Higher education

- K-12 teachers

[K-12 teachers](https://support.claude.com/solutions/teachers)
K-12 teachers

- Legal

[Legal](https://support.claude.com/solutions/legal)
Legal

- Life sciences

[Life sciences](https://support.claude.com/solutions/life-sciences)
Life sciences

- Nonprofits

[Nonprofits](https://support.claude.com/solutions/nonprofits)
Nonprofits

- Small business

[Small business](https://support.claude.com/solutions/small-business)
Small business

Claude Platform

- Overview

[Overview](https://support.claude.com/platform/api)
Overview

- Developer docs

[Developer docs](../04-API-Reference/Other/home.md)
Developer docs

- Pricing

[Pricing](../17-Billing-Plans/pricing.md#api)
Pricing

- Ecosystem

[Ecosystem](https://support.claude.com/ecosystem)
Ecosystem

- Marketplace

[Marketplace](https://support.claude.com/platform/marketplace)
Marketplace

- Claude on AWS

[Claude on AWS](https://support.claude.com/partners/claude-on-aws)
Claude on AWS

- Google Cloud

[Google Cloud](https://support.claude.com/partners/google-cloud)
Google Cloud

- Microsoft Foundry

[Microsoft Foundry](https://support.claude.com/partners/microsoft-foundry)
Microsoft Foundry

- Regional compliance

[Regional compliance](https://support.claude.com/regional-compliance)
Regional compliance

- Console login

[Console login](../04-API-Reference/Other/usage-limits.md)
Console login

Resources

- Blog

[Blog](https://support.claude.com/blog)
Blog

- Claude partner network

[Claude partner network](https://support.claude.com/partners)
Claude partner network

- Community

[Community](https://support.claude.com/community)
Community

- Connectors

[Connectors](https://support.claude.com/connectors)
Connectors

- Courses

[Courses](https://www.anthropic.com/learn)
Courses

- Customer stories

[Customer stories](https://support.claude.com/customers)
Customer stories

- Engineering at Anthropic

[Engineering at Anthropic](https://www.anthropic.com/engineering)
Engineering at Anthropic

- Events

[Events](https://www.anthropic.com/events)
Events

- Plugins

[Plugins](https://support.claude.com/plugins)
Plugins

- Powered by Claude

[Powered by Claude](https://support.claude.com/partners/powered-by-claude)
Powered by Claude

- Service partners

[Service partners](#)
Service partners

- Tutorials

[Tutorials](https://support.claude.com/resources/tutorials)
Tutorials

- Use cases

[Use cases](https://support.claude.com/resources/use-cases)
Use cases

Company

- Anthropic

[Anthropic](https://www.anthropic.com/)
Anthropic

- Careers

[Careers](https://www.anthropic.com/careers)
Careers

- Policy

[Policy](https://www.anthropic.com/policy)
Policy

- Economic Futures

[Economic Futures](https://www.anthropic.com/economic-futures)
Economic Futures

- Research

[Research](../19-Reference/anthropic-com-research.md)
Research

- News

[News](../19-Reference/news.md)
News

- Policy on the AI Exponential

---

## Anthropic Connectors Directory FAQ | Claude Help Center

Source: https://support.claude.com/en/articles/11596036-anthropic-connectors-directory-faq
Path: 14-Connectors/anthropic-connectors-directory-faq.md

# Anthropic Connectors Directory FAQ

August 6, 2026

The Connectors Directory FAQ has moved to the Claude developer docs.

[Connectors overview →](https://claude.com/docs/connectors/overview)

[Building custom connectors →](https://claude.com/docs/connectors/building)

[Submitting to the Connectors Directory →](https://claude.com/docs/connectors/building/submission)

---

## Authorize MCP connectors for your entire organization | Claude Help Center

Source: https://support.claude.com/en/articles/15537633-authorize-mcp-connectors-for-your-entire-organization
Path: 14-Connectors/authorize-mcp-connectors-for-your-entire-organization.md

# Authorize MCP connectors for your entire organization

August 24, 2026

This article explains how Enterprise-managed auth works and how admins can authorize connectors for their organization through their identity provider. With Enterprise-managed auth, you authorize a connector once for your entire organization, and your team inherits access automatically on first login.

This feature is generally available for Team and Enterprise plans on Claude.

## What is Enterprise-managed auth?

Enterprise-managed auth is an authorization and authentication model for connectors in Claude. Instead of having every person authenticate each connector individually, admins provision connector access centrally through the organization's identity provider.

Once you enable a connector for your organization, your team gets it automatically the first time they log in, with identity inherited from their existing identity provider groups and roles.

## What you control

You decide which connectors are enabled, which groups or roles get them, and at what access level:

- Auth connectors once for your organization, and access is given to your team automatically.

- Use **[role-based permissions](https://support.claude.com/en/articles/13930458-set-up-role-based-permissions-on-enterprise-plans)** to choose exactly which roles get each connector, so different teams get the access that fits their work. See **Choose which roles get managed auth** below.

- Choose which permissions Claude can request when members connect through your identity provider, and narrow that further for individual roles.

- Revoke access by deprovisioning someone in your identity provider, which removes their connector access at the same time.

- Require that a connector only ever connects through your identity provider so personal accounts stay out of work tools.

**Note:** Your identity provider and each connector are operated by third parties under their own terms. Claude relays the authorization your identity provider issues; access decisions, scoping, and the data each connector can reach are governed by your identity provider’s policies and the connected service’s permissions, not by Anthropic.

Token lifetimes and lifecycle are managed by the connected authorization server and identity provider. Existing sessions end when the connector’s access token expires or is revoked.

## Choose which roles get managed auth

When you set up Enterprise-managed auth for a connector, you choose which roles inherit the connector when you set up role-based permissions. You can use role-based permissions to pilot a connector with a specific team before turning it on for your whole organization.

1. Go to **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)** and select a connector.

2. On the **Configuration** tab, click "Set up" next to **Managed authorization**.

3. On the **Connect** step, confirm your identity provider connection. Follow the setup guide to configure Enterprise-managed auth for this connector in your identity provider, and to enable managed auth in the connector's own admin settings. Click "Run test" to confirm the connection works.

4. On the **Roles** step, select who should get this connector automatically.

1. **User, Admin, Owner, Primary owner**: your organization's built-in roles, as a group.

2. Any custom role, selected individually.

To pilot a connector with one team, select only that team's custom role and leave the built-in roles unchecked. Members on the User, Admin, Owner, or Primary Owner role won't get the connector until you come back and add that option.

5. On the **Scopes** step, choose which permissions Claude can request when members connect through your identity provider. These apply to every role you selected. To narrow permissions for a specific role, use that role's **Connectors** tab instead (see below).

6. Click "Save & turn on."

Once set up, the connector's Configuration tab shows its current state: **Applied roles** lists which roles connect through managed authorization, and **Scopes** shows what's granted. To expand a pilot, click "Edit" next to **Applied roles** and add "User, Admin, Owner, Primary owner" or more custom roles.

**Note:** **Browser sign-in** and **Managed authorization** can be on for a connector at the same time. When they are, Claude tries **Managed authorization** first and prompts the user to sign in individually if that fails, so members aren't locked out while an identity provider issue gets resolved.

### Connector settings inside a custom role

You can also start from a role in **Organization settings** \> **Roles** instead of a connector. On a custom role's **Connectors** tab, **How members connect** controls how that role's members authenticate, across every connector at once, or per connector:

- **Individually**: members sign in with their own accounts.

- **Managed authorization**: members connect through your identity provider.

- **Set per connector**: choose individually for each connector.

## What works with Enterprise-managed auth

Enterprise-managed auth brings together two things your organization already uses: your identity provider, which controls who gets access, and the connectors your teams work with day to day.

### Identity providers

Okta is supported at launch, with more identity providers coming soon. See **[Okta’s documentation](https://developer.okta.com/docs/guides/xaa-agent-to-app/main/)** for more details.

### Connectors

Currently, you can provision these connectors through Enterprise-managed auth:

- Asana (see **[Asana’s documentation](https://help.asana.com/s/article/cross-app-access)**)

- Atlassian (see **[Atlassian’s documentation](https://support.atlassian.com/security-and-access-policies/docs/configuring-enterprise-managed-authentication/)**)

- Canva (see **[Canva’s documentation](https://www.canva.com/help/manage-cross-app-access/)**)

- Datadog (see **[Datadog’s documentation](https://docs.datadoghq.com/account_management/org_settings/cross_app_access/)**)

- Figma (see **[Figma’s documentation](https://help.figma.com/hc/articles/41992841175959)**)

- Granola (see **[Granola’s documentation](https://docs.granola.ai/help-center/sharing/integrations/mcp#enterprise-managed-authorization)**)

- Linear (see **[Linear’s documentation](https://linear.app/docs/mcp#enterprise-managed-authorization)**)

- Notion (see **[Notion’s documentation](https://www.notion.com/help/set-up-enterprise-managed-connections-for-notion-mcp)**)

- Slack (see **[Slack’s documentation](https://slack.com/help/articles/54548358406419)**)

- Supabase (see **[Supabase’s documentation](https://supabase.com/docs/guides/platform/sso/enterprise-mcp-authentication)**)

Any MCP provider can add support for Enterprise-managed auth. See **[Enterprise-Managed Authorization](../06-MCP-Tools/Extensions/extensions-auth-enterprise-managed-authorization.md)** for more details.

### Personal connectors

Your team can still add personal connectors on top of what you provision. Enterprise-managed auth handles the connectors you enable for your organization, while individuals can connect additional services for their own use.

---

## Browse skills, connectors, and plugins in one directory | Claude Help Center

Source: https://support.claude.com/en/articles/14328846-browse-skills-connectors-and-plugins-in-one-directory
Path: 14-Connectors/browse-skills-connectors-and-plugins-in-one-directory.md

# Browse skills, connectors, and plugins in one directory

Our unified directory brings skills, connectors, and plugins together in one place so you can find and install everything that customizes Claude without switching between separate menus. On Team and Enterprise plans, the directory is also where skills and plugins published to your organization appear.

------------------------------------------------------------------------

## Access the directory

1. Open Claude or Claude Desktop

2. Click “Customize” in the left sidebar.

3. Click on the tab you want to view: Skills, Connectors, or Plugins.

4. Open the **Discover** tab.

### Skills

To open the Skills directory, go to **[Customize \> Skills](https://claude.ai/customize/skills)**, click the “+” button, then “Browse skills.” Click the “Add” button on any skill to add it to your skills list. Once installed, the skill appears in **[Customize \> Skills](https://claude.ai/customize/skills)** and is enabled by default, so Claude can use it automatically when relevant. You can toggle it off at any time, but the skill stays in the directory so you can re-enable it later.

Skills you install from the directory are view-only. You can use them, but you can't edit their contents. If you want to change how a skill works, download a copy, modify it, and upload it as your own.

On Team and Enterprise plans, the "Your organization" tab lists skills available to your entire organization. This includes skills that owners have provisioned centrally and skills that colleagues have published to the organization. You can't fully delete these skills from your list. Only an organization owner can remove them from the directory.

**Note:** Skills and plugins shared with you directly by a colleague don’t appear in the directory, they go straight to your skills list. See **[Use skills in Claude](../02-Claude-Code-CLI/using-skills-in-claude.md)** and **[Use plugins in Claude](https://support.claude.com/en/articles/13837440-use-plugins-in-claude)** for details on how shared skills and plugins work.

### Connectors

The connectors tab shows the same catalog of services you can connect Claude to, now in the unified view. Click "Connect" on any service to start the authentication flow. For more on connecting and managing services, see **[Use connectors to extend Claude’s capabilities](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**.

### Plugins

The **Discover** tab in **Customize \> Plugins** shows available plugins, including any your organization has distributed through a marketplace. Plugins a colleague has shared with you directly are listed under **Shared with you** in **Customize \> Plugins**.

Select a plugin, then click "Add." The plugin is saved to your account. Its skills and commands are available in chat (on the web and the Chat tab in Claude Desktop), in Cowork, and in Claude Code sessions signed in with the same Claude account. To take a plugin off your account later, open it and select "Remove."

## For organization owners

Whether people can publish to the directory depends on your Publishing setting. To let people in your organization publish skills to the directory, set **Publishing** to **Open** or **Requires review** in **[Organization settings \> Plugins & skills](https://claude.ai/admin-settings/skills)** in the “Policy” tab. The separate **Skill sharing** lets people share skills and plugins with specific colleagues without publishing to the directory.

For full details on configuring sharing and provisioning skills centrally, see **[Provision and manage skills for your organization](https://support.claude.com/en/articles/13119606-provision-and-manage-skills-for-your-organization)**.

---

## Build custom connectors via remote MCP servers | Claude Help Center

Source: https://support.claude.com/en/articles/11503834-building-custom-connectors-via-remote-mcp-servers
Path: 14-Connectors/building-custom-connectors-via-remote-mcp-servers.md

# Build custom connectors via remote MCP servers

The guide to building custom connectors has moved to the Claude developer docs.

**[View the building guide →](https://claude.com/docs/connectors/building)**

---

## Claude for Microsoft 365 | Claude by Anthropic

Source: https://www.claude.com/claude-for-powerpoint
Path: 14-Connectors/claude-for-excel.md

# Claude for Microsoft 365

Work without the window shuffle

Claude works inside Excel, PowerPoint, Word, and Outlook. Start in your inbox, end in the deck. It remembers everything in between.

Install for Microsoft 365

[Install for Microsoft 365](https://marketplace.microsoft.com/en-us/product/office/WA200010725?tab=Overview)

Install for Microsoft 365

Install for Outlook

[Install for Outlook](https://marketplace.microsoft.com/en-us/product/office/WA200010724?tab=Overview)

Install for Outlook

## Claude for Excel

Ask about any cell, update assumptions without breaking formulas, and build models from scratch.

## Claude for PowerPoint

Build slides in your template, edit what you've selected, and generate native charts and diagrams.

## Claude for Word

Edit with tracked changes, respond to comment threads, and update content using company styles.

Beta

## Claude for Outlook

Triage your inbox in one prompt, draft replies that wait for you to send, and find time across calendars.

## How teams use Claude for Microsoft 365

[Play video](#)

Play video

### Turn an email into a deliverable

Triage email, open the brief in Word, build the model in Excel, make the PowerPoint deck, draft the review invite. Context carries across each step.

### Clear your inbox before the meeting

Ask Claude what needs your attention, get replies drafted for a few quick wins, and open the brief from your inbox. The context comes with it into Word.

### Build a model from a brief

Ask Claude to build the model behind your Word brief. It opens Excel, pulls the numbers from the doc, and builds real formulas across multiple tabs.

### Draft in your template

Point Claude at a brief, a dataset, or a thread. It drafts sections in your heading styles, populates tables in place, and keeps your numbering intact.

## The Claude you trust, inside Microsoft 365

### Every edit is reviewable

Tracked changes in Word, highlighted cells in Excel, drafts that wait in Outlook. Nothing goes out or gets saved until you say so.

### Your templates and formatting

Claude uses your rules, whether for slide masters, heading styles, formula structures, or numbering so you stay on brand.

### Enterprise security, built in

Sign in with a Claude account, or connect through your existing cloud provider. Works within your existing compliance framework.

How can Claude help?

Open the brief in Word and start the memo from our firm template.

Copy prompt

[Copy prompt](https://claude.ai/new?q=Open+the+brief+in+Word+and+start+the+memo+from+our+firm+template.)

Copy prompt

How can Claude help?

Turn this updated analysis into the SteerCo deck in the Acme template.

Copy prompt

[Copy prompt](https://claude.ai/new?q=Turn+this+updated+analysis+into+the+SteerCo+deck+in+the+Acme+template)

Copy prompt

How can Claude help?

Find 30 minutes with everyone on this thread next week

Copy prompt

[Copy prompt](https://claude.ai/new?q=What+did+the+other+side+change+in+section+4%2C+and+are+any+of+these+dealbreakers%3F)

Copy prompt

[Prev](#)

Blog post

Claude for Excel, PowerPoint, and Word are now generally available on all paid plans, with Claude for Outlook joining in beta.

Read blog

[Read blog](https://www.claude.com/blog/collaborate-with-claude-across-excel-powerpoint-word-and-outlook)

Read blog

### What customers are saying

“Claude enables a seamless transition from rough ideas to polished, branded deliverables across presentation, document and spreadsheet applications without disrupting the workflow. That end-to-end consistency has been a significant time-saver, especially when quality, formatting, and speed all matter.”

Vivek Kulkarni, US AI Transformation Leader

“Claude in Excel allows my teams to build an initial version of complex models faster, enabling them to focus on refining the model, pressure testing inputs and assumption, and exploring more scenarios and trade-offs. This helps us have richer and deeper discussions with our clients earlier.”

Gene Rapoport, Head of Private Equity AI Practice

“Claude for M365 is being rapidly adopted by ServiceNow. Claude does the work in Excel itself, instead of asking us to move content between tools, driving step change in productivity.”

Rajeev Sethi, GVP Enterprise Technologies

“We can instruct Claude to build a style guide from an executive's prior written communications so our EAs can draft their emails in their voice. That's high-leverage work the team would never have time to set up by hand.”

Ben Letalik, Sr. Director, Digital Transformation & Innovation

“Our investment professionals live in data and analytical models, and Claude for Excel meets them there. Analysts are using it to build and update coverage models, separate signal from noise, and pressure-test their work — all with a step-change in efficiency.”

Atte Lahtiranta, Head of Core Engineering

[Prev](#)

0/5

## Core capabilities across the apps you use every day

### One conversation across all your apps

Context carries from Outlook to Word to Excel to PowerPoint. Change one thing, and every open file catches up.

### Deploy through your preferred cloud

Connect through Microsoft Foundry, Amazon Bedrock, or Google Cloud Vertex AI credentials.

### Bring any document into the conversation

Drop a PDF or doc into any sidebar. Claude reads it alongside your open file and references it in other apps.

### Turn workflows into Skills

When a process is right, save it as a skill. The team can use it the same way in all four apps.

Learn more

[Learn more](https://www.claude.com/skills)

Learn more

### Type or talk, whichever is faster

Use dictation to talk to Claude in a sidebar instead of typing.

### Access connectors

Pull context from outside sources directly from the sidebar.

Learn more

[Learn more](../04-API-Reference/Other/partners-mcp.md)

Learn more

## FAQ

### Where is this available?

Claude for Excel, PowerPoint, and Word are generally available on all paid Claude plans. Claude for Outlook is in beta on all paid plans.

### Can I connect through my cloud provider?

Yes. Claude for Microsoft 365 is available on Amazon Bedrock, Google Cloud Vertex AI, and Microsoft Foundry.

### Does Claude preserve my formatting and templates?

Yes. Claude inherits your heading styles, slide masters, formula conventions, and numbering. Edit one section without disturbing the rest.

### Can Claude send an email without me seeing it first?

No. Drafts and calendar invites open in Outlook's native compose form and wait for you to click send.

[Prev](#)

## Get started with Claude for Microsoft 365

Install for Microsoft 365

[Install for Microsoft 365](https://marketplace.microsoft.com/en-us/product/office/WA200010725?tab=Overview)

Install for Microsoft 365

Install for Outlook

[Install for Outlook](https://marketplace.microsoft.com/en-us/product/office/WA200010724?tab=Overview)

Install for Outlook

[Homepage](https://claude.com)

Homepage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

[Anthropic](https://www.anthropic.com/)

Anthropic

Products

- Claude

[Claude](../15-Claude-AI-Features/product-overview.md)
Claude

- Claude Code

[Claude Code](../15-Claude-AI-Features/claude-com-product-claude-code.md)
Claude Code

- Claude Cowork

[Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
Claude Cowork

- @Claude

[@Claude](claude-for-slack.md)
@Claude

- Claude Science

[Claude Science](../15-Claude-AI-Features/product-claude-science.md)
Claude Science

- Claude Security

[Claude Security](../15-Claude-AI-Features/product-claude-security.md)
Claude Security

- Download app

[Download app](https://www.claude.com/download)
Download app

- Pricing

[Pricing](../17-Billing-Plans/pricing.md)
Pricing

- Log in

[Log in](https://claude.ai/login)

Capabilities

- Artifacts

[Artifacts](https://www.claude.com/features/artifacts)
Artifacts

- Design

[Design](../15-Claude-AI-Features/product-design.md)
Design

- Connectors

[Connectors](https://www.claude.com/marketplace/connectors-plugins)
Connectors

- Plugins

[Plugins](https://www.claude.com/marketplace/plugins)
Plugins

- Skills

[Skills](https://www.claude.com/skills)
Skills

Extensions

- Claude in Chrome

[Claude in Chrome](https://www.claude.com/claude-in-chrome)
Claude in Chrome

- Claude for Microsoft 365

[Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
Claude for Microsoft 365

Models

- Mythos

[Mythos](../15-Claude-AI-Features/claude-mythos.md)
Mythos

- Fable

[Fable](../15-Claude-AI-Features/claude-fable.md)
Fable

- Opus

[Opus](../15-Claude-AI-Features/claude-opus.md)
Opus

- Sonnet

[Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
Sonnet

- Haiku

[Haiku](../15-Claude-AI-Features/claude-haiku.md)
Haiku

Enterprise

- Overview

[Overview](../18-Industry-UseCases/enterprise.md)
Overview

- Claude Code for Enterprise

[Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
Claude Code for Enterprise

Use cases

- AI agents

[AI agents](../18-Industry-UseCases/agents.md)
AI agents

- Code modernization

[Code modernization](../18-Industry-UseCases/code-modernization.md)
Code modernization

- Coding

[Coding](../18-Industry-UseCases/coding.md)
Coding

- Commerce

[Commerce](../18-Industry-UseCases/commerce.md)
Commerce

Departments

- Customer support

[Customer support](../18-Industry-UseCases/customer-support.md)
Customer support

- Cybersecurity

[Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
Cybersecurity

- Legal

[Legal](../18-Industry-UseCases/legal.md)
Legal

- Sales

[Sales](../18-Industry-UseCases/sales.md)
Sales

Industries

- Financial services

[Financial services](../18-Industry-UseCases/finance.md)
Financial services

- Government

[Government](../18-Industry-UseCases/government.md)
Government

- Healthcare

[Healthcare](../18-Industry-UseCases/healthcare.md)
Healthcare

- Higher education

[Higher education](../18-Industry-UseCases/education.md)
Higher education

- K-12 teachers

[K-12 teachers](../18-Industry-UseCases/teachers.md)
K-12 teachers

- Life sciences

[Life sciences](../18-Industry-UseCases/life-sciences.md)
Life sciences

- Nonprofits

[Nonprofits](../18-Industry-UseCases/nonprofits.md)
Nonprofits

- Small business

[Small business](../18-Industry-UseCases/small-business.md)
Small business

Programs

- Startups

[Startups](../15-Claude-AI-Features/programs-startups.md)
Startups

- Scientists

[Scientists](../15-Claude-AI-Features/programs-claude-team-plan-for-research-labs.md)
Scientists

Developers

- Developer docs

[Developer docs](../02-Claude-Code-CLI/code-home.md)
Developer docs

- Developer blog

[Developer blog](https://claude.dev/)
Developer blog

- Community

[Community](https://www.claude.com/community)
Community

- Console

[Console](../04-API-Reference/Other/home.md)
Console

- Engineering at Anthropic

[Engineering at Anthropic](https://www.anthropic.com/engineering)
Engineering at Anthropic

Platform

- Overview

[Overview](https://www.claude.com/platform/api)
Overview

- Marketplace

[Marketplace](https://www.claude.com/marketplace)
Marketplace

- Claude on AWS

[Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
Claude on AWS

- Google Cloud

[Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
Google Cloud

- Microsoft Foundry

[Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
Microsoft Foundry

Resources

- Blog

[Blog](https://www.claude.com/blog)
Blog

- Claude partner network

[Claude partner network](../04-API-Reference/Other/partners.md)
Claude partner network

- Claude Academy

[Claude Academy](https://academy.claude.com/)
Claude Academy

- Customer stories

[Customer stories](../18-Industry-UseCases/customers.md)
Customer stories

- Events

[Events](https://www.anthropic.com/events)
Events

- Powered by Claude

[Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
Powered by Claude

- Service partners

[Service partners](https://www.claude.com/marketplace/service-partners)
Service partners

Help and security

- Availability

[Availability](https://www.anthropic.com/supported-countries)
Availability

- Check files

[Check files](https://claude.com/check-files)
Check files

- Regional compliance

[Regional compliance](https://www.claude.com/regional-compliance)
Regional compliance

- Report abuse

[Report abuse](https://claude.com/form/anthropic-content-reporting)
Report abuse

- Security and compliance

[Security and compliance](https://trust.anthropic.com/)
Security and compliance

- Status

[Status](https://status.anthropic.com/)
Status

- Support center

[Support center](https://support.claude.com/en/)
Support center

Company

- Anthropic

[Anthropic](https://www.anthropic.com/)
Anthropic

- Careers

[Careers](https://www.anthropic.com/careers)
Careers

- Policy

[Policy](https://www.anthropic.com/policy)
Policy

- Research

[Research](../19-Reference/anthropic-com-research.md)
Research

- Anthropic news

[Anthropic news](../19-Reference/news.md)
Anthropic news

- Policy on the AI Exponential

---

## Claude in Slack: Tag @Claude in any thread | Claude by Anthropic

Source: https://www.claude.com/claude-for-slack
Path: 14-Connectors/claude-for-slack.md

# Tag Claude in Slack

@Claude reads threads, understands full context, and reacts in real time so your team moves forward together. Bring Claude into your channel.

Add to Slack

[Add to Slack](https://api.anthropic.com/integrations/v1/slack/install)

Add to Slack

Read documentation

[Read documentation](https://claude.com/docs/claude-tag/overview)

Read documentation

Available in beta for Claude Enterprise and Team customers in Slack.

[Play video](#)

Play video

“Rather than using AI on my computer or in my own IDE, I can now do work out in the open in a public Slack channel with my teammates, and we can actually more effectively collaborate on tasks together.”

Micah Stairs, Head of Support Engineering

“Claude Tag solved two problems at once: the interface and the data access piece. My whole team now has Claude as a teammate to ask about our code, docs and support conversations right in Slack, where they already work, and we manage what it can access in one place.”

George Dilthey, Head of Support

“Claude Tag is our first responder for internal bugs. It reads incoming reports, looks at screenshots of failures, and uses access to Datadog, Linear, and GitHub to weed out user errors, trace root cause, and often draft a fix PR. Our engineers’ first reaction was ‘this is amazing.’”

Aabhas Sharma, CTO

“Claude Tag turned a summer of conference logistics — the follow-ups and chasing that always fell through the cracks — into an events program that runs itself while I stay on strategy.”

Matthew Scott, Product Marketing

“Claude Tag doesn’t just do the work — it challenges our thinking, provokes better questions, and elevates our judgement rather than replacing it. And we still feel very much in control throughout.”

Simon Mansfield, Director, Enterprise AI

“There were no skeptics on our team. Everyone leaned in from day one — it felt like Claude Tag in Slack was something they’d been waiting for.”

Darian Bailey, AI Engineer & Tag Admin

“Claude Tag meets our teams where they already work. Slack is the entry point for everything at Gusto, and the fact that Claude Tag is native there is huge for us. We see a lot of potential here.”

Chad Kunsman, AI Developer

[Prev](#)

0/5

Coming soon to Microsoft Teams

Tag [@Claude](https://anthropic.enterprise.slack.com/team/U08SSLN6TTL) in Teams, where it will read the conversation, understand context, and respond in real time.

Join the waitlist

[Join the waitlist](https://www.claude.com/form/claude-tag-teams-waitlist)

Join the waitlist

## How it works

Tag Claude into any thread in Slack, no matter how long or messy. It reacts to context, decisions, or open questions to help busy teams get more done.

### Tag it in

@Claude in any thread or channel and it picks up the context everyone already shares. Ask it to run the numbers, file a ticket, or organize a chaotic chat into action items. It reads the room and does the work.

Thread \#checkout-incidents

Marcus Nguyen 2:14 PM

@Claude checkout error rate jumped from 0.3% to 6% right after the 14:00 deploy — can you dig in and figure out what broke?

1 reply

ClaudeAGENT 2:14 PM

On it — tracing the checkout error spike since the 14:00 deploy.

✓Pulled the 14:00 deploy diff from GitHub (`#4821`)

✓Queried Datadog — 502s isolated to the `cart-service`

✓Correlated with a 5× spike in DB connection-pool timeouts

✓Compared error rates by region against rollback candidates

✱Writing root-cause summary + rollback recommendation…

To-dos as of 2:18 PM (Now)

[Open session in Claude](#)

[](#send)

### Set a schedule or let it run long tasks

Give @Claude standing instructions and it works without a mention now or in the future. Ask it to watch a channel, run a weekly digest, flag anything urgent, or page the right person.

\#revenue ⋮

Marcus Nguyen Thursday 8:55 AM

@Claude Every Monday at 9, post a pipeline update for the team — pull the latest from Salesforce.

ClaudeAGENT Thursday 8:55 AM

Got it — I'll pull the pipeline from Salesforce and post a digest every Monday at 9 AM.

Monday ▾

ClaudeAGENT 9:00 AM

**Weekly pipeline — Jun 8–14**

\$3.6M open pipeline · +\$610K WoW · 5 deals advanced.

pipeline-trend.png▾

- Beacon Corp expansion advanced to **Negotiation** — \$240K
- 2 new logos entered Discovery; 5 deals moved a stage
- Acme renewal flagged at risk — pricing pushback, exec synced Thu

[Open session in Claude](#)

[](#threads)

### It jumps in, and can tag you back

@Claude doesn't wait to be asked. It surfaces the thread that went quiet, posts when the deploy is live, and flags the decision that needs your call.

Thread \#eng-triage

SentryAPP 10:02 AM

**New issue** · `NullPointerException` in `CheckoutService.applyPromo()`

142 events in the last 30m · first seen 10:02 AM · 38 users affected

[View in Sentry](#)

2 replies

ClaudeAGENT 10:03 AM

Reproduced — a null promo code slips past validation and hits `applyPromo()`. Fix is a one-line guard plus a regression test.

ClaudeAGENT 10:05 AM

Opened PR [\#1247](#) with the fix. cc @Marcus Nguyen — you own `checkout`, mind reviewing?

[Open session in Claude](#)

[](#get-help)

## How teams use @Claude

Claude in Slack can share work in the format your team needs, right in the thread.

New

On-call

Catch up

Pull numbers

Draft PRs

Call prep

Active

Prompt

Can you tell me ...

Attachments

Document

84kb

TXT

Document

105 lines

TXT

Search Workspace

\#prod-alerts

Message \#prod-alerts

@Claude Watch this channel, triage what comes in, and work through the backlog. Tag me only when something needs my call.

On it — watching **\#prod-alerts** now. I’ll triage what comes in and work the backlog, and only tag you when something needs your call.

🚨 `checkout-api` — p99 latency **4,812ms** (threshold 2,000ms)

env: `prod` · 3/12 hosts · started 02:06 UTC · [monitor](#) · [APM trace](#)

On it. Spike lines up with deploy `c4f1a09` (02:04) — new inventory check in `CartService.validate()` is calling `inventory-svc` per line item instead of batched. Only the 3 canary hosts have it.

✓ Paused rollout at 25%
✓ Opened revert [\#48231](#) — merging once CI is green (~6m)
✱ Watching p99, should recover as canaries drain

Not paging anyone. @Nathan — only flagging because the real fix (batch the inventory call) touches the pricing path you own; revert ships regardless.

[Open session in Claude](#)

### Watch what matters

@Claude can manage work in the channels your team never had bandwidth for: monitoring backlogs, triaging alerts, and surfacing what needs a human to review, so work that keeps getting pushed out can finally be completed.

## Prompt

@Claude Watch this channel, triage what comes in, and work through the backlog. Tag me only when something needs my call.

Prompt

Can you tell me ...

Attachments

Document

84kb

TXT

Document

105 lines

TXT

Search Workspace

\#launch-q3

Message \#launch-q3

Pushing feature freeze to Thursday. Legal needs another pass on the data handling docs.

Agreed. Also — pricing page copy is approved. Design can proceed.

Can someone loop in Compliance on the pricing copy too, or is Legal's sign-off enough?

@claude What got decided here and what's still open?

✓ Read through the channel from the top.
✓ Sort out what's settled vs. still pending.
✓ Write the summary.

todos as of 1:22 PM

[Open session in Claude](#)

**Decided:**

- Feature freeze moves to Thursday — Legal needs another pass on the data handling docs first.
- Pricing page copy is approved — design can proceed.

**Still open:**

- No timeline yet on when Legal's pass will be done — Thursday freeze could slip again if it runs long.
- Unclear who owns following up with Legal for status (Elena didn't assign it).

[Open session in Claude](#)

### Catch up fast

Get everything you need from a long thread in seconds. @Claude can surface decisions, open questions, and stakeholders, and you see exactly what's waiting on you.

## Prompt

@Claude What got decided here and what's still open?

Prompt

Can you tell me ...

Attachments

Document

84kb

TXT

Document

105 lines

TXT

Search Workspace

Thread \#revenue-ops

Reply…

@Claude What are the top 20 enterprise accounts by spend, last 7 and 28 days?

✓ Pulled enterprise account spend from BigQuery for the trailing 7 and 28 days.
✓ Ranked the top 20 by 28-day spend and charted the 7-day alongside.

todos as of 10:42 AM

[Open session in Claude](#)

Here are the top 20 enterprise accounts by spend, ranked by the trailing 28 days with the last 7 alongside.

| Rank | Account | 7-day | 28-day |
|------|-----------------------|--------|--------|
| 1 | Northwind Trading | \$151K | \$512K |
| 2 | Vertex Logistics | \$118K | \$438K |
| 3 | Helios Energy | \$96K | \$391K |
| 4 | Meridian Bank | \$88K | \$356K |
| 5 | Atlas Robotics | \$101K | \$312K |
| 6 | Sunbeam Health | \$64K | \$287K |
| 7 | Cobalt Systems | \$71K | \$264K |
| 8 | Orion Media | \$52K | \$241K |
| 9 | Ironclad Security | \$70K | \$223K |
| 10 | Pinnacle Foods | \$41K | \$205K |
| 11 | Lumen Analytics | \$63K | \$188K |
| 12 | Cascade Retail | \$38K | \$171K |
| 13 | Granite Capital | \$44K | \$156K |
| 14 | Beacon Aerospace | \$33K | \$142K |
| 15 | Tideline Shipping | \$41K | \$129K |
| 16 | Summit Pharma | \$24K | \$117K |
| 17 | Verdant Agriculture | \$33K | \$104K |
| 18 | Quartz Semiconductor | \$21K | \$92K |
| 19 | Halcyon Games | \$29K | \$71K |
| 20 | Driftwood Hospitality | \$14K | \$53K |

top-20-enterprise-accounts-by-spend.png▾

The top 5 accounts are ~45% of enterprise spend (**\$2.0M** of **\$4.45M**). Worth watching **Atlas Robotics** and **Halcyon Games** — their last 7 days are 32% and 41% of the 28-day figure (a flat week would be ~25%), so both are accelerating.

### Pull the numbers

Ask @Claude to query your data and it posts results like metrics, benchmarks, and charts in the channel, so the whole team sees the answer and can keep asking questions right there.

## Prompt

@Claude Top 20 enterprise accounts by spend, last 7 and 28 days.

Prompt

Can you tell me ...

Attachments

Document

84kb

TXT

Document

105 lines

TXT

Search Workspace

\#eng-tickets

Message \#eng-tickets

Auth is throwing 502s on token refresh since the deploy. Looks like a race condition in `services/auth`.

@Claude fix the bug in this thread and open a draft PR.

Found it — race in `services/auth/token_cache.go`. Concurrent refreshes for the same subject both miss cache and the slower one overwrites the fresh token with a stale one → next request gets a 502. Deploy `a3f9c1e` exposed it by dropping the per-request mutex.

Draft PR: [\#48217](#) · CI green · +71 −12

[Open session in Claude](#)

### Build from the thread

Turn a bug report into a draft PR from the context is in the thread without ever leaving Slack. Get more done without switching tabs.

## Prompt

@Claude Fix the bug in this thread and open a draft PR.

Prompt

Can you tell me ...

Attachments

Document

84kb

TXT

Document

105 lines

TXT

Search Workspace

Thread \#acme-renewal

Reply…

@Claude I’m meeting Acme at 2 — what do I need to know?

**Acme · 2pm** — Sarah Chen (CTO, decision), Marcus Webb (VP Eng, champion)

- **Deal:** \$1.4M renewal + expansion, close Jun 30. Redlined MSA with their legal since Fri.
- **Sticking points:** EU data residency · 99.95% SLA ask · flat price on 62 overage seats
- **Usage:** +38% MoM, 312/250 seats, 2 P1s last 30d (both \<4h)
- **Watch:** “evaluating Cursor” thread in their \#eng-leads Tue — leverage, not real
- **Play:** lead with usage + support SLAs → trade EU commit (Q3) for them dropping 99.95%. Let them raise the overage.

[Deal room](#) · [last Gong recap](#)

[Open session in Claude](#)

### Prep before calls

Walk into every meeting with a full briefing. CRM notes, recent threads, and call history pulled together before you think to ask.

## Prompt

@Claude I'm meeting Acme at 2 — what do I need to know?

## Core capabilities

See what @Claude can do for your team.

### **Customizable identities for granular governance**

The longer Claude works with your team, the more it understands how your organization thinks, how decisions get made, and who owns what.

### Memory across threads and days

Context can draw on previous conversations and memory. What happened in Monday's standup is still there on Thursday, without anyone repeating it.

### A shared resource in your channel

Claude surfaces what matters to the whole channel, not just the person who asked. Everyone sees the work, and anyone can build on it

### Proactive action instead of asking

Set a standing instruction once. Claude watches the channel, runs routines, flags what's urgent, and tags you back when something needs a decision.

### In the work and tools with you

Shape how Claude works in each channel with skills and instructions. Give it access to tools and data to take action on your behalf and post results.

### Runs tasks that take days

Hand Claude a complex task and it works while you move on to other projects. It follows up, asks for input, or comes back when it's done.

56%

fewer alerts after Claude Tag began resolving the root causes behind them

Read story

[Read story](../18-Industry-UseCases/carvana.md)

Read story

Claude on call:
How Claude Tag serves as Anthropic’s first responder for CI/CD failures

An engineer on our Continuous Integration team walks through the agent he built that powers CI incident response at Anthropic.

[Read more](https://www.claude.com/blog/ai-ci-cd-on-call)

How Anthropic deploys Claude Tag for ad-hoc questions

Two data scientists at Anthropic walk through how Claude Tag turns Slack threads into self-service analytics, with the same governed definitions analysts use.

[Read more](https://www.claude.com/blog/self-service-data-analytics-in-slack-how-anthropic-deploys-claude-tag-for-ad-hoc-questions)

Learn more about how Anthropic employees are using Claude Tag

Producing customer-ready collateral, compiling weekly issue reports, and running legal review, all where the work already happens.

[Read more](https://www.claude.com/blog/how-anthropic-employees-use-claude-tag)

[Prev](#)

## @Claude connects to your tools

Configure any tool with an API using Agent Identity. Claude can query, act, and report back in the thread where the work is happening.

[Read more](https://www.claude.com/blog/agent-identity-access-model)

## Admins stay in control

Claude acts under its own identity in your systems. Admins configure access once; everyone else just types @Claude.

### **Customizable identities for granular governance**

Claude has its own account in your systems, not a borrowed login. Every credential’s use is logged, so "what did Claude do, and who asked for it?" always has an answer.

### Add it per channel

Decide which tools Claude can reach and read. Confine sensitive connectors to a single private channel or enable broader access for specific tools and resources. Adjust any time from the admin console.

What is Claude Tag?

Learn more about [**@Claude**](https://anthropic.enterprise.slack.com/team/U08SSLN6TTL) and what happens to the former Claude for Slack experience.

[Read more](https://support.claude.com/en/articles/15594475)

Agent identity: a new security model for autonomous, team-wide AI

Explore our new security model built for agents, not retrofitted from chatbots.

[Read more](https://www.claude.com/blog/agent-identity-access-model)

Tutorial: Working with @Claude in your workspace

Claude now works alongside your team, under its own account, in the places you already work together. You tag it in the way you'd tag anyone, or have it speak up on its own when there's something it can help with.

[Read more](https://www.claude.com/resources/tutorials/best-practices-using-claude-tag)

[Prev](#)

## Ready for a new way of working?

Add to Slack

[Add to Slack](https://api.anthropic.com/integrations/v1/slack/install)

Add to Slack

Join Teams waitlist

[Join Teams waitlist](https://www.claude.com/form/claude-tag-teams-waitlist)

Join Teams waitlist

[Homepage](https://claude.com)

Homepage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

[Anthropic](https://www.anthropic.com/)

Anthropic

Products

- Claude

[Claude](../15-Claude-AI-Features/product-overview.md)
Claude

- Claude Code

[Claude Code](../15-Claude-AI-Features/claude-com-product-claude-code.md)
Claude Code

- Claude Cowork

[Claude Cowork](../15-Claude-AI-Features/product-cowork.md)
Claude Cowork

- @Claude

[@Claude](claude-for-slack.md)
@Claude

- Claude Science

[Claude Science](../15-Claude-AI-Features/product-claude-science.md)
Claude Science

- Claude Security

[Claude Security](../15-Claude-AI-Features/product-claude-security.md)
Claude Security

- Download app

[Download app](https://www.claude.com/download)
Download app

- Pricing

[Pricing](../17-Billing-Plans/pricing.md)
Pricing

- Log in

[Log in](https://claude.ai/login)

Capabilities

- Artifacts

[Artifacts](https://www.claude.com/features/artifacts)
Artifacts

- Design

[Design](../15-Claude-AI-Features/product-design.md)
Design

- Connectors

[Connectors](https://www.claude.com/marketplace/connectors-plugins)
Connectors

- Plugins

[Plugins](https://www.claude.com/marketplace/plugins)
Plugins

- Skills

[Skills](https://www.claude.com/skills)
Skills

Extensions

- Claude in Chrome

[Claude in Chrome](https://www.claude.com/claude-in-chrome)
Claude in Chrome

- Claude for Microsoft 365

[Claude for Microsoft 365](https://www.claude.com/claude-for-microsoft-365)
Claude for Microsoft 365

Models

- Mythos

[Mythos](../15-Claude-AI-Features/claude-mythos.md)
Mythos

- Fable

[Fable](../15-Claude-AI-Features/claude-fable.md)
Fable

- Opus

[Opus](../15-Claude-AI-Features/claude-opus.md)
Opus

- Sonnet

[Sonnet](../15-Claude-AI-Features/claude-sonnet.md)
Sonnet

- Haiku

[Haiku](../15-Claude-AI-Features/claude-haiku.md)
Haiku

Enterprise

- Overview

[Overview](../18-Industry-UseCases/enterprise.md)
Overview

- Claude Code for Enterprise

[Claude Code for Enterprise](../15-Claude-AI-Features/product-claude-code-enterprise.md)
Claude Code for Enterprise

Use cases

- AI agents

[AI agents](../18-Industry-UseCases/agents.md)
AI agents

- Code modernization

[Code modernization](../18-Industry-UseCases/code-modernization.md)
Code modernization

- Coding

[Coding](../18-Industry-UseCases/coding.md)
Coding

- Commerce

[Commerce](../18-Industry-UseCases/commerce.md)
Commerce

Departments

- Customer support

[Customer support](../18-Industry-UseCases/customer-support.md)
Customer support

- Cybersecurity

[Cybersecurity](../18-Industry-UseCases/cybersecurity.md)
Cybersecurity

- Legal

[Legal](../18-Industry-UseCases/legal.md)
Legal

- Sales

[Sales](../18-Industry-UseCases/sales.md)
Sales

Industries

- Financial services

[Financial services](../18-Industry-UseCases/finance.md)
Financial services

- Government

[Government](../18-Industry-UseCases/government.md)
Government

- Healthcare

[Healthcare](../18-Industry-UseCases/healthcare.md)
Healthcare

- Higher education

[Higher education](../18-Industry-UseCases/education.md)
Higher education

- K-12 teachers

[K-12 teachers](../18-Industry-UseCases/teachers.md)
K-12 teachers

- Life sciences

[Life sciences](../18-Industry-UseCases/life-sciences.md)
Life sciences

- Nonprofits

[Nonprofits](../18-Industry-UseCases/nonprofits.md)
Nonprofits

- Small business

[Small business](../18-Industry-UseCases/small-business.md)
Small business

Programs

- Startups

[Startups](../15-Claude-AI-Features/programs-startups.md)
Startups

- Scientists

[Scientists](../15-Claude-AI-Features/programs-claude-team-plan-for-research-labs.md)
Scientists

Developers

- Developer docs

[Developer docs](../02-Claude-Code-CLI/code-home.md)
Developer docs

- Developer blog

[Developer blog](https://claude.dev/)
Developer blog

- Community

[Community](https://www.claude.com/community)
Community

- Console

[Console](../04-API-Reference/Other/home.md)
Console

- Engineering at Anthropic

[Engineering at Anthropic](https://www.anthropic.com/engineering)
Engineering at Anthropic

Platform

- Overview

[Overview](https://www.claude.com/platform/api)
Overview

- Marketplace

[Marketplace](https://www.claude.com/marketplace)
Marketplace

- Claude on AWS

[Claude on AWS](../04-API-Reference/Other/partners-claude-on-aws.md)
Claude on AWS

- Google Cloud

[Google Cloud](../04-API-Reference/Other/partners-google-cloud.md)
Google Cloud

- Microsoft Foundry

[Microsoft Foundry](../04-API-Reference/Other/partners-microsoft-foundry.md)
Microsoft Foundry

Resources

- Blog

[Blog](https://www.claude.com/blog)
Blog

- Claude partner network

[Claude partner network](../04-API-Reference/Other/partners.md)
Claude partner network

- Claude Academy

[Claude Academy](https://academy.claude.com/)
Claude Academy

- Customer stories

[Customer stories](../18-Industry-UseCases/customers.md)
Customer stories

- Events

[Events](https://www.anthropic.com/events)
Events

- Powered by Claude

[Powered by Claude](../04-API-Reference/Other/partners-powered-by-claude.md)
Powered by Claude

- Service partners

[Service partners](https://www.claude.com/marketplace/service-partners)
Service partners

Help and security

- Availability

[Availability](https://www.anthropic.com/supported-countries)
Availability

- Check files

[Check files](https://claude.com/check-files)
Check files

- Regional compliance

[Regional compliance](https://www.claude.com/regional-compliance)
Regional compliance

- Report abuse

[Report abuse](https://claude.com/form/anthropic-content-reporting)
Report abuse

- Security and compliance

[Security and compliance](https://trust.anthropic.com/)
Security and compliance

- Status

[Status](https://status.anthropic.com/)
Status

- Support center

[Support center](https://support.claude.com/en/)
Support center

Company

- Anthropic

[Anthropic](https://www.anthropic.com/)
Anthropic

- Careers

[Careers](https://www.anthropic.com/careers)
Careers

- Policy

[Policy](https://www.anthropic.com/policy)
Policy

- Research

[Research](../19-Reference/anthropic-com-research.md)
Research

- Anthropic news

[Anthropic news](../19-Reference/news.md)
Anthropic news

- Policy on the AI Exponential

---

## Connect to Microsoft 365 | Claude Help Center

Source: https://support.claude.com/en/articles/15183774
Path: 14-Connectors/connect-to-microsoft-365.md

# Connect to Microsoft 365

Connecting Microsoft 365 lets Claude search and analyze content across SharePoint, OneDrive, Outlook, and Teams in your work account. If your admin has enabled write tools, Claude can also draft and send emails, manage calendar events, create and update files, and send Teams messages. Ask Claude for what you need, and it pulls the right information or takes the action.

The Microsoft 365 connector is available on all Claude plans: Free, Pro, Max, Team, and Enterprise.

## Before you connect

You'll need a work Microsoft 365 account tied to a Microsoft Entra tenant. Personal Microsoft accounts (such as @outlook.com, @hotmail.com, or @live.com) can't be used. If you're not sure whether your account qualifies, check with your IT administrator.

**Important:** Before anyone in your organization can connect Microsoft 365, an admin needs to set it up. On Team and Enterprise plans, your Claude organization Owner enables Microsoft 365 for the organization. In every tenant, a Microsoft Entra Global Administrator also needs to grant a one-time consent. For details on the admin side, see **[Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-)**.

## Connect Microsoft 365

Once your admin has finished setup:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Find **Microsoft 365** in the list and click “Connect.”

3. Sign in with your Microsoft 365 credentials when prompted.

**Note:** Once you've connected Microsoft 365 to your Claude account, you can also use it on Claude for iOS and Claude for Android.

## Use Microsoft 365 with Claude

Ask Claude a question that needs information from your Microsoft 365 data. Claude detects which tools it needs and retrieves the relevant content.

### Example queries

- "Find the Q4 strategic planning document in SharePoint."

- "Summarize email conversations about the product launch."

- "What discussions happened in the Teams channel about the marketing campaign?"

- "Review meeting notes from last week's leadership sync."

- "Draft a reply to the latest email from the vendor, but don't send it."

- "Schedule a 30-minute sync with the design team next Tuesday."

- "Post a summary of this thread in the \#project-updates channel in Teams."

### What Claude can do

**SharePoint and OneDrive**

- Search documents across SharePoint sites and libraries to locate project specifications, strategic plans, and other business documents.

- Access files stored in your OneDrive and have Claude analyze content without manually uploading them.

- Consolidate information from distributed file locations and analyze trends across multiple documents.

**Outlook email**

- Search email threads and conversations to track project status, client feedback, and team alignment.

- Access message content and metadata, filtering by date, sender, subject, and other criteria.

- Find specific information from past correspondence.

**Outlook Calendar**

- Review meeting summaries, attendee information, and content to prepare for upcoming meetings or catch up on ones you missed.

- Analyze scheduling patterns and track project decisions.

**Teams**

- Access Teams chat messages and channel discussions where you're a participant.

- Review team collaboration patterns and find decisions made across conversations.

**Write tools**

If your admin has enabled write tools for your organization, Claude can also:

- Draft, send, and organize email, including managing categories, inbox rules, and automatic replies.

- Create, update, and delete calendar events.

- Create and update files in OneDrive and SharePoint.

- Send a Teams chat message, post or reply in a channel, or start a new chat.

When Claude sends an email, it includes a message header identifying it as agent-initiated. Teams messages, file writes, and calendar writes aren't currently tagged. Write tools are subject to per-user limits.

**Note:** Attachments aren't currently supported in write tools—Claude can't send, forward, or draft emails with attachments.

**Note:** Your admin turns on each Teams write tool separately. Sending a chat message and posting or replying in a channel always ask you to confirm before Claude sends anything.

## Supported file types

When reading files from SharePoint and OneDrive, Claude can open these formats:

- **Word, Excel, and PowerPoint**, including older .doc, .xls, and .ppt files

- **PDF**

- **Plain-text files**: .txt, .md, .csv, .tsv, .json, .xml, .html, .htm, and .log

Files in any other format can't be read. They still appear in search results because they're ordinary files in your libraries, but when Claude tries to open one, you'll see a "mime type '...' is not allowed" error.

**Note:** OneNote isn't supported. Notebooks show up in search results, but read attempts return a "mime type 'application/msonenote' is not allowed" error. To bring OneNote content into Claude, export pages or sections to Word or PDF in the same library.

## Manage your connection

### Turn individual tools on or off

You can selectively turn off specific tools within Microsoft 365—for example, you might keep document search on but turn off email access. To do this:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Click on “Microsoft 365.”

3. Toggle the tool on or off under **Tool permissions**.

### Turn the connector on or off per chat

You can also enable or disable Microsoft 365 in a specific conversation.

1. Click the “+” button on the lower left corner of the chat window.

2. Hover over “Connectors.”

3. Find **Microsoft 365** in the list and toggle it on or off.

### Disconnect Microsoft 365

Disconnecting removes Claude's access to your Microsoft 365 data. Reconnecting later doesn't require admin reapproval as long as your admin's consent is still active.

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Find Microsoft 365 in your connected services.

3. Click “Disconnect.”

## What Claude can access

Microsoft 365 stays under your control once connected. A few things to keep in mind:

- **Your permissions apply.** Claude can only access data you can already see in Microsoft 365. If you don't have access to a SharePoint site or aren't a member of a private Teams channel, Claude can't reach that content either.

- **On-demand only.** Claude only accesses Microsoft 365 when you ask a question that needs it. It doesn't run background searches.

- **Write tools are admin-controlled.** Claude can always search and analyze your data. Whether Claude can also take actions like sending email, updating your calendar, creating files, or sending Teams messages depends on what your admin has enabled. Claude can't change Teams settings or permissions.

- **You can disconnect any time.** Use the steps above to remove Claude's access.

For the full list of permissions the integration requests, see **[Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-)** or the **[Microsoft 365 connector security guide](https://support.claude.com/en/articles/12684923-)**.

------------------------------------------------------------------------

## Troubleshooting

### Authentication is failing

1. Confirm you're using a Microsoft 365 work account tied to a Microsoft Entra tenant. Personal Microsoft accounts (@outlook.com, @hotmail.com, @live.com) aren't supported.

2. Confirm your Microsoft 365 license is active.

3. If you're not a Microsoft Entra Global Administrator, check with your admin that tenant-wide consent has been granted for Microsoft 365. Without this, you'll see an error during authentication.

4. Your IT team may need to approve third-party app access. If your organization restricts unapproved apps, ask your admin to check organizational policies.

5. Try a different browser, or disable ad blockers and privacy extensions that might block authentication popups.

6. Clear cookies and cache and try again.

### Claude says it can't find a document I know exists

1. Verify you can access the document directly in Microsoft 365.

2. Make sure the document is in SharePoint or OneDrive, not stored locally on your machine.

3. Recently uploaded files may take time to become searchable.

4. Try specifying the SharePoint site or library name in your prompt.

5. Search by exact file name or unique keywords from the document.

### Search results are incomplete or irrelevant

- Be specific about what you're looking for.

- Specify locations, such as site names, date ranges, or document types.

- Use exact phrases for better matching.

- Break complex questions into simpler, more focused ones.

- Double-check spelling of names, projects, or technical terms.

------------------------------------------------------------------------

## Frequently asked questions

### Can Claude modify my Microsoft 365 data?

Only if your admin has enabled write tools. When they're enabled, Claude can draft and send emails, manage calendar events, create and update files, and send Teams messages (a chat message, a post or reply in a channel, or a new chat), always within your existing Microsoft 365 permissions. When they're not enabled, the integration is read-only. Either way, Claude can't change Teams settings or permissions. Attachments also aren't supported in write tools, so Claude can't send, forward, or draft emails with attachments.

### Does Claude search shared drives and team sites?

Yes. Claude can search any SharePoint sites and shared drives you have permission to access, including team sites, communication sites, document libraries, and shared OneDrive folders.

### How do I tell Claude to search a specific place?

Be specific in your prompts:

- *"Search the Engineering team site in SharePoint for architecture documents."*

- *"Find emails from the last week about the Q4 budget."*

- *"Show me Teams discussions with Sarah about the product roadmap."*

- *"Find PowerPoint presentations in SharePoint about sales strategy."*

### Can I point my project at a specific Sharepoint site?

No, `Sites.Selected` is not supported, so you can't scope the Microsoft 365 connector to an allowlist of specific SharePoint sites. The connector searches across all SharePoint content you already have permission to access.

### Why can't Claude read OneNote notebooks?

OneNote isn't currently a supported file type. Notebooks show up in SharePoint search results because they're ordinary files in your libraries, but Claude can't open them, so read attempts return a "mime type 'application/msonenote' is not allowed" error. To work with OneNote content in Claude, export pages or sections to Word or PDF. For the full list of formats Claude can read, see **[Supported file types](#h_ddeb82923f)** above.

### Can Claude search shared mailboxes?

Yes. Claude can search shared mailboxes you have delegate access to in Microsoft 365. This includes full access shared mailboxes and folder-level delegation, such as when you can see only the inbox of another mailbox. Search access follows your existing Microsoft 365 permissions: if you can open a shared mailbox in Outlook, Claude can search it.

### Can Claude search archived emails?

Yes, but only if they're in your primary mailbox. Claude can search every folder in your primary Outlook mailbox, including its Archive folder. Claude doesn't search the separate Online Archive mailbox (also called the In-Place Archive), so messages that a retention policy has moved there won't appear in results. To work with one of those messages, move it back into a folder in your primary mailbox, or open it in Outlook and paste the content into your chat.

### Can Claude summarize long email threads?

Yes. Try a prompt like *"Summarize the email thread about the vendor selection process."* Claude will read the thread and provide a summary with key points and decisions.

### Why don't I see write tools?

Write tools require extra setup on the admin side: a Microsoft Entra administrator needs to consent to updated permissions, and your organization needs to enable write tools for your account. If you connected before write tools launched, ask your admin to complete both steps. For details, see **[Set up the Microsoft 365 connector](enabling-and-using-the-microsoft-365-connector.md)**.

### Why does Claude ask me to confirm before sending a Teams message?

Sending a chat message and posting or replying in a channel always require your confirmation. Your admin can't set these to send automatically. Starting a new chat can be set to run without confirmation if your admin allows it.

### Can Claude access private Teams channels?

Only ones you're a member of. Claude mirrors your Microsoft 365 permissions, so if you can see a private channel, Claude can search it; if you're not a member, it can't.

### What if I try to connect before my admin has set things up?

You'll see an error indicating that an administrator must grant app permissions before you can connect. Ask your organization’s Microsoft Entra Global Administrator to complete consent. If you're on a Team or Enterprise plan, your Claude organization owner also needs to enable Microsoft 365 in organization settings.

---

## Set up the Microsoft 365 connector | Claude Help Center

Source: https://support.claude.com/en/articles/12542951
Path: 14-Connectors/enabling-and-using-the-microsoft-365-connector.md

# Set up the Microsoft 365 connector

This article walks admins through enabling the Microsoft 365 connector for their organization in Claude—including granting Microsoft Entra consent, restricting access, and managing permissions. Once setup is complete, people in your tenant can connect Microsoft 365 to their own Claude accounts to search across SharePoint, OneDrive, Outlook, and Teams from Claude. You can also enable write tools, which let Claude send email, manage calendar events, create and update files, and send Teams messages on a member's behalf.

The Microsoft 365 connector is available on all Claude plans: Free, Pro, Max, Team, and Enterprise.

For end-user instructions on connecting and using Microsoft 365 once setup is complete, see **[Connect Claude to Microsoft 365](connect-to-microsoft-365.md)**.

**Important:** The Microsoft 365 connector requires a Microsoft Entra tenant tied to a Microsoft Business plan. Personal Microsoft accounts (such as @outlook.com or @hotmail.com addresses) can't be used to connect.

------------------------------------------------------------------------

## Setup overview

Two things need to happen before anyone in your organization can connect Microsoft 365, plus an optional third step if you want to enable write tools:

1. **On Team and Enterprise plans:** A Claude organization owner enables the Microsoft 365 connector for the organization.

2. **In every tenant:** A Microsoft Entra Global Administrator grants a one-time consent that authorizes the integration for your tenant.

3. **To enable write tools:** A Microsoft Entra administrator consents to the updated permission set, and you enable write tools for your organization. See **[Enable write tools](#h_a51d877afd)** below.

After completing these steps, members can connect Microsoft 365 to their own Claude accounts following the steps in **[Connect Claude to Microsoft 365](connect-to-microsoft-365.md)**.

## Enable the connector for your organization

This step applies to Team and Enterprise plans only. On Free, Pro, and Max plans, skip to the next section.

1. Sign in to Claude.

2. Navigate to **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

3. Click “+ Add” at the top of the page, then “All available.”

4. Find **Microsoft 365** and click “Add to your team.”

## Grant Microsoft Entra admin consent

A Microsoft Entra Global Administrator in your tenant needs to authorize the integration before anyone can connect. There are two ways to do this.

### Option 1: Consent through Claude

If your Microsoft Entra Global Administrator has a Claude account, they can grant consent during the standard connection flow:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Find **Microsoft 365** and click “Connect.”

3. Authenticate with Microsoft 365 credentials.

4. Review and accept the requested permissions, checking the box to grant access on behalf of the whole organization.

After this, other people in the same Entra tenant can connect by following the standard end-user steps. They won't see the consent prompt—they'll just authenticate and start using the integration.

### Option 2: Manual setup in Microsoft Entra ID

Use this path if your Microsoft Entra Global Administrator doesn't have a Claude account, or if you need to troubleshoot the app install and permissions setup. You can add the connector apps and grant admin consent directly in Microsoft Entra ID.

This process adds two service principals to your tenant. Each principal establishes a service-level identity for one of the two M365 MCP for Claude app registrations, allowing them to access and interact with your organization's data and resources via the Microsoft Graph API.

**1. Add the service principals**

Using Microsoft Graph Explorer, add both required service principals:

M365 MCP Client for Claude:

POST https://graph.microsoft.com/v1.0/servicePrincipals
{"appId":"08ad6f98-a4f8-4635-bb8d-f1a3044760f0"}

M365 MCP Server for Claude:

POST https://graph.microsoft.com/v1.0/servicePrincipals
{"appId":"07c030f6-5743-41b7-ba00-0a6e85f37c17"}

**2. Grant admin consent**

Construct and visit the following URLs in your browser, replacing {your-tenant-id} with your organization's tenant ID.

M365 MCP Client for Claude:

https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=08ad6f98-a4f8-4635-bb8d-f1a3044760f0

M365 MCP Server for Claude:

https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=07c030f6-5743-41b7-ba00-0a6e85f37c17

When you visit each URL, you'll be prompted to consent to the delegated permissions required by the integration on behalf of your organization.

**3. Finish setup**

- **Team and Enterprise plans:** A Claude organization Owner needs to enable the connector in **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**. Then members can connect individually.

- **Free, Pro, and Max plans:** Members can connect by navigating to **[Customize \> Connectors](https://claude.ai/customize/connectors)**, finding **Microsoft 365**, and clicking “Connect.”

### Restrict who can use the connector

To limit which people in your tenant can authenticate to Microsoft 365 through Claude:

1. Go to the Microsoft Entra admin center at entra.microsoft.com.

2. Navigate to the **M365 MCP Server for Claude** enterprise application.

3. Go to **Properties** and set **Assignment required?** to “Yes.”

4. Under **Users and groups**, add the specific users or groups who should have access.

5. Repeat the same steps for the **M365 MCP Client for Claude** enterprise application.

Both components need to be restricted to the same set of authorized people.

### Restrict which permissions the connector can use

To limit which types of resources the integration can access, selectively revoke permissions from the default set of authorized scopes. This requires Microsoft Entra admin access.

1. As a Microsoft Entra admin, go to entra.microsoft.com.

2. Select “Enterprise Applications.”

3. Next to the search box, remove the application type filter.

4. Search for and click “M365 MCP Server for Claude.”

5. Go to **Permissions**.

6. Under the **Admin consent** tab and in the Microsoft Graph list of permissions, select the permission you would like to revoke and click the “**…**” button.

7. Select “Revoke permission” and confirm with “Yes, revoke.”

Once revoked, attempts to access a resource with that permission will return a "Failed to call tool" error.

Members can also individually turn off specific tools in their own Microsoft 365 settings to prevent Claude from trying to access a tool for which the permission has been revoked.

To restore a revoked permission, follow the steps to grant admin consent described in **Option 2: Manual setup in Microsoft Entra ID**. This will revert the permissions to the default state.

------------------------------------------------------------------------

## Enable write tools

Write tools let Claude send email, manage drafts and calendar events, update mailbox settings, and create and update files in OneDrive and SharePoint, and send messages in Microsoft Teams. Read and search tools work the same whether or not write tools are enabled.

**1. Re-consent to the updated permissions**

The connector's permission set now includes additional Microsoft Graph scopes to support write tools. If your tenant consented before write tools or the Teams write tools launched, a Microsoft Entra Global Administrator needs to review and approve the updated permission set before write tools activate. Review and approve the updated permissions for the connector in your tenant's **Enterprise Applications** consent flow.

**2. Enable write tools for your organization**

If your organization was using the connector before write tools launched, they will be blocked by default. Enable them for everyone by going to **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**, finding “Microsoft 365,” and setting the appropriate permissions. Enterprise plans can enable them for a subset of users through **[custom roles](https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans#h_979e558d00)**. For Microsoft Teams specifically, set each Teams write tool individually: the send, post, and reply tools can be set to Ask or Blocked (members confirm each send), and starting a new chat can also be set to Allow. The connector-wide "all tools" permission on its own doesn't turn these on.

**3. Verify**

Once enabled, ask Claude to perform a low-risk write action, such as "Draft an email to myself, but don't send it," to confirm write tools are active.

**Note:** Emails Claude sends include an attribution header identifying them as agent-initiated. File writes, calendar writes, and Teams messages aren't currently tagged. Attachments aren’t supported in write tools, so sending, forwarding, and drafting all reject messages with attachments. Write tools are also subject to per-user limits on writes, sends, and recipients.

------------------------------------------------------------------------

## Permissions reference

The Microsoft 365 connector uses **delegated permissions**, meaning Claude acts on behalf of each individual user and can only access data that user already has permission to view in Microsoft 365. Permissions are read-only by default. Claude can only send, create, or update content if you enable write tools.

During authentication, the integration requests the following permissions:

**Basic access**

- `User.Read`: Sign in and read user profile

- `openid`: Sign in with organizational account

- `offline_access`: Maintain access to data

- `email`: View email address

- `profile`: View basic profile information

**Email (Outlook)**

- `Mail.Read`: Read email messages

- `Mail.ReadBasic`: Read email metadata (sender, subject, date)

- `Mail.Read.Shared`: Read emails in mailboxes the user has access to

- **Note:** Shared mailbox access is included through the `Mail.Read.Shared` permission. Users can search shared mailboxes they have delegate access to in Microsoft 365, including full access and folder-level delegation. No setup is needed beyond standard admin consent and the delegate permissions already configured in Microsoft 365.

- `MailboxFolder.Read`: Read mailbox folder structure

- `MailboxItem.Read`: Read items in mailbox

- `MailboxSettings.Read`: Read mailbox settings, like the user's timezone

**Note:** Email search covers each user's primary mailbox, including its Archive folder, and any shared mailboxes they can access. It doesn't cover the separate Online Archive mailbox (also called the In-Place Archive), so messages that a retention policy has moved there won't appear in results.

**Calendar**

- `Calendars.Read`: Read calendar events

- `Calendars.Read.Shared`: Read calendars shared with the user

**Teams chat**

- `Chat.Read`: Read Teams chat messages

- `Chat.ReadBasic`: Read Teams chat metadata

- `ChatMember.Read`: Read information about chat participants

- `ChatMessage.Read`: Read Teams chat messages

**Teams channels**

- `Channel.ReadBasic.All`: Read channel names and descriptions

- `ChannelMessage.Read.All`: Read channel messages

**Meetings**

- `OnlineMeetings.Read`: Read online meetings

- `OnlineMeetingTranscript.Read.All`: Read meeting transcripts

- `OnlineMeetingAiInsight.Read`: Read AI-generated meeting insights

- `OnlineMeetingArtifact.Read.All`: Read meeting recordings and artifacts

- `OnlineMeetingRecording.Read.All`: Read meeting recordings

**Files (OneDrive and SharePoint)**

- `Files.Read`: Read user files

- `Files.Read.All`: Read all files the user can access

- `Sites.Read.All`: Read items in SharePoint sites

**Write permissions**

The following permissions support write tools and are included in the updated consent set:

- `Mail.Send`: Send and forward email

- `Mail.ReadWrite`: Create, update, and delete drafts; move and label messages

- `Calendars.ReadWrite`: Create, update, delete, and respond to calendar events

- `Files.ReadWrite.All`: Create and update files in OneDrive and SharePoint

- `MailboxSettings.ReadWrite`: Manage categories, inbox rules, and automatic replies

- `ChatMessage.Send`: Send a Teams chat message on the user's behalf

- `ChannelMessage.Send`**:** Post or reply in a Teams channel

- `Chat.Create`: Start a new chat on the user’s behalf

- `People.Read`: Find people in the organization to start a chat with

**User directory**

- `User.ReadBasic.All`: Read basic profile information for all users in the organization (used for finding meeting availability)

The Microsoft 365 connector searches SharePoint across the entire tenant using the permissions of the user. Site-specific search restriction isn't supported.

## Privacy and security

- **Permission inheritance:** Claude mirrors each user's existing Microsoft 365 permissions. Members can't access anything through Claude that they couldn't already see directly in Microsoft 365.

- **On-demand access:** Claude only accesses data when a user explicitly asks a question that requires it.

- **Revocable access:** Members can disconnect their own integration through **[Customize \> Connectors](https://claude.ai/customize/connectors)**. Team and Enterprise plan Owners can also remove the connector for the entire organization in **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

For more detail, see the **[Microsoft 365 connector security guide](https://support.claude.com/en/articles/12684923-)**.

------------------------------------------------------------------------

## Troubleshooting

### A member can't authenticate

1. Confirm their account is tied to a Microsoft Entra tenant, not a personal Microsoft account.

2. Confirm their Microsoft 365 license is active.

3. Confirm admin consent has been granted using Option 1 or Option 2 above.

4. Check whether a Conditional Access policy in your tenant is blocking the connection. See below: **[Conditional Access is blocking the connection](#h_c7635fb6e2)**.

### Members are seeing "Failed to call tool" errors

A permission may have been selectively revoked in Microsoft Entra. Members can turn off the corresponding tool in their Microsoft 365 settings to suppress the error, or you can restore the permission by repeating the admin consent steps in **[Option 2: Manual setup in Microsoft Entra ID](#h_c5f095c9cf)**.

### Write tools aren't appearing for members

1. Confirm a Microsoft Entra administrator has consented to the updated permission set that includes write scopes.

2. Confirm write tools are enabled in the Microsoft 365 connector configuration, or that the member is covered by a role-based access policy that grants them.

3. Have the member disconnect and reconnect Microsoft 365 in **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

### Conditional Access is blocking the connection

A Conditional Access block shows up in one of three ways:

- A user sees "Authorization with the MCP server failed" and a reference code starting with `ofid_` when they try to connect. Our Support team can look up that code.

- A member who is already connected gets an error when Claude uses a Microsoft 365 tool. The error includes an `AADSTS` code, a note that the request was blocked by a Conditional Access policy, and the Trace ID and Correlation ID you can search for in Entra.

- Members are asked to reconnect Microsoft 365 on a regular cycle, much more often than the normal 90-day expiry. This usually means a sign-in frequency policy.

Connecting Microsoft 365 involves more than the sign-in the member sees. After the member signs in to Microsoft in their browser, Claude's servers exchange that sign-in for access tokens, and later exchange those tokens for Microsoft 365 access on the member's behalf. In our testing, Entra evaluates your Conditional Access policies against these server-side requests as coming from Anthropic's IP range, `160.79.104.0/21`. They identify the member and carry the device recorded when the member connected, not the member's current device or network. So a policy can pass the member's own sign-in and still block the connection a moment later, or block it days later. Learn more about **[Anthropic's IP addresses](../04-API-Reference/Endpoints/ip-addresses.md)**.

**Find the policy that's blocking the connection**

1. In the Microsoft Entra admin center, go to **Sign-in logs** and open the **User sign-ins (non-interactive)** tab. The member's own sign-in appears on the interactive tab and usually shows as successful, so the block is rarely there.

2. Filter by the affected member. The blocked requests can appear under either **M365 MCP Server for Claude** or **M365 MCP Client for Claude**, so filtering by member is more reliable than filtering by application. Don't filter by resource, which hides some of the rows.

3. Open the failed entry and select the **Conditional Access** tab. It names the policy that blocked the request.

The error code tells you what kind of policy it is:

- `AADSTS70043`: a sign-in frequency policy. See the next section.

- `AADSTS53003`: a policy set to block access. The Conditional Access tab tells you which one. If it's based on location, see the next section.

- `AADSTS50076`: a policy required multi-factor authentication on a server-side request. Disconnecting and reconnecting Microsoft 365 clears it. If it keeps happening, see the **[Microsoft 365 connector security guide](microsoft-365-connector-security-guide.md)**.

- `AADSTS53000`: a policy requires a compliant device. The similar code `AADSTS530003` means a policy requires a managed device. In both cases the member needs to reconnect from a device that meets the policy. Learn more in the **[Microsoft 365 connector security guide](microsoft-365-connector-security-guide.md)**.

**Exclude Anthropic's IP range from sign-in frequency and location policies**

Because the server-side requests come from Anthropic's IP range, a policy that limits sign-ins to your own network, or that enforces a sign-in frequency, blocks them for every member. Excluding the two Claude applications from the policy isn't enough on its own. We recommend excluding Anthropic's IP range from the policy as well.

**Note:** Don't use this exclusion for a device compliance policy. The server-side requests carry the device recorded when the member connected, so a device policy still applies to them, and excluding Anthropic's IP range would turn the device check off for the connector. Members blocked by a device policy need to reconnect from a device that meets it. Learn more in the **[Microsoft 365 connector security guide](microsoft-365-connector-security-guide.md)**.

If the policy that blocked the request is a sign-in frequency or location policy:

1. In the Microsoft Entra admin center, go to **Conditional Access \> Named locations** and create an IP range location containing `160.79.104.0/21`. Leave **Mark as trusted location** unchecked so the exclusion doesn't affect other policies that use trusted locations.

2. Open the policy that blocked the request and go to **Conditions \> Locations \> Exclude**.

3. Add the named location you created. Keep any existing exclusions for the Claude applications in place.

4. Save the policy and wait a few minutes for the change to apply.

5. Have an affected member disconnect and reconnect Microsoft 365 in **Customize \> Connectors**.

**Note:** Excluding the range lifts the policy for every request that comes from Anthropic's addresses, which means all Microsoft 365 connector activity for all of your members. For a sign-in frequency policy, this also means the connector's background requests are no longer subject to it, so a connection stays signed in until it expires after 90 days of inactivity. If you'd rather keep the periodic reconnects, leave the policy as it is. Members who are asked to reconnect can sign out of Microsoft in their browser, or use a private browsing window, before reconnecting. If you want to check the effect of a change before making it, clone the policy in report-only mode first.

------------------------------------------------------------------------

## Frequently asked questions

### What happens if a member tries to connect before consent is granted?

They'll see an error message indicating that an administrator must grant app permissions before they can use the integration. The connection will fail until a Microsoft Entra Global Administrator approves the necessary permissions.

### Can the Microsoft 365 connector be used with enterprise search?

Yes. When enterprise search is enabled, it can query Microsoft 365 alongside other connected services for unified search across Slack, Google Workspace, Microsoft 365, and more.

### What file types can the connector read?

Claude reads Word, Excel, PowerPoint (including older .doc, .xls, and .ppt files), PDF, and plain-text formats such as .txt, .md, and .csv from SharePoint and OneDrive. Other formats, including OneNote, can't be read. For the full list, see **[Connect to Microsoft 365](https://support.claude.com/en/articles/15183774-connect-to-microsoft-365#h_ddeb82923f)**.

### Can the integration modify Microsoft 365 data?

Only after an Entra admin grants write scopes. With write tools on, Claude can send email, manage drafts and calendar events, update mailbox settings, create and update files in OneDrive and SharePoint, and send messages in Microsoft Teams (post/reply in a channel, send a chat message, or start a new chat on the user's behalf), always within each member's existing Microsoft 365 permissions. Without them, the integration is read-only. Claude still can't change Teams settings or permissions, only send messages.

---

## Get started with Claude Compliance API integrations | Claude Help Center

Source: https://support.claude.com/en/articles/15167101-get-started-with-claude-compliance-api-integrations
Path: 14-Connectors/get-started-with-claude-compliance-api-integrations.md

# Get started with Claude Compliance API integrations

Updated today

Security and compliance platforms have built integrations on top of the Claude Compliance API, so your team can monitor Claude activity within the tools you already use. Integrations are available from security and compliance providers across the categories enterprises rely on, spanning DLP, SASE, data security, SIEM and security operations, identity, eDiscovery, AI security posture management, and AI observability and telemetry infrastructure.

This article lists available Compliance API integrations with a link to their setup documentation. If you're a security, compliance, or IT platform that has built a Compliance API integration, **[apply here to join the program](https://forms.gle/1rkBcdwwR5bLLD82A)**.

The Claude Compliance API is available to Claude Enterprise plans and Claude Platform customers.

## What data you can access

The Compliance API provides access to different data depending on the product:

- **Claude Enterprise:**

- **Conversation content** including chats, uploaded files, and projects

- **Session content from Cowork (via Claude, Claude Desktop, and Claude Mobile) and Claude Code (via CLI and Claude Desktop).** Includes prompts and responses, tool calls content, and skills and artifacts content captured as transcript text.

- **Session content from the Claude for Microsoft 365 add-ins (Excel, Word, PowerPoint, and Outlook) and Claude Science**, in beta. Includes prompts and responses, plus drafted emails, formulas, and document text from the Microsoft 365 add-ins.

- **Activity feed events** covering user logins, admin actions, and configuration changes

- **Claude Platform:**

- **Activity feed events**, including admin and system events (such as member and workspace changes, API key creation, and account settings) and resource events (such as file creation, downloads, and skill changes)

- **Note:** Conversation content (prompts and model responses) is not available through the Compliance API for the Claude Platform.

## How to set up an integration

For Claude Enterprise customers, using an integration is straightforward:

1. Ask your organization's Primary Owner to enable the Compliance API (only the Primary Owner can do this), then create an access key—Owners can create keys limited to their own organization. Learn how to **[access the Compliance API](https://support.claude.com/en/articles/13015708-access-the-compliance-api)**.

2. Connect your instance to a supported security platform. Setup guides are available in the **[Available integrations section](#h_7ff9e34f8e)**.

Claude activity will flow into the same dashboards and workflows your team uses for every other application.

**Important**: For Claude Enterprise organizations, only your organization's Primary Owner can enable the Compliance API, from **[Organization settings \> API](https://claude.ai/admin-settings/api-access)**. You can create a key on the same page by clicking "+Create key" under **Keys**: the Primary Owner can create a key covering every linked organization, and Owners can create keys limited to their own organization. Owners see this page but not the **Compliance API** toggle—only the Primary Owner can turn the API on or off. Admins don't see the page at all. If your organization is linked to a parent organization, the parent organization's Primary Owner enables it and the setting applies to every linked organization.

For Claude Platform, contact your Anthropic sales team. Review **[Compliance API documentation](../04-API-Reference/Other/manage-claude-compliance-api.md)** on Claude API Docs.

## Available integrations

- **Above Security:** Above Security brings enterprise Claude activity - claude.ai chats and Claude Code, Cowork, and remote Cowork sessions - into its AI-powered insider risk platform via the Claude Compliance API. Read-only and privacy-preserving, it gives security teams evidence-grounded, automated investigations of how people use Claude across the organization. To set up this integration, see the **[Above Security setup guide](https://www.above.security/integrations)**.

- **Air:** Air utilizes the Claude Compliance API as a core part of its agentic security platform, giving security teams unified posture management, real-time runtime protection, and supply-chain governance across all of their endpoint, cloud, and SaaS agents from a single control plane. To set up this integration, see the **[Air setup guide](https://www.air.security/claude-air-integration)**.

- **Airia:** Airia's integration with the Compliance API gives security and risk teams policy enforcement, automated compliance reporting, and continuous audit trails across Claude usage, so enterprises can detect risky behavior, enforce governance policies, and demonstrate regulatory compliance with confidence. To set up this integration, see the **[Airia setup guide](https://explore.airia.com/integrations/Tools/anthropic-compliance-api)**.

- **aizome:** aizome discovers and inventories how Claude is used across your organization—users, agents, projects, skills, MCP servers, and connectors—surfacing governance risks, producing audit reports, and deciding which agents to onboard into an identity-aware control plane with scoped permissions, just-in-time access, and full auditability. Learn more about **[aizome's integration with the Claude Compliance API](https://www.aizome.ai/integrations).**

- **Akeyless Security:** Akeyless gives Claude agents secretless, just-in-time access to the systems they act on—databases, cloud services, and SaaS APIs—removing standing credentials and ensuring each agent performs only its permitted task, with a full audit trail of every action. To set up this integration, see the **[Akeyless Security setup guide](https://www.akeyless.io/blog/securing-ai-agents-in-claude-demo-and-setup-guide/)**.

- **Akto:** Akto's Claude Compliance API integration gives security teams visibility into Claude Enterprise chats, files, connectors, and projects across AI agents, MCP servers, and human users—detecting prompt injection, sensitive-data exposure, and policy violations. To set up this integration, see the **[Akto setup guide](https://ai-security-docs.akto.io/akto-atlas-agentic-ai-security-for-employee-endpoints/endpoints-discovery-agents/anthropic-connector)**.

- **Alignmt AI:** Alignmt AI transforms Compliance API activity into a risk-scored inventory of every AI resource, surfacing autonomous automations, write-capable connectors, and sensitive-data exposure, with provenance on every fact and human attestation for what evidence can't resolve. Learn more about **[Alignmt AI's integration with the Claude Compliance API](https://www.alignmt.ai/post/alignmt-ai-integrates-with-anthropic-s-compliance-api)**.

- **Apiiro:** Apiiro uses the Compliance API activity feed to give security teams visibility into the AI coding agents, MCP servers, skills, and plugins active across their organization, correlating that activity with Apiiro's software supply chain risk model to surface unsafe or unauthorized components. Learn more about **[Apiiro’s integration with the Claude Compliance API](https://apiiro.com/blog/claude-compliance-api-now-in-the-apiiro-software-graph)**.

- **Artemis Security:** Artemis ingests Claude Compliance API data to detect and investigate malicious behavior, correlating Claude activity with the rest of the environment for machine-speed detection and response. To set up this integration, see the **[Artemis setup guide](https://artemissecurity.com/company-news/secure-your-enterprise-ai-artemis-now-integrates-with-anthropic-compliance-api-and-telemetry/)**.

- **Axonius:** Axonius brings Claude Enterprise into the Axonius Asset Cloud, reconciling directory and access artifacts against every other asset and exposure in your stack. Decision-grade asset intelligence surfaces coverage gaps, drift, and identity risk across the environment, mapped to the assets and owners behind them. To set up this integration, see the **[Axonius setup guide](https://docs.axonius.com/docs/anthropic)**.

- **Bay:** Bay secures AI agents in the enterprise—providing real-time visibility and enforcement for Claude across all endpoints, containers, and browsers. To set up this integration, see the **[Bay setup guide](https://bay.security/use-cases/platform/claude).**

- **Beacon Security:** Beacon is the platform for AI-native SecOps, serving as the data and context layer for security teams. Its Claude connector ingests Claude Enterprise activity and compliance data, normalizes and enriches it, and makes it available to security agents, SIEMs, data lakes, and compliance archives. Learn more about **[Beacon's integration with the Claude Compliance API](https://beacon.security/beacon-for-anthropic-compliance-api)**.

- **BigID:** BigID secures Claude usage by giving security teams visibility into every file shared with Claude, pinpointing exactly which sensitive attributes are present the moment a risky file is uploaded. Learn more about **[BigID's integration with the Claude Compliance API](https://bigid.com/blog/securing-claude/)**.

- **Bloom Security:** Bloom is the endpoint security platform for the AI-native era, giving security teams visibility and governance over every AI tool, plugin, and MCP server across their organization. The Claude Compliance API integration deepens that coverage—into every session, file, and configuration change across every user—so security teams can enable Claude at scale without losing control. To set up this integration, see the **[Bloom Security setup guide](https://bloom.security/anthropic-compliance-api-integration)**.

- **Bluebear Security:** Bluebear uses the Compliance API to continuously check a Claude Enterprise organization's security settings—including SSO enforcement, trusted devices, permission bypass, network egress, data retention, and connector auto-approval—against a secure baseline, opening an incident with remediation steps when a control drifts and tying Claude activity to what AI coding agents executed on developer machines. To set up this integration, see the **[Bluebear Security setup guide](https://bluebear.io/integrations/claude/)**.

- **Bold Security:** Prevent sensitive data from being misused by users or AI agents with real-time protection directly on the endpoint. To set up this integration, see the **[Bold Security setup guide](https://www.bold.security/blog/bold-security-extends-ai-data-protection-through-claudes-compliance-api)**.

- **Brava Security:** Brava ingests the Claude activity feed via the Compliance API and turns it into fully-leveraged security telemetry—routed into your existing SIEM, data lake, and archive, and searchable for investigation—so one feed powers monitoring, insider risk, retention, and governance with no custom collectors. To set up this integration, see the **[Brava Security setup guide](https://brava.security/integrations/anthropic-claude)**.

- **C1.ai:** C1.ai integrates with the Claude Compliance API to bring usage-informed access reviews, dormant-account detection, and automated lifecycle workflows to Claude Enterprise and Claude Platform—extending the same identity governance customers already run across the rest of their stack. To set up this integration, see the **[C1.ai setup guide](https://www.c1.ai/docs/baton/claude-enterprise)**.

- **Capsule Security:** Capsule connects to the Claude Compliance API to turn your organization's members, conversations, and activity into an auditable AI inventory, giving security and compliance teams continuous visibility, data-leakage detection, rogue-agent detection, and audit-ready governance over Claude usage. To set up this integration, see the **[Capsule Security setup guide](https://docs.capsulesecurity.io/guides/claude-enterprise)**.

- **Cato Networks:** Cato AI Security integrates with the Compliance API to secure, govern, and audit all Claude interactions, enforcing real-time policies, preventing data leakage, and maintaining comprehensive compliance visibility. To set up this integration, see the **[Cato Networks setup guide](https://www.catonetworks.com/integrations/ai-activity-monitoring/anthropic-compliance-api/)**.

- **Check Point:** Check Point's Workforce AI Security integration with the Claude Compliance API gives enterprises audit-grade visibility into Claude usage across surfaces and organization-level MCP servers—per-user and per-surface usage analytics plus content-level exposure analysis across chats and uploaded files, flagging PII, credentials, and regulated data for existing security workflows. To set up this integration, see the **[Check Point setup guide](https://sc1.checkpoint.com/documents/Infinity_Portal/WebAdminGuides/EN/Workforce-AI-Security-Admin-Guide/Topics-Workforce-AI-Security-AG/Integrations.htm?tocpath=Integrations%7C_____0)**.

- **CloudEagle.ai:** CloudEagle.ai integrates with the Compliance API to give IT and security teams first-party visibility into who uses Claude and whether their access is current, pairing activity data with usage and spend analytics and automated provisioning and deprovisioning—so Claude is governed alongside every other SaaS and AI tool. To set up this integration, see the **[CloudEagle.ai setup guide](https://www.cloudeagle.ai/app-integration/claude)**.

- **Cloudflare:** Cloudflare’s CASB integration provides security teams agentless visibility into posture, data, and compliance risks across their organization’s use of Claude. To set up this integration, see the **[Cloudflare setup guide](https://developers.cloudflare.com/changelog/post/2026-05-19-casb-claude-compliance-api/)**.

- **Clover Security:** Clover uses the Compliance API to give security teams organization-wide visibility into Claude Code usage—who's building with Claude Code, how much is already protected by Clover, and where the gaps are—then extends Clover's security controls to every developer. Learn more about **[Clover Security's integration with the Claude Compliance API](https://clover.security/blog/see-what-your-coding-agents-build-clover-integrates-with-anthropics-claude-compliance-api-to-give-security-real-time-visibility/)**.

- **Concentric AI:** Concentric AI Semantic DLP gives organizations visibility into the AI tools employees use, including shadow AI. Through its integration with the Compliance API, it captures every prompt, response, and attachment—including historical activity across Claude's browser and desktop apps—to strengthen governance, accelerate investigations, and demonstrate compliance. Learn more about **[Concentric AI's integration with the Claude Compliance API](https://concentric.ai/integrations/anthropic-compliance/)**.

- **Cribl:** The Claude Compliance API lets you ingest audit activity from Claude Enterprise and Claude Platform into Cribl Stream over HTTPS as a first‑class telemetry stream. It pulls user activities including authentication, chat interactions, file uploads, and administrative actions so you can normalize, enrich, mask, and route that data alongside the rest of your observability and security pipelines. To set up this integration, see the **[Cribl setup guide](https://docs.cribl.io/stream/sources-anthropic-compliance/)**.

- **CrowdStrike:** CrowdStrike built an integration with the Claude Compliance API that brings Claude activity into the Falcon platform, delivering real-time visibility, detection, and automated response through Falcon Next-Gen SIEM and CrowdStrike’s Agentic SOAR. It will further extend protection with Falcon AIDR and Falcon Shield to continuously detect, govern, and secure AI usage at scale. To set up this integration, see the **[CrowdStrike setup guide](https://marketplace.crowdstrike.com/listings/anthropic-data-connector/)**.

- **Cyberhaven:** Cyberhaven integrates with the Compliance API to give enterprise security teams visibility into the data their employees share with Claude, applying Cyberhaven's data classification engine to chats, files, and projects so customers can adopt Claude confidently while meeting their security and compliance requirements. To set up this integration, see the **[Cyberhaven setup guide](https://www.cyberhaven.com/support/anthropic-claude-enterprise-connector)**.

- **Cyera:** Cyera integrates with Claude Enterprise through the Claude Compliance API, giving security teams comprehensive visibility into conversations, files, and user activity across the platform. Every interaction is analyzed through OmniDLP and enriched with Cyera’s 95%-precision data classification and risk scoring, helping teams identify sensitive data exposure, detect risky or unsanctioned behavior, and maintain audit-ready oversight from day one. Deployment takes just minutes. **[Learn more about the integration](https://www.cyera.com/blog/cyera-and-anthropic-integrate-to-bring-real-time-ai-security-to-claude-enterprise)** and contact your Cyera Sales Rep to get started.

- **Dash Security:** Dash Security provides real-time, intent-aware monitoring and policy enforcement over Claude Enterprise conversations, detecting sensitive-data exposure, prompt injection, and risky behavior. By extracting conversational intent, Dash understands what users are actually doing with AI and distinguishes real threats from false positives and benign activity. To set up this integration, see the **[Dash Security setup guide](https://dash.security/integrations/claude-enterprise)**.

- **Datadog:** Datadog’s Claude Compliance ingests audit logs from the Claude Platform into Datadog, giving security teams visibility into admin activity, API key lifecycle events, and authentication events across their Claude organization for SIEM and compliance use cases. To set up this integration, see the **[Datadog setup guide](https://docs.datadoghq.com/integrations/anthropic-compliance-logs/).**

- **Daylight:** Monitor Claude usage in an organization for security investigations and compliance purposes. To set up this integration, see the **[Daylight setup guide](https://daylight.ai/claude-enterprise-detection)**.

- **Elastic:** Collect Claude audit and usage activity to detect security risks, support compliance requirements, and investigate AI-related incidents. To set up this integration, see the **[Elastic setup guide](https://www.elastic.co/docs/reference/integrations/anthropic)**.

- **Eon:** Eon provides AI governance for Claude through automated data classification and natural-language security queries, helping enterprises maintain visibility and control over sensitive data shared with AI tools. Learn more about **[Eon's integration with the Claude Compliance API](https://www.eon.io/integrations/claude-compliance-api)**.

- **eSentire:** eSentire Atlas integrates with the Compliance API to deliver 24/7 managed detection and response for Claude usage. eSentire ingests activity events and conversation content, correlates them with endpoint, identity, and cloud telemetry, and investigates and responds to threats and policy violations on customers' behalf. Learn more about **[eSentire's integration with the Claude Compliance API](https://www.esentire.com/what-we-do/mdr-and-platform-integrations)**.

- **Evoke Security:** Evoke Security provides runtime threat detection and response for AI agents, covering Claude Code and Cowork. Its Compliance API integration extends that coverage to the Claude Enterprise conversation layer, joining chats, files, projects, and activity events with endpoint telemetry in Evoke's detection and response platform. To set up this integration, see the **[Evoke Security setup guide](https://www.evokesecurity.com/blogs/evoke-anthropic-compliance-api).**

- **Exaforce:** Exaforce ingests Claude Compliance API activity, chat, and file data into the Exaforce Agentic SOC Platform, giving security teams a governed, SOC-ready view of Claude usage to monitor, detect, and investigate risky activity alongside their broader security signals. To set up this integration, see the **[Exaforce setup guide](https://www.exaforce.com/blogs/anthropic-integration)**.

- **ForceAI Security:** ForceAI PineSMITH integrates with the Anthropic Claude Compliance API to provide enterprise visibility into Claude activity, users, chats, files, projects, governance events, and audit-ready compliance data. To set up this integration, see the **[ForceAI Security setup guide](https://forceaisecurity.com/documents/claude-compliance-integration)**.

- **Forcepoint:** Forcepoint's solution to securely enable AI now extends to Claude Enterprise via the Claude Compliance API, ingesting every conversation, file upload, generated content and user activity into a unified AI governance dashboard. Security teams can apply existing DLP and DSPM policies across all Claude interactions, detecting sensitive data exposures, enforcing compliance, and maintaining a complete audit trail, with historical activity backfilled the moment the connector is deployed. To set up this integration, see the **[Forcepoint setup guide](https://www.forcepoint.com/use-case/securely-enable-ai)**.

- **Fortinet:** The Fortinet data security posture management integration with the Claude Compliance API enables organizations to monitor and analyze user interactions within Claude Enterprise, including prompts and uploaded files, to detect potential exposure of sensitive data such as PII, PHI, CHD, and authentication data. The integration provides visibility, alerting, and auditability for AI usage, helping security teams strengthen governance, compliance, and data protection across enterprise AI workflows. To set up this integration, see the **[Fortinet setup guide](https://www.fortinet.com/content/dam/fortinet/assets/alliances/fortidata-claude-setup-guide.pdf)**.

- **Geordie AI:** Geordie, the agentic security and governance platform, extends its existing coverage of the Claude suite, including Claude Code and Claude Cowork, across the full Claude Enterprise deployment surface through the Claude Compliance API. Together, this gives security and compliance teams a single, coherent view of every Claude use case and activity across the enterprise, with the visibility and controls to govern it. To set up this integration, see the **[Geordie AI setup guide](https://www.geordie.ai/resources/geordie-extends-agentic-ai-security-and-governance-coverage-through-claude-compliance-api/)**.

- **Glow:** Glow ingests the Compliance API activity feed to complete its picture of AI adoption and security posture across an organization's Claude workspace, enabling consistent governance and security controls across every form of Claude adoption, from individual users to managed deployments and agentic integrations. To set up this integration, see the **[Glow setup guide](https://docs.glow.io/integrations/anthropic)**.

- **Grip Security:** Grip integrates with the Anthropic Compliance API to deliver SSPM checks, remediation, and AI agent visibility for Claude. To set up this integration, see the **[Grip Security setup guide](https://help.grip.security/docs/anthropic-claude-compliance-api-integration-with-grip-security-1)**.

- **Hadrius:** Hadrius is the agentic compliance infrastructure for SEC- and FINRA-regulated firms. Its Claude integration captures conversations and activity into a compliant books-and-records archive with automated surveillance, so advisers and broker-dealers can adopt Claude while meeting their recordkeeping and supervision obligations. To set up this integration, see the **[Hadrius setup guide](https://support.hadrius.com/articles/8197408781-claude-integration?lang=en)**.

- **Harmonic Security:** Harmonic Security uses the Anthropic Compliance API to govern Claude use across every surface (Desktop, Web, Mobile, Claude Code, Cowork), classifying every interaction with proprietary detection models to surface sensitive-data exposure, prompt injection, and AI usage and adoption insights broken down by team, department, and location. To set up this integration, see the **[Harmonic Security setup guide](https://docs.harmonicsecurity.app/integration-guides/configure-anthropic-compliance-api-connector)**.

- **IBM Guardium:** IBM Guardium helps organizations monitor data access and usage by agentic AI systems and help ensure autonomous activities remain within approved security boundaries. With ready-to-use templates, customizable policies, continuous audit workflows, and compliance reporting aligned to frameworks such as EU AI Act, AIDA, PCI, SOX, HIPAA, GDPR, and CPRA, Guardium helps security and compliance teams confidently demonstrate oversight of AI-driven activity. Learn more about **[IBM Guardium](https://www.ibm.com/products/guardium)**.

- **Island:** Island's Claude Compliance API integration gives security and compliance teams visibility into every Claude session—user-driven or autonomous—covering conversation topics, tool/model/skill usage, and continuously enriched detection of sensitive-data exposure and policy violations for posture assessment and anomaly detection. Learn more about **[Island's integration with the Claude Compliance API](https://www.island.io/blog/island-integrates-with-the-claude-compliance-api)**.

- **KnowBe4:** KnowBe4 Agent Risk Manager uses the Compliance API to inventory AI agents and Claude usage, map activity back to its human, system, or agent source, and detect risks such as prompt injection, sensitive information disclosure, excessive agency, and unbounded consumption—with no on-device software to deploy. Note on availability: General availability is planned for November 2026. To set up this integration, see the **[KnowBe4 setup guide](https://support.knowbe4.com/hc/en-us/articles/55662933177875-Claude-Compliance-Integration-Guide-for-Agent-Risk-Manager)**.

- **Lasso Security:** Lasso integrates with the Compliance API to give security teams centralized visibility into Claude activity—who is using Claude, what they are doing, and which MCP servers and skills they invoke—classifying each interaction against customer-defined policies with a full audit trail for compliance. To set up this integration, see the **[Lasso Security setup guide](https://www.lasso.security/use-cases/claude-enterprise).**

- **Linx Security:** Linx integrates with the Claude Compliance API to govern access across human, non-human, and agent identities in Claude—delivering visibility, risk detection, access reviews, and least-privilege enforcement. To set up this integration, see the **[Linx Security setup guide](https://docs.linxsecurity.io/connectors/connectors-library/anthropic/claude.ai)**.

- **Microsoft Purview:** Purview's integration with the Claude Compliance API extends Purview's enterprise security and compliance coverage by surfacing insights from Claude activity feed and chat conversations, enabling scenarios within Purview Data Security Posture Management and Audit. It provides centralized visibility of activities across Claude Enterprise and Claude Platform, allowing organizations to understand how data is accessed and used across their Claude systems. Surfacing this signal within Purview helps close a critical governance gap as enterprises rapidly adopt AI across multiple platforms. The same comprehensive visibility Purview provides for Copilot and the broader Microsoft AI ecosystem, is now available for Claude Enterprise users. To set up this integration, see the **[Microsoft Purview setup guide](https://learn.microsoft.com/en-us/purview/ai-microsoft-purview)**.

- **Mimecast:** Mimecast's Governance, Compliance & Insights (GCI) platform now integrates with the Claude Compliance API to bring Claude Enterprise conversations into the same unified governance and compliance experience organizations already use for email and collaboration data, with no new interfaces or workflows required. To set up this integration, see the **[Mimecast setup guide](https://www.mimecast.com/use-cases/ai-governance/)**.

- **Mind Security Inc:** MIND integrates with the Compliance API to discover Claude usage across the organization, correlate it with user identities, and classify the data shared in chats and files, so security teams can detect data risk in Claude alongside SaaS, endpoint, and GenAI activity. Learn more about **[Mind Security Inc's integration with the Claude Compliance API](https://mind.io/blog/claude-compliance-governance)**.

- **Mint Security:** Mint provides contextual runtime security for AI agents, using the Claude Compliance API to apply organization-specific visibility, context, and policy controls to how teams use Claude. To set up this integration, see the **[Mint Security setup guide](https://docs.mint.security/integrations/claude/claude)**.

- **Netskope:** Netskope's integration with the Claude Compliance API lets organizations connect Claude Enterprise directly into the enhanced AI security features of the Netskope One platform, delivering full asset, identity, and activity visibility, robust policy enforcement, advanced data security, and comprehensive security posture management, all within the workflows security and compliance teams already rely on. **Note:** Available in private preview. To set up this integration, see the **[Netskope setup guide](https://docs.netskope.com/en/onboard-claude-for-ai-discovery/)**.

- **Nightfall AI:** Nightfall integrates with the Claude Compliance API to detect sensitive data (PII, PHI, PCI, secrets, source code) in Claude Enterprise chats and file uploads. Monitor-only, with admin alerts, end-user notifications, and an audit trail in the same workflow as other SaaS connectors. To set up this integration, see the **[Nightfall AI setup guide](https://help.nightfall.ai/nightfall-for-anthropic-claude/nightfall-for-claude-enterprise-compliance-api)**.

- **Noma Security:** Noma's AI Detection and Response (AI-DR) integration with the Compliance API gives security teams continuous visibility into Claude Enterprise usage, detecting sensitive-data exposure, risky prompts, and policy violations with full behavioral context—so teams can say yes to Claude with governance in place. Learn more about **[Noma Security's integration with the Claude Compliance API](https://noma.security/integrations/claude-enterprise/)**.

- **Obsidian Security:** Obsidian extracts posture and activity from the Compliance API and 200+ other applications. That data is normalized and used by enterprise customers for continuous governance, drift detection, and identifying and investigating potential threats. Learn more about **[Obsidian Security's integration with the Claude Compliance API](https://www.obsidiansecurity.com/integrations/claude)**.

- **Okta:** Okta's integration with the Claude Compliance API brings Claude usage within Okta Identity Security Posture Management, allowing security and compliance teams to contextualize Claude user activity with signals from other identity platforms, SaaS tools, and cloud providers and surface identity blind spots from one unified view. This enables organizations to continuously assess identity risk posture, detect misconfigurations and risks—such as overprivileged users, dormant accounts, and unused admin keys—remediate issues by severity, and securely deploy AI at scale. Learn more about **[Okta's integration with the Claude Compliance API](https://www.okta.com/newsroom/articles/okta-identity-security-posture-management-integrates-with-anthropics-new-compliance-api/)**.

- **Note on availability:** This offering will soon be available in beta to select customers using Okta Identity Security Posture Management alongside either Anthropic’s Claude Enterprise or Claude Platform.

- **Onyx Security:** Onyx is the secure AI control plane that gives enterprises observability, security, and governance over AI agents across SaaS, cloud, endpoint, and code. This integration extends Onyx's guardrails and audit trail to Claude deployments—letting security teams monitor usage, enforce policies, prevent data exfiltration, and meet compliance requirements without slowing Claude adoption. To set up this integration, see the **[Onyx Security setup guide](https://onyx.security/integrations/anthropic)**.

- **Opal Security:** Opal uses the Compliance API to show security and IAM teams how their organization uses Claude—including MCP server connections and API keys—and to tighten what Claude agents can reach by adjusting entitlements in connected systems, before over-broad access becomes an incident. To set up this integration, see the **[Opal Security setup guide](https://docs.opal.dev/docs/agent-inventory)**.

- **Opsin:** AI risk and agent governance for Claude Enterprise: Opsin's Compliance API integration surfaces data oversharing, risky user behavior, and agent sprawl within 24 hours, using a context graph that connects identity, data, and model for root-cause remediation. To set up this integration, see the **[Opsin setup guide](https://www.opsinsecurity.com/claude-integration)**.

- **Orca Security:** Orca Security extends its unified platform to Claude Enterprise, giving security teams complete visibility into Claude identities, access, AI workspaces, and the sensitive data within them—to surface risk, enforce least privilege, and track compliance. To set up this integration, see the **[Orca Security setup guide](https://claude-doc.orca.security/)**.

- **Origin:** Origin is endpoint observability for agentic AI: every AI agent on your fleet, what it did, and where your AI spend goes. The Compliance API adds Claude Enterprise usage from claude.ai and Claude Desktop, attributed to each user and folded into the same record as the agents Origin observes. To set up this integration, see the **[Origin setup guide](https://support.originhq.com/docs/claude-enterprise)**.

- **Palo Alto Networks:** The Claude Compliance API integration enables organizations to understand what data is being shared with Claude, detect sensitive content and policy violations, identify threats and anomalous behavior, and guide users toward safer AI usage. To set up this integration, see the **[Palo Alto Networks setup guide](https://www.paloaltonetworks.com/blog/cloud-security/claude-security-integration-ai-governance)**.

- **Pi Security:** Pi Security uses the Compliance API to understand how engineering teams build with Claude - the tasks they delegate, the workflows they follow, and where security-relevant decisions happen - so its agentic application security guidance reflects real development practice and catches risk earlier in the SDLC. Learn more about **[Pi Security’s integration with the Claude Compliance API](https://www.pi.security/blog/powering-every-builder-with-security-context-pi-integrates-with-anthropics-compliance-api)**.

- **Pluto Security:** Pluto provides real-time visibility and enforcement across the Anthropic ecosystem—Claude Code, Cowork, and Office Agents. It monitors agent activity, detects risks like prompt injection and sensitive-data exposure, identifies malicious ecosystem components, and enforces policies on agent actions, MCPs, connectors, and tool usage. Learn more about **[Pluto Security's integration with the Claude Compliance API](https://pluto.security/blog/claude-enterprise-meets-ai-security-platform/)**.

- **Proofpoint:** Proofpoint’s integration with the Claude Compliance API brings security and governance together across AI interactions. Sensitive data in prompts, responses, and files is protected with DLP, AI-aware classifiers, and Insider Threat signals, while activity is captured and retained for eDiscovery, supervision, and compliance purposes. The result is comprehensive visibility, control, and retention for organizations leveraging Claude, consistent with the controls protecting the rest of their tech stack. To set up this integration, see the **[Proofpoint setup guide](https://support.nuclei.ai/hc/en-us/articles/39717913412759-Compliance-Archiving-for-Anthropic-Claude-Enterprise)**.

- **Reco:** Reco monitors Claude Enterprise for AI security threats, posture risks, and identity anomalies. Using the Compliance API, it ingests activity logs and conversation data to detect MCP server abuse, permission escalations, and unauthorized access, surfacing violations mapped to MITRE ATT&CK, OWASP LLM Top 10, and more. Learn more about **[Reco's integration with the Claude Compliance API](https://www.reco.ai/blog/claude-security-governance)**.

- **RelativityOne:** RelativityOne enables legal, compliance, and security teams to collect Claude Enterprise data directly from the source via the Claude Compliance API. This includes conversation prompt and response data—such as chats, uploaded files, and projects. Collected data is automatically mapped, preserved, and processed into a reviewable format, including normalization into Relativity Short Message Format (RSMF). This ensures teams can quickly analyze conversational evidence with full context while maintaining the metadata and transparency required for defensibility. To set up this integration, see the **[RelativityOne setup guide](https://help.relativity.com/RelativityOne/Content/Collect/Data_sources/Claude.htm)**.

- **ReliaQuest:** The ReliaQuest GreyMatter platform now integrates with the Claude Compliance API, bringing Anthropic’s Claude Enterprise activity data into GreyMatter, giving security and IT teams visibility into activity logs to detect threats or unwanted behavior. To set up this integration, see the **[ReliaQuest setup guide](https://greymatter.myreliaquest.com/resources/articles/anthropic-claude-compliance)**.

- **Reva.ai:** Reva brings runtime authorization to Claude Code and Claude Enterprise agents, evaluating policy at the moment of action through pre-tool hooks and Inference Hooks, and checking each request against the agent's purpose and normal patterns to catch drift and misuse that permission checks alone miss. Learn more about **[Reva.ai's integration with the Claude Compliance API](https://codingagent.dev.reva.ai/register)**.

- **Rubrik:** Rubrik Agent Cloud integrates with the Claude Compliance API to help organizations control how Claude is used at work. Teams can see who is using Claude, review activity when needed, flag risky behavior, and use Rubrik SAGE to create natural-language policies that route alerts to their security tools. To set up this integration, see the **[Rubrik setup guide](https://www.rubrik.com/products/rubrik-agent-cloud)**.

- **Safeguard:** Safeguard integrates with the Claude Compliance API to monitor Claude usage as part of AI-native software supply chain security—surfacing vulnerabilities and risks with AI-driven remediation across the lifecycle. To set up this integration, see the **[Safeguard setup guide](https://safeguard.sh/mcp/claude)**.

- **SailPoint:** The SailPoint Claude Compliance API integration streamlines identity and access management by aggregating Organizational users, groups, and roles. To set up this integration, see the **[SailPoint setup guide](https://documentation.sailpoint.com/connectors/saas/claude_enterprise/help/)**.

- **Salt Security:** Salt Security's Claude Compliance API integration gives security teams a continuous, authoritative inventory of every MCP server connected to Claude Enterprise—tracking added, removed, and active servers through a single read-only scope that never touches prompts or conversation content. To set up this integration, see the **[Salt Security setup guide](https://salt.security/blog/introducing-the-salt-claude-connect-continuous-mcp-server-visibility-for-claude-enterprise)**.

- **Saviynt:** The Saviynt Claude Compliance API integration streamlines identity governance for Claude Enterprise by aggregating users, groups, and roles to enable centralized visibility, automated access certifications, and seamless lifecycle management. To set up this integration, see the **[Saviynt setup guide](https://exchange.saviynt.com/products/claude-enterprise)**.

- **SentinelOne:** Give security teams visibility and control to adopt Claude across the enterprise with SentinelOne's Anthropic Compliance API integration. Prompt Security scans every prompt and response against your policies, flagging violations in real time. Singularity AI SIEM correlates Claude activity across your security telemetry to accelerate investigation, detection, and response. Learn more about **[SentinelOne's integration with the Claude Compliance API](https://sentinelone.com/blog/sentinelone-and-claude-integrations-for-ai-visibility-governance-and-defense)**.

- **Sentra:** Discover sensitive data across projects, chats, prompts, and files, identify data exposure risks, and extend data security and compliance controls to your AI environments. To set up this integration, see the **[Sentra setup guide](https://sentra.io/guides/sentra-claude-enterprise-integration-guide)**.

- **Shield:** Shield uses the Compliance API to capture Claude Enterprise chats, files, projects, and artifacts into compliant long-term storage, surveilled with behavioral analytics and NLP-based risk detection—giving regulated financial institutions an examination-ready recordkeeping and eDiscovery layer for their Claude usage. To set up this integration, see the **[Shield setup guide](https://hs.shieldfc.com/claude-connector)**.

- **Silverfort:** Silverfort uses the Compliance API to map Claude identities and activity into its unified identity graph, helping security teams investigate access and surface risks such as dormant privileged users, incomplete offboarding, SSO bypass, public artifacts, exposed tunnel secrets, and ungoverned MCP servers. Learn more about **[Silverfort's integration with the Claude Compliance API](https://www.silverfort.com/blog/silverfort-integration-with-anthropic-compliance-api/)**.

- **Smarsh:** Smarsh Capture helps organizations monitor and retain Claude Enterprise interactions, so you can adopt and govern AI with confidence and support compliance workflows. By connecting directly to the Claude Compliance API, you gain structured access to Claude conversations, consistent complete records, and support for audit and regulatory response. This enables company-wide Claude Enterprise adoption and governance while staying ahead of evolving regulations. To set up this integration, see the **[Smarsh setup guide](https://central.smarsh.com/s/article/From-which-networks-does-cloudcapture-gather-data-from)**.

- **Snyk:** This new integration gives security and compliance teams a complete inventory of their Claude Enterprise environment including models, approved MCP servers, and tool-level permissions, in the platform they already use to govern the rest of the stack. To set up this integration, see the **[Snyk setup guide](https://docs.snyk.io/integrations/cloud-ai-platforms/anthropic-claude-enterprise)**.

- **Sola Security:** Sola connects to the Compliance API to bring Claude Enterprise activity, user access, and conversation data into Sola's AI-powered security platform, where security teams can query their Claude environment in plain language, correlate it with identity tools, and surface governance risks like overprivileged users and orphaned accounts. To set up this integration, see the **[Sola Security setup guide](https://docs.sola.security/integrations/data-sources/claude-enterprise)**.

- **Splunk, a Cisco Company:** Splunk ingests Claude Enterprise audit, usage, cost, and spend-limit data through the Compliance API and related Claude APIs, with CIM-normalized events, ready-made detections, and dashboards for security auditing, governance, and usage and spend analytics. To set up this integration, see the **[Splunk setup guide](https://lantern.splunk.com/Security_Use_Cases/Compliance/Monitoring_and_governing_enterprise_AI_platforms)**.

- **Strac:** Strac helps enterprises safely adopt Claude by using the Compliance API to detect sensitive-data exposure, monitor usage, and generate audit-ready security insights. To set up this integration, see the **[Strac setup guide](https://www.strac.io/integrations/claude-compliance-api)**.

- **Straiker:** Straiker provides real-time security for Claude Enterprise—detecting prompt injection, data exfiltration, and agentic misuse across Claude chat and Claude Code. Security teams get unified visibility, enforcement, and forensic investigation across all Claude surfaces in a single platform. Learn more about **[Straiker's integration with the Claude Compliance API](https://www.straiker.ai/claude-code)**.

- **Sumo Logic:** Sumo Logic’s integration with the Claude Compliance API brings Claude Enterprise activity logs and Claude platform activity logs into the Sumo Logic Intelligence Operations Platform, so teams can transform AI governance into a transparent, enterprise-ready operation that reduces risk through real-time monitoring and automated detection, investigation, and response capabilities within Sumo Logic. To set up this integration, see the **[Sumo Logic setup guide](https://www.sumologic.com/help/docs/integrations/saas-cloud/claude-compliance)**.

- **Surf AI:** Surf reads Claude usage from the Compliance API to detect unsanctioned MCP connections, tie each to an accountable owner, and drive remediation. Learn more about **[Surf AI's integration with the Claude Compliance API](https://www.surf.ai/technology-partners/anthropic)**.

- **Sysdig:** Sysdig detects suspicious Claude credential activity and correlates it with runtime and security events on the same machine, turning isolated API alerts into clear evidence of misuse and allowing security teams to respond to real threats with full context. To set up this integration, see the **[Sysdig setup guide](https://www.sysdig.com/integrations/anthropic)**.

- **Tenable:** The integration with the Claude Compliance API will leverage visibility into user interactions to detect malicious and suspicious activity. This capability allows organizations to safely adopt Claude Enterprise across the organization without losing visibility into how users engage with it. To set up this integration, see the **[Tenable setup guide](https://docs.tenable.com/early-access/ai-exposure/Content/settings/integrations/claude.htm)**.

- **Theta Lake:** As enterprises deploy Claude across their workforce to unlock productivity and ROI at scale, AI interactions between AI and humans and AI agents are causing entirely new user behaviors and generating a new class of communications. Security, compliance, and legal teams need complete visibility into how Claude is being used. This integration empowers organizations to use Theta Lake’s Investigation, Analytics, and Regulatory Compliance capabilities, each of which received the tops scores in the Gartner® Critical Capabilities. To set up this integration, see the **[Theta Lake setup guide](https://docs.thetalake.com/docs/en-US/integrations/anthropic.html?Highlight=anthropic%20)**.

- **Token Security:** Token Security integrates with Anthropic's Compliance API to discover, govern, and secure the non-human identities powering Claude usage, surfacing stale keys, ownership gaps, and agent activity within a unified NHI security platform. Learn more about **[Token Security's integration with the Claude Compliance API](https://www.token.security/blog/token-security-brings-anthropic-claude-compliance-api-into-its-identity-control-plane)**.

- **Torch Security:** Torch brings Claude Enterprise under identity governance: it reads the Claude org directory and activity feed via the Compliance API, correlates every account to a real identity, and runs access reviews that flag out-of-band (non-SCIM) group grants, orphaned accounts, and dormant access—read-only, never touching conversation content. To set up this integration, see the **[Torch Security setup guide](https://www.torch.security/integrations/claude/)**.

- **Trellix:** The Trellix Claude Compliance API integration checks all chat content, artifacts, and responses against customer-defined privacy policies using their Data Security Engine and creates detection and audit events in Trellix Helix. This includes customer-specific patterns and policies that are defined for their endpoint, server, and collaboration software and applies it to Claude as well. To set up this integration, see the **[Trellix setup guide](https://www.trellix.com/platform/data-security/)**.

- **TrendAI:** TrendAI's integration with the Claude Compliance API automatically collects and monitors Claude chat activity across your organization, scans for prompt injection, harmful content, and sensitive-data leakage, and correlates findings with your broader security signals through SIEM and XDR for investigation and audit-ready compliance and governance. To set up this integration, see the **[TrendAI setup guide](https://www.trendmicro.com/en_us/research/26/f/governing-claude-enterprise.html)**.

- **Twine Security:** Twine's AI digital employee, Alex, uses the Compliance API to bring identity governance to Claude Enterprise - mapping who has access, which roles, groups, and connectors they hold, and flagging risks such as accounts provisioned outside the identity provider, with remediation routed for human approval. To set up this integration, see the **[Twine Security setup guide](https://www.twinesecurity.com/resource/twine-anthropic-governing-claude-enterprise)**.

- **Valence Security:** Valence integrates with the Compliance API to give security teams visibility into how Claude Enterprise and Claude Platform are used, including users, agents, MCP servers, connectors, and tools. Valence correlates this activity with identities and configurations across the rest of the environment, helping teams detect risky behavior and remediate exposure. To set up this integration, see the **[Valence Security setup guide](https://www.valencesecurity.com/resources/blogs/securing-agentic-identities-in-claude-the-valence-integration-with-the-compliance-api)**.

- **Vanta:** Vanta uses the Compliance API to build an AI inventory from Claude Enterprise chats and Claude Code and Cowork sessions in its AI Governance product, so compliance teams can monitor Claude usage and produce audit-ready reports against their policies and controls. Note on availability: This integration is available in beta to select Vanta AI Governance customers using Claude Enterprise, with general availability planned for January 2027. To set up this integration, see the **[Vanta setup guide](https://www.vanta.com/integrations/claudes-compliance-api)**.

- **Varonis:** The Compliance API integration deepens Varonis' support for Claude, enabling security and governance teams to monitor usage, investigate misuse across full sessions, and assess AI-related risk with data context. To set up this integration, see the **[Varonis setup guide](https://info.varonis.com/hubfs/documentation/varonis-atlas-anthropic-compliance-api-documentation.pdf)**.

- **Vega:** Vega ingests your organization's Compliance API activity feed, normalizes it to a common security schema, and lets your team search, detect, alert, and investigate Claude audit events alongside the rest of their security telemetry. Learn more about **[Vega's integration with the Claude Compliance API](https://vega.io/blog/vega-anthropic-claude-compliance-api)**.

- **Vero Security:** Vero Security integrates with the Compliance API to provide security insights for enterprises, enabling full context for governance and policy enforcement so teams can monitor, manage, and safely scale Claude adoption across the organization. Learn more about **[Vero Security's integration with the Claude Compliance API](https://www.vero.security/blog/vero-antrpc-integration)**.

- **Willow:** Willow gives every AI agent an identity and permissioned access to the right tools and skills, with a full audit trail. Through its integration with the Compliance API, Willow extends that governance to Claude usage so security teams can see and control agent activity across the organization. To set up this integration, see the **[Willow setup guide](https://docs.withwillow.ai/docs/admin/settings/claude-compliance-sync)**.

- **WithWings:** WithWings uses the Compliance API to discover the AI agents and sessions across a Claude Enterprise environment, map their identities, permissions, and integrations, and assess whether each agent's actions stay aligned with its original purpose—detecting drift between intent and behavior. To set up this integration, see the **[WithWings setup guide](https://withwings.ai/integrations/claude)**.

- **Wiz:** The Wiz connector for the Claude Compliance API allows organizations to discover AI projects, models, and users while identifying security risks like elevated roles or sensitive data within knowledge bases. It maps identity relationships and tracks model usage across the enterprise by integrating via the Claude Compliance API. Learn more about **[Wiz's integration with the Claude Compliance API](https://www.wiz.io/blog/claude-wiz-integration)**.

- **Zenity:** Zenity automatically discovers and inventories all Claude agents, MCP servers, connected resources, and non-human identities—mapping their relationships and security posture from the moment a session starts. To set up this integration, see the **[Zenity setup guide](https://zenity.io/use-cases/platform/claude-enterprise)**.

- **Zscaler:** By integrating with the Claude Compliance API, Zscaler is now able to provide deep visibility and granular control over every Claude prompt created by an enterprise user. Zscaler Data Security and DLP workflows help administrators strengthen their data protection programs through detailed analysis of organizational data and activity logs extracted from Claude. This solution enables faster enforcement actions to prevent data loss across multiple exfiltration channels. To set up this integration, see the **[Zscaler setup guide](https://www.zscaler.com/products-and-solutions/data-security)**.

---

## Get started with custom connectors using remote MCP | Claude Help Center

Source: https://support.claude.com/en/articles/11175166-getting-started-with-custom-connectors-using-remote-mcp
Path: 14-Connectors/getting-started-with-custom-integrations-using-remote-mcp.md

# Get started with custom connectors using remote MCP

August 11, 2026

Custom connectors using remote MCP are available on Claude, Cowork, and Claude Desktop for users on Free, Pro, Max, Team, and Enterprise plans. Free users are limited to one custom connector.

## What are custom connectors?

Custom connectors let you connect Claude directly to the tools and data sources that matter most to your workflows. This enables Claude to operate within your favorite software and draw insights from the complete context of your external tools.

You can:

- Connect Claude to existing remote MCP servers.

- Build your own remote MCP servers to connect with any tool.

**Security and privacy with custom connectors**

Custom connectors allow you to connect Claude to services that haven't been verified by Anthropic. Once connected, Claude can access those services and take action in them. For more guidance, review the **[Security and privacy considerations](#h_b79c05dfcd)** section below.

## What are remote MCP servers?

The Model Context Protocol (MCP) is an open standard, created by Anthropic, for AI applications to connect to tools and data.

Previously, **[MCP servers only ran locally](../16-Mobile-Desktop/getting-started-with-local-mcp-servers-on-claude-desktop.md)** (i.e. on a user's laptop). Now, developers can build and host remote MCP servers that communicate with AI apps over the internet.

Remote MCP servers give models access to internet-hosted tools and data, transforming Claude into an informed teammate that can independently handle complex, multi-step projects tailored to your needs.

------------------------------------------------------------------------

## Network requirements

When you add a custom connector, Claude connects to your remote MCP server from Anthropic's cloud infrastructure, rather than from your local device. This is true across every Claude client, including claude.ai, Claude Desktop, Cowork, and the mobile apps.

This means your MCP server must be reachable over the public internet from Anthropic's IP ranges. Servers hosted on a private corporate network, behind a VPN, or blocked by a firewall won't connect, even if you can reach them from your own machine.

### If your server is on a private network

You’ll need to allowlist Anthropic's IP addresses in your firewall so inbound connections from Claude can reach your server. See **[Anthropic IP addresses](../04-API-Reference/Endpoints/ip-addresses.md)** for the current ranges.

### Why this applies to Cowork and Claude Desktop

Even though Cowork and Claude Desktop run on your computer, remote connectors are configured and brokered through your Claude account. The connection to your MCP server originates from Anthropic's servers, not from your machine's network interface. Local MCP servers configured in Claude Desktop via `claude_desktop_config.json` are a separate mechanism and do use your local network, but those aren't available in Cowork or claude.ai.

------------------------------------------------------------------------

## Add a custom connector

**Note:** While anyone can build and host connectors using remote MCP, only Owners can add them to Team and Enterprise plans. Once a connector has been added to a Team or Enterprise organization, users individually connect to and enable that connector. This ensures that Claude can only access tools and data that the individual user has access to.

### For Team and Enterprise plans

**Preliminary steps for owners:**

Before members of Team and Enterprise plans can configure custom connectors, an Owner or Primary Owner needs to follow these initial steps to add a custom connector to your organization:

1. Navigate to **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

2. Click the "Add" button.

3. Hover over “Custom,” then select “Web.”

4. Add your connector's remote MCP server URL.

5. Optionally, click “Advanced settings” to specify an OAuth Client ID and OAuth Client Secret for your server.

6. Finish configuring your connector by clicking "Add."

**Steps for members after connector is configured:**

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Find the custom connector your Owner added in the list. It usually has a "Custom" label.

3. Click "Connect" to authenticate and start using the connector with Claude.

**Note:** If your custom connector's URL is on a domain that matches a listing in the Connectors Directory (for example, a Workato workspace URL), it appears with that service's name and branding instead of a "Custom" label. It's still your own connector. It connects to the exact URL your owner entered and uses your server's tools, so you don't need to remove it or add it again.

### For Pro and Max plans

If you are using an individual Pro or Max plan, follow these steps to add a custom connector:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Click "+" then “Add custom connector.”

3. Add your connector's remote MCP server URL.

4. Optionally, click “Advanced settings” to specify an OAuth Client ID and OAuth Client Secret for your server.

5. Finish configuring your connector by clicking "Add."

### Enabling connectors after configuration

You can enable connectors for individual conversations via the “+” button on the lower left of your chat interface, then "Connectors." You'll see your configured connectors with toggles allowing you to enable/disable them per conversation.

------------------------------------------------------------------------

## Remove custom connectors

You can remove a custom connector by following these steps:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

1. Team and Enterprise Owners can do this on their organization's behalf in **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

2. Locate the "Connectors" section.

3. Click "Remove" or select the three dots next to the connector you'd like to remove.

4. Follow the prompts to remove.

If you're hoping to edit a custom connector, you'll need to remove it first, then re-add it using the updated details.

------------------------------------------------------------------------

## Build custom connectors

To learn about building connectors to use with Claude, see **[Building custom connectors](https://claude.com/docs/connectors/building)** in Claude Docs.

------------------------------------------------------------------------

## Security and privacy considerations

Custom connectors allow you to connect Claude to arbitrary services that have not been verified by Anthropic. When you connect Claude to external services, you're granting it the ability to access and potentially modify data within those services based on your permissions. It’s important to make sure you’re only connecting to remote MCP servers that you trust and that you’re aware of Claude’s interactions with web connectors.

### Security and permissions

When you add a custom connector to Claude, you'll typically go through an OAuth authentication process to securely sign in to the application and grant specific permissions. This allows Claude to interact with the application on your behalf, without Claude ever seeing your actual password. You can revoke these permissions at any time by disconnecting the connector in Claude's settings or the third-party service's security settings.

Remote MCP servers act as intermediaries between Claude and external applications. You should:

- **Only connect to trusted servers:** Only connect Claude to servers built and hosted by organizations and applications you trust.

- **Review requested permissions carefully:** During auth, review what permissions the MCP server is requesting to the application. Limit these scopes when possible and deny access if requested permissions seem unnecessary.

- **Be aware of prompt injections:** Malicious MCP servers may include hidden instructions that try to make Claude perform unintended actions. Claude has built-in protections that attempt to block these attacks, but it's important to pay attention to tool inputs & outputs and connect only to trusted servers.

- **Monitor changes in tool behavior:** Server developers may update tool behavior unexpectedly, leading to unintended or malicious behavior.

### Reporting malicious MCP servers

If you become aware of a malicious MCP server, please report it to our **[vulnerability disclosure program](https://hackerone.com/anthropic-vdp/)**, and choose `https://github.com/modelcontextprotocol` as the Asset.

### Taking actions with tools

Remote MCP servers give Claude tools it can invoke during your conversation. The developer of an MCP server can define what these tools do, including:

- Reading data from connected applications.

- Creating, modifying, or deleting data in connected applications.

- Taking actions on behalf of the user.

Claude can only access resources that you've given the server permission to access, but you should:

- Be aware of any actions Claude is taking and that they have no destructive or unintended effects.

- Review Claude's tool approval requests carefully and only click "Allow always" when using a server and tool that you trust to run unsupervised.

- Using the "Search and tools" menu, disable any tools that aren't relevant to the current conversation or that you don't want Claude to be able to invoke.

### Interactive connectors

Some connectors can display interactive interfaces directly within your Claude conversations. Instead of only returning text-based responses, these connectors can open live, interactive apps—like dashboards, task boards, or design tools—right in the chat.

Interactive connectors appear in two ways:

- **Inline cards:** Compact components embedded in the conversation, showing summaries, confirmations, or quick actions.

- **Fullscreen view:** Immersive interfaces for complex interactions like data visualizations or document editing. The conversation composer remains available so you can continue chatting with Claude.

You can interact with these connectors directly—filtering data, checking off tasks, adjusting settings—without leaving the conversation. Any actions you take within the interface use the same permissions you granted when connecting the tool.

**Admin controls:** Team and Enterprise plan owners can disable specific tool calls that render interactive connectors within **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

### Using Claude with Research

**Note: [Advanced research](https://claude.com/blog/integrations)** is not currently able to invoke tools from local MCP servers.

Research allows Claude to deeply investigate queries by searching through hundreds of internal and external sources. During the research process, Claude can invoke tools from your connectors automatically without further approval.

When using research with custom connectors:

- Disable any tools that can take write actions in external applications.

- Review Claude’s approval request carefully and be aware of which tools you’re granting Claude permission to invoke.

- Be mindful of the impact of Claude sending a large number of requests to your connectors.

See **[Use research on Claude](../15-Claude-AI-Features/using-research-on-claude-ai.md)** for more information about this feature.

---

## Google Sheets add-on | Claude Help Center

Source: https://support.claude.com/en/articles/13162029-google-sheets-add-on
Path: 14-Connectors/google-sheets-add-on.md

# Google Sheets add-on

The [Claude for Sheets extension](https://workspace.google.com/marketplace/app/claude%5Ffor%5Fsheets/909417792257) integrates Claude into Google Sheets, allowing you to execute interactions with Claude directly in cells.

## Why use Claude for Sheets?

Claude for Sheets enables prompt engineering at scale by enabling you to test prompts across evaluation suites in parallel. Additionally, it excels at office tasks like survey analysis and online data processing.

Visit our [prompt engineering example sheet](https://docs.google.com/spreadsheets/d/1sUrBWO0u1-ZuQ8m5gt3-1N5PLR6r__UsRsB7WeySDQA/copy) to see this in action.

## Get started with Claude for Sheets

### Install Claude for Sheets

Easily enable Claude for Sheets using the following steps:

1. **Get your Claude API key:** If you don't yet have an API key, you can make API keys in the Claude Console.

2. **Install the Claude for Sheets extension:** Find the [Claude for Sheets extension](https://workspace.google.com/marketplace/app/claude%5Ffor%5Fsheets/909417792257) in the add-on marketplace, then click the blue \`Install\` button and accept the permissions.

1. Permissions: The Claude for Sheets extension will ask for a variety of permissions needed to function properly. Please be assured that we only process the specific pieces of data that users ask Claude to run on. This data is never used to train our generative models.

2. Extension permissions include:

1. **View and manage spreadsheets that this application has been installed in:** Needed to run prompts and return results.

2. **Connect to an external service:** Needed in order to make calls to Claude API endpoints.

3. **Allow this application to run when you are not present:** Needed to run cell recalculations without user intervention.

4. **Display and run third-party web content in prompts and sidebars inside Google applications:** Needed to display the sidebar and post-install prompt.

3. **Connect your API key:** Enter your API key at `Extensions` \> `Claude for Sheets™` \> `Open sidebar` \> `☰` \> `Settings` \> `API provider`. You may need to wait or refresh for the Claude for Sheets menu to appear.

**Important:** You will have to re-enter your API key every time you make a new Google Sheet.

### Enter your first prompt

There are two main functions you can use to call Claude using Claude for Sheets. For now, let's use `CLAUDE()`.

**Simple prompt**

In any cell, type `=CLAUDE("Claude, in one sentence, what's good about the color blue?")`.

Claude should respond with an answer. You will know the prompt is processing because the cell will say `Loading...`.

**Adding parameters**

Parameter arguments come after the initial prompt, like `=CLAUDE(prompt, model, params...)`.

**Note:** `model` is always second in the list.

Now type in any cell `=CLAUDE("Hi, Claude!", "claude-haiku-4-5-20251001", "max_tokens", 3)`.

Any API parameter can be set this way. You can even pass in an API key to be used just for this specific cell, like this: `"api_key", "sk-ant-api03-j1W..."`.

## Advanced use

`CLAUDEMESSAGES` is a function that allows you to specifically use the [Messages API](https://support.claude.com/en/04-API-Reference/Other/api-messages-2dd213ca95.md). This enables you to send a series of `User:` and `Assistant:` messages to Claude.

This is particularly useful if you want to simulate a conversation or [prefill Claude's response](../10-Prompting-Guides/build-with-claude-prompt-engineering-prefill-claudes-response.md).

Try writing this in a cell:

=CLAUDEMESSAGES("User: In one sentence, what is good about the color blue?
Assistant: The color blue is great because")

**Newlines**

Each subsequent conversation turn (`User:` or `Assistant:`) must be preceded by a single newline. To enter newlines in a cell, use the following key combinations:

- **Mac:** Cmd + Enter

- **Windows:** Alt + Enter

**Example multiturn CLAUDEMESSAGES() call with system prompt**

To use a system prompt, set it as you'd set other optional function parameters. (You must first set a model name.)

=CLAUDEMESSAGES("User: What's your favorite flower? Answer in <answer> tags.
Assistant: <answer>", "claude-haiku-4-5-20251001", "system", "You are a cow who loves to moo in response to any and all user queries.")

## Optional function parameters

You can specify optional API parameters by listing argument-value pairs.

You can set multiple parameters. Simply list them one after another, with each argument and value pair separated by commas.

**Note:** The first two parameters must always be the prompt and the model. You cannot set an optional parameter without also setting the model.

The argument-value parameters you might care about most are:

[TABLE]

### Example: Setting parameters

Ex. Set `system` prompt, `max_tokens`, and `temperature`:

=CLAUDE("Hi, Claude!", "claude-haiku-4-5-20251001", "system", "Repeat exactly what the user says.", "max_tokens", 100, "temperature", 0.1)

Ex. Set \`temperature\`, \`max_tokens\`, and \`stop_sequences\`:

=CLAUDE("In one sentence, what is good about the color blue? Output your answer in <answer> tags.","claude-opus-4-5-20251101","temperature", 0.2,"max_tokens", 50,"stop_sequences", "\[""</answer>""\]")

Ex. Set `api_key`:

=CLAUDE("Hi, Claude!", "claude-haiku-4-5-20251001","api_key", "sk-ant-api03-j1W...")

## Claude for Sheets usage examples

### Prompt engineering interactive tutorial

Our in-depth [prompt engineering interactive tutorial](https://docs.google.com/spreadsheets/d/19jzLgRruG9kjUQNKtCg1ZjdD6l6weA6qRXG5zLIAhC8/edit?usp=sharing) utilizes Claude for Sheets.

Check it out to learn or brush up on prompt engineering techniques.

**Note:** Just as with any instance of Claude for Sheets, you will need an API key to interact with the tutorial.

### Prompt engineering workflow

Our [Claude for Sheets prompting examples workbench](https://docs.google.com/spreadsheets/d/1sUrBWO0u1-ZuQ8m5gt3-1N5PLR6r%5F%5FUsRsB7WeySDQA/copy) is a Claude-powered spreadsheet that houses example prompts and prompt engineering structures.

### Claude for Sheets workbook template

Make a copy of our [Claude for Sheets workbook template](https://docs.google.com/spreadsheets/d/1UwFS-ZQWvRqa6GkbL4sy0ITHK2AhXKe-jpMLzS0kTgk/copy) to get started with your own Claude for Sheets work!

## Troubleshooting

### NAME? Error: Unknown function: 'claude'

1. Ensure that you have enabled the extension for use in the current sheet

1. Go to *Extensions \> Add-ons \> Manage add-ons*

2. Click on the triple dot menu at the top right corner of the Claude for Sheets extension and make sure "Use in this document" is checked

2. Refresh the page

### \#ERROR!, ⚠ DEFERRED ⚠ or ⚠ THROTTLED ⚠

You can manually recalculate `#ERROR!`, `⚠ DEFERRED ⚠`, or `⚠ THROTTLED ⚠` cells by selecting from the recalculate options within the Claude for Sheets extension menu.

### Can't enter API key

1. Wait 20 seconds, then check again

2. Refresh the page and wait 20 seconds again

3. Uninstall and reinstall the extension

## Further information

For more information regarding this extension, see the [Claude for Sheets Google Workspace Marketplace](https://workspace.google.com/marketplace/app/claude%5Ffor%5Fsheets/909417792257) overview page.

---

## Getting started with connectors · Claude Academy

Source: https://support.claude.com/en/articles/13123742-intro-to-connectors
Path: 14-Connectors/intro-to-connectors.md

# Getting started with connectors

Learn how to supercharge Claude by connecting the tools you already use. This tutorial shows you how to set up connectors that give Claude access to your files, apps, and workflows.

4 minClaude.ai

---

## MCP connectors | Claude Help Center

Source: https://support.claude.com/en/articles/14503689-mcp-connectors
Path: 14-Connectors/mcp-connectors.md

# MCP connectors

April 10, 2026

MCP connectors let Claude connect to your organization’s tools, data sources, and services. Claude can search your documents, read your email, or call external APIs on your behalf, all without leaving the chat.

For general questions about connectors in Claude, see **[Use connectors to extend Claude's capabilities](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**.

## How MCP connectors differ in Claude for Government

**Claude for Government runs the first FedRAMP High authorized MCP implementation.** The MCP framework, the infrastructure that registers, authenticates, and executes Anthropic-provided connectors, operates entirely within the Claude for Government authorized boundary. Because the authorization covers MCP as a feature, new Anthropic-provided and customer-provided connectors can be added without additional FedRAMP audits of Claude for Government itself, as long as the connectors meet your agency's data-handling requirements.

**The connector catalog is curated.** Only connectors approved for the government environment appear in the Admin Settings directory, so some commercial Claude connectors are not available.

**Important:** Some connectors call external APIs that transmit data outside the FedRAMP boundary. Each connector's catalog description states what data flows where. Your organization is responsible for evaluating whether that data flow is appropriate for your workloads, data classification levels, and applicable regulatory requirements.

## Browse available connectors

[TABLE]

Organizations can also register their own MCP servers for internal systems, custom tools, or approved third-party services. See **[Custom Connectors](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)**.

## Enable a connector for your organization

Connectors are enabled org-wide from Admin Settings. Once enabled, individual users in your organization can connect their own accounts.

**Note**: You must be an Owner or Primary Owner to enable connectors. Members can connect their accounts to connectors that are already enabled but cannot add new ones to the catalog.

1. Navigate to **claude.fedstart.com/admin-settings/connectors** (or use your organization’s custom Claude for Government domain).

2. Click "Browse connectors" to view the catalog.

3. Select a connector and review its description, paying particular attention to what data leaves the boundary, if any.

4. Click "Add to your organization."

5. Some connectors require an organization-level authentication step (for example, the Microsoft 365 connector requires tenant-admin consent in Microsoft Entra). Follow the on-screen instructions.

## Connect your account to a connector

After your org admin enables a connector, it appears in your personal settings.

1. Navigate to **claude.fedstart.com/settings/connectors**

2. Click "Connect" next to the connector.

3. Complete the authentication flow—typically a one-time OAuth consent screen.

4. The connector is now active in your chats. Claude will use it automatically when relevant, or you can reference it directly ("search my SharePoint for…").

------------------------------------------------------------------------

## Security and privacy

### How authentication works

Connectors use delegated, per-user OAuth wherever possible. When you connect a tool, Claude inherits your permissions in that tool and can only see and do what you can already see and do. There are no service accounts with elevated access.

### Where your credentials are stored

OAuth tokens are encrypted at rest and stored entirely within the Claude for Government FedRAMP High boundary. Tokens are scoped to the individual user who authenticated and are never shared between users. Anthropic does not receive standing access to your connected tenants.

### What stays inside the boundary

The MCPservice, token storage, and all connector-execution audit logging stay inside the FedRAMP High authorized environment. Each tool invocation follows the path:

User → Claude (in boundary) → MCP service(in boundary) → connected service

Whether the **connected service** sits inside or outside the boundary depends on the connector. The catalog description for each connector states this explicitly. For example, the Microsoft 365 connector calls Microsoft Graph within your tenant; the Web Search connector calls a third-party search API outside the boundary under a zero-data-retention agreement.

**Important:** Adding a connector does not change Claude for Government's FedRAMP authorization, but your agency's own ATO process may require you to evaluate the specific data-handling characteristics of each connector before enabling it.

------------------------------------------------------------------------

## Frequently asked questions

### Does enabling a connector give Anthropic access to our data?

No. Connectors use per-user delegated OAuth. Data flows between the in-boundary MCP proxy and the connected service using the individual user's credentials. Anthropic does not receive standing access to your tenant.

### If we add a new connector, do we need to update our ATO?

Adding a connector does not change Claude for Government's FedRAMP authorization—MCP was authorized as a feature. Whether your agency's own ATO requires an update depends on the data the connector handles and your internal authorization process.

### Can we restrict which users in our org can use a connector?

Connectors are enabled at the organization level. Once enabled, any user in the org can connect their individual account. Per-user or per-group connector gating is not currently available.

### Can Claude take write actions—send emails, create files—through connectors?

It depends on the connector: admins should review all connector permissions before adding them. Custom connectors can expose write tools if your MCP server implements them; see the security guidance in Custom Connectors before enabling write scopes.

---

## MCP: Individual connectors | Claude Help Center

Source: https://support.claude.com/en/articles/14503703-mcp-individual-connectors
Path: 14-Connectors/mcp-individual-connectors.md

# MCP: Individual connectors

April 9, 2026

Your organization can register its own MCP servers in Claude for Government, letting Claude connect to internal systems, custom tools, or third-party services you've approved for your environment.

**Custom connectors work the same way in Claude for Government as in Claude Enterprise.** The prerequisites, the registration flow, and the behavior once enabled are identical. For full setup instructions, see **[Use connectors to extend Claude's capabilities](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**. This page covers only what's different.

For general guidance on building and deploying MCP servers, see **[modelcontextprotocol.io](https://modelcontextprotocol.io/)** and the **[commercial connector guide](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**.

## How custom connectors differ for Claude for Government

**Adding a connector does not trigger a new FedRAMP review**

MCP was authorized as a **feature** in Claude for Government's FedRAMP High package. The infrastructure that registers, authenticates, and executes your connector—including encrypted token storage, per-user OAuth, and audit logging—is already covered. You can add new custom connectors without re-engaging Anthropic's FedRAMP audit process.

**Important:** This applies to Claude for Government's authorization only. Your agency's own ATO process may still require you to evaluate the MCP server and any backing services it reaches before enabling them. Anthropic does not review, authorize, or assume responsibility for customer-registered MCP servers or the external systems they call.

## Register custom connectors

Navigate to **claude.fedstart.com/admin-settings/connectors** as an **Owner** or **Primary Owner**. The rest of the flow matches the **[commercial guide](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**.

Once added, the connector appears in your users' settings exactly as Anthropic-provided connectors do.

## Know where the FedRAMP boundary sits

When a user invokes a tool from your custom connector:

User → Claude → MCP proxy → Your MCP server → Your backing service

└──── inside FedRAMP High ────┘ └─your responsibility─┘

Claude, the MCP proxy, and all OAuth token storage stay inside the FedRAMP High authorized environment. Whether your MCP server and its backing service sit inside or outside that boundary is under your control and yours to evaluate against the data classifications your users will handle.

**Prefer FedRAMP-authorized backing services.** If your connector talks to a SaaS product, check whether that product has a government-cloud offering—Atlassian Government Cloud, Salesforce Government Cloud, ServiceNow GCC—and point the connector there rather than at the commercial endpoint.

---

## Microsoft 365 connector security guide | Claude Help Center

Source: https://support.claude.com/en/articles/12684923-microsoft-365-connector-security-guide
Path: 14-Connectors/microsoft-365-connector-security-guide.md

# Microsoft 365 connector security guide

The Microsoft 365 connector is an **Anthropic-hosted integration** that enables Claude to securely access Microsoft 365 services (Outlook, SharePoint, OneDrive, Teams) through user-delegated permissions. Anthropic has completed Microsoft's publisher verification process, associating our verified Microsoft Partner Network account with this application to confirm our organizational identity.

The Microsoft 365 connector is available on all Claude plans: Free, Pro, Max, Team, and Enterprise.

The connector operates as a **secure proxy**, and your Microsoft 365 documents, emails, and files remain in your tenant. The connector only retrieves data on-demand during active queries and doesn’t cache file content. Credentials are encrypted and managed by Anthropic's backend infrastructure. The MCP server itself doesn’t store or manage these credentials. Microsoft's Azure SDK handles the On-Behalf-Of token exchange and caching on a per-user basis for accessing the Graph API.

## Access restriction

### Access can be fully restricted

The connector provides **multiple layers of access control** to address your security requirements. For detailed information on administration of the Microsoft 365 connector, see **[Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-)**.

**1. Microsoft Entra tenant requirement**

All people using the connector—regardless of Claude plan—must authenticate with a Microsoft 365 account tied to a Microsoft Entra tenant. Personal Microsoft accounts (@outlook.com, @hotmail.com) can't be used. A Microsoft Entra Global Administrator must complete a one-time consent process before anyone in the tenant can connect.

**2. Organization-level gating (Team and Enterprise plans)**

On Team and Enterprise plans, access to the connector requires a two-step approval process. First, Owners must explicitly enable the Microsoft 365 connector in Claude organization settings by navigating to Organization settings \> Connectors \> Browse connectors \> Add "Microsoft 365." Until this approval is granted, team members have no access.

Second, after the Owner enables the connector, a Microsoft Entra Global Administrator must complete individual authentication and grant consent on behalf of the whole organization before any team members can connect.

**3. Granular permission revocation**

You can selectively disable specific capabilities via Microsoft Entra Admin Center. For example:

[TABLE]

Changes take effect immediately for all people in your organization. People can also choose to disable capabilities during a chat by selectively toggling off the connector's tools.

**4. Microsoft Conditional Access**

Your Conditional Access policies apply to the connector, but not always in the way they apply to a user working directly in Microsoft 365. When a user connects, Entra evaluates your policies against their sign-in. Every later request is made by Claude's servers. In our testing, Entra evaluates those requests as coming from Anthropic's IP range (`160.79.104.0/21`), identifying the member and carrying the device recorded when they connected, rather than the member's current device or network. What that means for each kind of policy:

- **Group-based access**: Supported. Scope your policy to specific security groups, or set **Assignment required** on both Claude applications as described in **[Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-set-up-the-microsoft-365-connector)**.

- **Multi-factor authentication (MFA)**: Supported. MFA is enforced when the member signs in to connect. If your MFA policy doesn't apply to the connector sign-in, for example because it targets specific applications, or has conditions that can skip MFA there, create a separate policy with no conditions that requires MFA for the two Claude applications.

- **Device compliance**: Supported, with a difference in when it's checked. In our testing, the policy is evaluated against the device the member connects from. A device that doesn't meet the policy isn't stopped at the connect screen; its requests fail from the first tool call afterwards. The connection then carries that device record, and ongoing access is checked against the record rather than the device currently in use, until the member next reconnects. Each member's most recent connection is the one that counts. The record is only created if the member's browser can prove the device to Entra, so a compliant device used with a browser profile that isn't signed in to your organization is treated as not compliant. Members who are blocked (`AADSTS53000`) fix it by reconnecting from a device that meets the policy, in a browser signed in to your organization. Keep the policy assigned to the Claude applications; excluding them removes the check.

- **Location and network restrictions**: Not supported. In our testing, the server-side requests always appear to come from Anthropic's IP range, wherever the member is, so a policy that limits sign-ins to your network or VPN blocks the connector for every member. The same applies to sign-in frequency policies. Learn how to exclude Anthropic's IP range in **[Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-set-up-the-microsoft-365-connector)**.

**Warning:** Don't change a device policy to require a compliant device *or* multi-factor authentication as a workaround. In our testing the MFA proof carries through the stored connection in the same way, so the policy can end up satisfied for every member and the device requirement stops doing anything reliable.

To stop members from connecting a work Microsoft 365 account to a Claude account outside your organization, turn on **[Restrict verified-domain connectors to your enterprise](../13-Enterprise-Admin/restrict-verified-domain-connectors-to-your-enterprise.md)**.

**5. User-level permissions**

- The Microsoft 365 Connector uses **[delegated permissions](https://learn.microsoft.com/en-us/graph/permissions-overview?tabs=http#delegated-permissions)**.

- Users can only access Microsoft 365 data **they already have permission** for

- SharePoint search requires Sites.Read.All permission. Site-specific permissioning (using \*.Selected permissions) is not supported because the underlying search is tenant-wide.

- Users cannot bypass SharePoint sharing settings or folder permissions.

- Users can't access other users' private files or emails. Users can search shared mailboxes they've been granted delegate access to in Microsoft 365, including full access and folder-level delegation. Shared mailbox access remains read-only, via the `Mail.Read.Shared` permission. Email search doesn't reach a user's separate Online Archive (In-Place Archive) mailbox.

- Delegated permissions inherently respect Microsoft 365 data loss prevention (DLP) policies.

**6. Token management**

- Refresh tokens expire after 90 days of inactivity by default, requiring re-authentication. This can be customized in Microsoft Entra ID using a token lifetime policy.

- Access tokens typically expire within 60-90 minutes per Microsoft Entra ID defaults and are automatically refreshed.

- Admins or users can revoke access anytime via Microsoft Entra ID.

- The Microsoft 365 Connector never sees or stores passwords.

## Security architecture summary

### Authentication flow

- **OAuth 2.0 On-Behalf-Of (OBO):** Industry-standard delegated authentication

- **PKCE protection**: Public client uses Proof Key for Code Exchange to prevent authorization code interception

- **Two-stage token exchange**: User authenticates to obtain access token for MCP server, then MCP server exchanges it for Graph API access using OBO flow with confidential client credentials. In this flow, not even the user or their Claude client has access to the OBO tokens. Only the MCP server can access and use tokens with access to the user’s data via the Microsoft Graph API.

- **No credential storage**: Users never share Microsoft passwords with Anthropic

- **Encrypted token storage**: Access and refresh tokens are encrypted while cached by the Claude backend

### Data flow

- Documents and other content are retrieved **only during active queries**

- **Tool call results** from the connector that are **part of stored chats are retained**

- **The user who requested the Claude chat** can see the tool call results and Claude’s response incorporating the data

- **Other users shared on the chat** can only see Claude’s response incorporating the result of the tool call

- Each request creates a fresh data flow which is cleaned up after the response is returned

### Multi-tenant isolation

- Microsoft Entra tenants are **cryptographically separated** from each other using a common-scoped multi-tenant configuration

- Multi-tenant isolation is cryptographically enforced through digitally signed access tokens that bind each user to their organization’s tenant

## Available capabilities

### Read and search tools

The connector provides **read-only** access to:

[TABLE]

### Write tools

[TABLE]

**Note:** “Always allow” is not supported for the following tools:

- `outlook_send_email`

- `outlook_forward_mail`

- `outlook_send_draft`

- `outlook_create_event`

- `outlook_update_event`

- `teams_send_chat_message`

- `teams_send_channel_message`

- `teams_reply_channel_message`

When an organization enables write tools, the connector also exposes write tools for sending and organizing email, managing drafts and calendar events, updating mailbox settings, creating and updating files in OneDrive and SharePoint, and sending Teams messages. Teams write tools are off by default and are enabled individually in **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)** within “Microsoft 365”; the connector-wide "all tools" permission doesn't turn them on. Claude can send messages in Teams but can't change Teams settings, memberships, or permissions.

Write tools include the following built-in safeguards:

- **Attribution:** Emails Claude sends include an attribution header identifying them as agent-initiated. File writes, calendar writes, and Teams messages aren't currently tagged.

- **Rate limits:** Per-user limits apply to writes, sends, and recipients.

- **Attachment restriction:** Attachments aren't supported in any write tool—sending, forwarding, and drafting all reject messages with attachments.

- **Blocked by default:** Organizations that used the connector before write tools launched have write tools blocked by default until an admin enables them. Teams write tools are blocked by default for every organization and must each be enabled individually.

- **Confirmation required:** Sending a Teams chat message and posting or replying in a channel can only be set to Ask, so the user confirms every send.

## Permissions list

**Basic permissions**

- **[User.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#userread)** - Sign in and read user profile (basic requirement)

**Mail permissions**

- **[Mail.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#mailread)** - Read user mail (required for email tools/resources)

- **[Mail.ReadBasic](https://learn.microsoft.com/en-us/graph/permissions-reference#mailreadbasic)** - Read user mail metadata (alternative for limited functionality)

- **[Mail.Read.Shared](https://learn.microsoft.com/en-us/graph/permissions-reference#mailreadshared)** - Read user and shared mail

- **[MailboxFolder.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#mail-permissions)** - Read a user's mailbox folders

- **[MailboxItem.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#mail-permissions)** - Read a user's mailbox items

**Calendar permissions**

- **[Calendars.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#calendarsread)** - Read user calendars and events

- **[Calendars.Read.Shared](https://learn.microsoft.com/en-us/graph/permissions-reference#calendarsreadshared)** - Read calendars user can access, including shared

**User directory**

- **[User.ReadBasic.All](https://learn.microsoft.com/en-us/graph/permissions-reference#userreadbasicall)** - Read basic profiles of all users (for meeting availability)

**Chat permissions**

- **[Chat.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#chatread)** - Read user chat messages

- **[Chat.ReadBasic](https://learn.microsoft.com/en-us/graph/permissions-reference#chatreadbasic)** - Read user chat metadata (alternative for limited functionality)

- **[ChatMember.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#chatmemberread)** - Read the members of chats

- **[ChatMessage.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#chatmessageread)** - Read user chat messages (more specific than Chat.Read)

**Channel permissions**

- **[Channel.ReadBasic.All](https://learn.microsoft.com/en-us/graph/permissions-reference#channelreadbasicall)** - Read the names and descriptions of channels

- **[ChannelMessage.Read.All](https://learn.microsoft.com/en-us/graph/permissions-reference#channelmessagereadall)** - Read channel messages

**Meeting permissions**

- **[OnlineMeetings.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#onlinemeetingsread)** - Read online meetings

- **[OnlineMeetingTranscript.Read.All](https://learn.microsoft.com/en-us/graph/permissions-reference#onlinemeetingtranscriptreadall)** - Read meeting transcripts

- **[OnlineMeetingAiInsight.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#onlinemeetingaiinsightread)** - Read all AI Insights for online meetings

- **[OnlineMeetingArtifact.Read.All](https://learn.microsoft.com/en-us/graph/permissions-reference#onlinemeetingartifactreadall)** - Read user's online meeting artifacts

- **[OnlineMeetingRecording.Read.All](https://learn.microsoft.com/en-us/graph/permissions-reference#onlinemeetingrecordingreadall)** - Read all recordings of online meetings

**Files permissions**

- **[Files.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#filesread)** - Read user files

- **[Files.Read.All](https://learn.microsoft.com/en-us/graph/permissions-reference#filesreadall)** - Read all files user can access

**Sites permissions**

- **[Sites.Read.All](https://learn.microsoft.com/en-us/graph/permissions-reference#sitesreadall)** - Read items in all site collections

**Write permissions**

Requested as part of the updated consent set; used only when write tools are enabled:

- **[Mail.Send](https://learn.microsoft.com/en-us/graph/permissions-reference#mailsend)** - Send and forward email

- **[Mail.ReadWrite](https://learn.microsoft.com/en-us/graph/permissions-reference#mailreadwrite)** - Create, update, and delete drafts; move and label messages

- **[Calendars.ReadWrite](https://learn.microsoft.com/en-us/graph/permissions-reference#calendarsreadwrite)** - Create, update, delete, and respond to calendar events

- **[Files.ReadWrite.All](https://learn.microsoft.com/en-us/graph/permissions-reference#filesreadwriteall)** - Create and update files in OneDrive and SharePoint

- **[MailboxSettings.ReadWrite](https://learn.microsoft.com/en-us/graph/permissions-reference#mailboxsettingsreadwrite)** - Manage categories, inbox rules, and automatic replies

- **[ChatMessage.Send](https://learn.microsoft.com/en-us/graph/permissions-reference#chatmessagesend)** - Send a Teams chat message on the user's behalf

- **[ChannelMessage.Send](https://learn.microsoft.com/en-us/graph/permissions-reference#channelmessagesend)** - Post or reply in a Teams channel

- **[Chat.Create](https://learn.microsoft.com/en-us/graph/permissions-reference#chatcreate)** - Start a new Teams chat on the user's behalf

- **[People.Read](https://learn.microsoft.com/en-us/graph/permissions-reference#peopleread)**: Find people in the organization to start a chat with

## Current limitations

- **Teams write access is limited to messaging**: Claude can send a chat message, post or reply in a channel, or start a new chat, but can't modify Teams settings, memberships, or permissions. All write tools require an admin to enable them, and Teams write tools are enabled individually.

- **User-level access only**: Access with service principal authentication is not supported.

- **Online Archive mailboxes aren't searched**: email search covers each user's primary mailbox, including its Archive folder, and any shared mailboxes they can access. It doesn't cover the separate Online Archive mailbox (also called the In-Place Archive), so messages that a retention policy has moved there won't appear in results.

## Frequently asked questions

### Can we test with a small pilot group before enterprise-wide rollout?

Yes. The recommended approach is to use app assignment to restrict who can use the connector:

- Enable the connector (Team and Enterprise Owners enable it in organization settings; individual plan users can connect directly).

- Microsoft Entra Admin completes pre-consent setup

- Use Microsoft Entra Enterprise App assignment to restrict access to specific users or groups (e.g., assign only "IT Security Test Group" to the app).

- Expand groups progressively for gradual deployment

### How do we ensure no data leakage occurs between our organization and others in the multi-tenant environment?

Multi-tenant isolation ensures complete separation:

- Server uses the common tenant configuration to accept tokens from any Microsoft Entra ID tenant

- Each user's token contains their organization's tenant ID (tid claim) which is validated

- Graph API tokens obtained through OBO are automatically scoped to the user and their tenant

- Cross-tenant token access is prevented cryptographically by the design of Microsoft Graph’s OAuth 2.0 implementation.

### What happens if someone tries to connect with a personal Microsoft account?

The connector requires a Microsoft Entra tenant tied to a Microsoft Business plan. Personal Microsoft accounts (@outlook.com, @hotmail.com) can't be used to authenticate. People attempting to connect with a personal account will receive an authentication error.

### Do you have audit logging for compliance?

Yes. All Graph API calls made by the connector are logged in your organization's Microsoft 365 audit log, which you can access through the M365 Compliance Center. These logs show the timestamp, user, operation performed, and resource accessed, with retention periods matching your Microsoft 365 audit policy. Additionally, Anthropic logs authentication and tool execution events.

### Can we revoke access if we discover unauthorized usage?

There are multiple revocation methods:

- **Individual:** Users disconnect via **Customize \> Connectors**

- **Admin-level**: On Team and Enterprise plans, Owners disable the connector in Claude organization settings (all team members affected).

- **Permission-level**: Revoke specific permissions in Microsoft Entra Admin Center

- **Tenant-level**: Revoke all permissions in Microsoft Entra Admin Center

### What certifications does Anthropic have?

Anthropic has the following certifications:

- **SOC 2 Type II** (annual audit)

- **ISO 27001** certified

- **GDPR compliant** (DPA available)

- **Microsoft publisher-verified** application

## Additional resources

- **[Set up the Microsoft 365 connector](https://support.claude.com/en/articles/12542951-)**

- **[Connect Claude to Microsoft 365](connect-to-microsoft-365.md)**

- **[Overview of Microsoft Graph permissions: Delegated permissions](https://learn.microsoft.com/en-us/graph/permissions-overview?tabs=http#delegated-permissions)**

---

## Claude Code in Slack - Claude Code Docs

Source: https://code.claude.com/docs/en/slack
Path: 14-Connectors/slack.md

## On this page

- [Use cases](#use-cases)
- [Prerequisites](#prerequisites)
- [Setting up Claude Code in Slack](#setting-up-claude-code-in-slack)
- [How it works](#how-it-works)
- [Automatic detection](#automatic-detection)
- [Context gathering](#context-gathering)
- [Session flow](#session-flow)
- [User interface elements](#user-interface-elements)
- [Message actions](#message-actions)
- [Repository selection](#repository-selection)
- [Access and permissions](#access-and-permissions)
- [User-level access](#user-level-access)
- [Workspace-level access](#workspace-level-access)
- [Channel-based access control](#channel-based-access-control)
- [What’s accessible where](#what%E2%80%99s-accessible-where)
- [Best practices](#best-practices)
- [Writing effective requests](#writing-effective-requests)
- [When to use Slack vs. web](#when-to-use-slack-vs-web)
- [Troubleshooting](#troubleshooting)
- [”Claude Code is not enabled for your account”](#%E2%80%9Dclaude-code-is-not-enabled-for-your-account%E2%80%9D)
- [Sessions not starting](#sessions-not-starting)
- [Sessions from a Claude Tag channel fail to start](#sessions-from-a-claude-tag-channel-fail-to-start)
- [Repository not showing](#repository-not-showing)
- [Wrong repository selected](#wrong-repository-selected)
- [Authentication errors](#authentication-errors)
- [Current limitations](#current-limitations)
- [Related resources](#related-resources)

Platforms and integrations

# Claude Code in Slack

Copy pageCopy page

Delegate coding tasks directly from your Slack workspace. Anthropic is retiring this earlier version for Team and Enterprise workspaces in favor of Claude Tag; it remains the setup path on Pro and Max plans.

Copy pageCopy page

This page documents the earlier Claude Code in Slack, which runs each session under an individual user’s account.

- **Team and Enterprise plans:** Anthropic is retiring this version in favor of [Claude Tag](claude-for-slack.md), which runs @Claude as your organization’s shared identity with admin-configured access. Your existing Slack app and @Claude handle stay, and your Anthropic account team can tell you the cutover date. [Set up Claude Tag](https://claude.com/docs/claude-tag/overview) for a new workspace; to move one that already uses this version, see [Migrate from the earlier Claude in Slack](https://claude.com/docs/claude-tag/admins/migrate-from-earlier).
- **Pro and Max plans:** Claude Tag isn’t available on individual plans, so this page remains the setup path.

Claude Code in Slack brings the power of Claude Code directly into your Slack workspace. When you mention `@Claude` with a coding task, Claude automatically detects the intent and creates a Claude Code cloud session, allowing you to delegate development work without leaving your team conversations. This integration is built on the existing Claude for Slack app but adds intelligent routing to Claude Code cloud sessions for coding-related requests. Each session runs under your own Claude account, using your connected repositories and your plan limits.

[](#use-cases)

Use cases

- **Bug investigation and fixes**: Ask Claude to investigate and fix bugs as soon as they’re reported in Slack channels.
- **Quick code reviews and modifications**: Have Claude implement small features or refactor code based on team feedback.
- **Collaborative debugging**: When team discussions provide crucial context (for example, error reproductions or user reports), Claude can use that information to inform its debugging approach.
- **Parallel task execution**: Kick off coding tasks in Slack while you continue other work, receiving notifications when complete.

[](#prerequisites)

Prerequisites

Before using Claude Code in Slack, ensure you have the following:

| Requirement | Details |
|:---------------------|:--------------------------------------------------------------------------------------------------|
| Claude Plan | Pro, Max, Team, or Enterprise with Claude Code access (premium seats or Chat + Claude Code seats) |
| Cloud sessions | [Cloud sessions](../02-Claude-Code-CLI/claude-code-on-the-web.md) are enabled for your account |
| GitHub Account | Connected at [claude.ai/code](https://claude.ai/code) with at least one repository authenticated |
| Slack Authentication | Your Slack account linked to your Claude account via the Claude app |

[](#setting-up-claude-code-in-slack)

Setting up Claude Code in Slack

Install the Claude App in Slack

A workspace administrator must install the Claude app from the Slack App Marketplace. Visit the [Slack App Marketplace](https://slack.com/marketplace/A08SF47R6P4) and click “Add to Slack” to begin the installation process.

Connect your Claude account

After the app is installed, authenticate your individual Claude account:

1. Open the Claude app in Slack by clicking on “Claude” in your Apps section
2. Open the App Home tab
3. Click “Connect” to link your Slack account with your Claude account
4. Complete the authentication flow in your browser

Configure cloud sessions

Ensure cloud sessions are properly configured for your account:

- Visit [claude.ai/code](https://claude.ai/code) and sign in with the same account you connected to Slack
- Connect your GitHub account if not already connected
- Authenticate at least one repository that you want Claude to work with

Choose your routing mode

After connecting your accounts, configure how Claude handles your messages in Slack. Open the Claude App Home in Slack to find the **Routing Mode** setting.

| Mode | Behavior |
|:----------------|:-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Code only** | Claude routes all @mentions to Claude Code sessions. Best for teams using Claude in Slack exclusively for development tasks. |
| **Code + Chat** | Claude analyzes each message and intelligently routes between Claude Code (for coding tasks) and Claude Chat (for writing, analysis, and general questions). Best for teams who want a single @Claude entry point for all types of work. |

In Code + Chat mode, if Claude routes a message to Chat but you wanted a coding session, you can click “Retry as Code” to create a Claude Code session instead. Similarly, if it’s routed to Code but you wanted a Chat session, you can choose that option in that thread.

Add Claude to channels

Claude is not automatically added to any channels after installation. To use Claude in a channel, invite it by typing `/invite @Claude` in that channel. Claude can only respond to @mentions in channels where it has been added.

[](#how-it-works)

How it works

[](#automatic-detection)

Automatic detection

In Code + Chat routing mode, when you mention @Claude in a Slack channel or thread, Claude automatically detects whether your message is a coding task. Coding tasks go to a Claude Code cloud session. Anything else gets a regular chat reply. In Code only mode, every @mention goes to Claude Code. You can also explicitly tell Claude to handle a request as a coding task, even if it doesn’t automatically detect it.

Claude Code in Slack only works in channels (public or private). It does not work in direct messages (DMs).

[](#context-gathering)

Context gathering

**From threads**: When you @mention Claude in a thread, it gathers context from all messages in that thread to understand the full conversation. **From channels**: When mentioned directly in a channel, Claude looks at recent channel messages for relevant context. This context helps Claude understand the problem, select the appropriate repository, and inform its approach to the task.

When @Claude is invoked in Slack, Claude is given access to the conversation context to better understand your request. Claude may follow directions from other messages in the context, so users should make sure to only use Claude in trusted Slack conversations.

[](#session-flow)

Session flow

1. **Initiation**: You @mention Claude with a coding request
2. **Detection**: Claude analyzes your message and detects coding intent
3. **Session creation**: A new Claude Code session is created on claude.ai/code
4. **Progress updates**: Claude posts status updates to your Slack thread as work progresses
5. **Completion**: When finished, Claude @mentions you with a summary and action buttons
6. **Review**: Click “View Session” to see the full transcript, or “Create PR” to open a pull request

[](#user-interface-elements)

User interface elements

[](#message-actions)

Message actions

- **View Session**: Opens the full Claude Code session in your browser where you can see all work performed, continue the session, or make additional requests.
- **Create PR**: Creates a pull request directly from the session’s changes.
- **Retry as Code**: If Claude initially responds as a chat assistant but you wanted a coding session, click this button to retry the request as a Claude Code task.
- **Change Repo**: Lets you select a different repository if Claude chose incorrectly.

[](#repository-selection)

Repository selection

Claude automatically selects a repository based on context from your Slack conversation. If multiple repositories could apply, Claude may display a dropdown allowing you to choose the correct one.

[](#access-and-permissions)

Access and permissions

[](#user-level-access)

User-level access

| Access Type | Requirement |
|:---------------------|:----------------------------------------------------------------|
| Claude Code Sessions | Each user runs sessions under their own Claude account |
| Usage & Rate Limits | Sessions count against the individual user’s plan limits |
| Repository Access | Users can only access repositories they’ve personally connected |
| Session History | Sessions appear in your Claude Code history on claude.ai/code |

[](#workspace-level-access)

Workspace-level access

Slack workspace administrators control whether the Claude app is available in their workspace:

| Control | Description |
|:-----------------------------|:------------------------------------------------------------------------------------------------------------------|
| App installation | Workspace admins decide whether to install the Claude app from the Slack App Marketplace |
| Enterprise Grid distribution | For Enterprise Grid organizations, organization admins can control which workspaces have access to the Claude app |
| App removal | Removing the app from a workspace immediately revokes access for all users in that workspace |

[](#channel-based-access-control)

Channel-based access control

Installing the app doesn’t add Claude to any channels. Claude responds to @mentions only in channels where it has been added; invite it with `/invite @Claude`. It works in both public and private channels. Admins can control who uses Claude Code by managing which channels Claude is invited to and who has access to those channels. This adds a layer of access control beyond workspace-level permissions.

[](#what’s-accessible-where)

What’s accessible where

**In Slack**: You’ll see status updates, completion summaries, and action buttons. The full transcript is preserved and always accessible. **At claude.ai/code**: The complete Claude Code session with full conversation history, all code changes, and file operations. Sessions stay in your Claude Code history at [claude.ai/code](https://claude.ai/code), where you can continue past sessions, reference them, or create pull requests. For Enterprise and Team accounts, sessions created from Claude in Slack are automatically visible to the organization. See [cloud session sharing](../02-Claude-Code-CLI/claude-code-on-the-web.md#share-sessions) for more details.

[](#best-practices)

Best practices

[](#writing-effective-requests)

Writing effective requests

- **Be specific**: Include file names, function names, or error messages when relevant.
- **Provide context**: Mention the repository or project if it’s not clear from the conversation.
- **Define success**: Explain what “done” looks like. Should Claude write tests? Update documentation? Create a PR?
- **Use threads**: Reply in threads when discussing bugs or features so Claude can gather the full context.

[](#when-to-use-slack-vs-web)

When to use Slack vs. web

**Use Slack when**: Context already exists in a Slack discussion, you want to start a task asynchronously, or you’re collaborating with teammates who need visibility. **Use the web directly when**: You need to upload files, want real-time interaction during development, or are working on longer, more complex tasks.

[](#troubleshooting)

Troubleshooting

[](#”claude-code-is-not-enabled-for-your-account”)

”Claude Code is not enabled for your account”

This error means your Claude account has no cloud environment yet. Sign in at [claude.ai/code](https://claude.ai/code) once with the same account you connected to Slack and finish [web onboarding](../02-Claude-Code-CLI/web-quickstart.md#connect-github), which creates your default cloud environment or asks you to create it. The error clears on your next mention. Each user must do this individually.

[](#sessions-not-starting)

Sessions not starting

1. Verify your Claude account is connected in the Claude App Home
2. Check that cloud sessions are enabled for your account
3. Ensure you have at least one GitHub repository connected to Claude Code

[](#sessions-from-a-claude-tag-channel-fail-to-start)

Sessions from a Claude Tag channel fail to start

This entry applies to workspaces using [Claude Tag](https://claude.com/docs/claude-tag/overview), where Claude works in channels as your organization’s shared identity, not as any member’s account. If you created the channel’s cloud environment at [claude.ai/code](https://claude.ai/code), it belongs to your personal account, and Claude can’t start channel sessions in a personal environment. Claude Code fails the session immediately, and retrying doesn’t help. If you’re an Owner and the environment is your own, [share it with the organization](../02-Claude-Code-CLI/cloud-environments.md#organization-shared-environments) from the environment selector. Otherwise, an Owner recreates it as an organization-shared environment from the **Cloud environments** page in [admin settings](https://claude.ai/admin-settings). You can apply it in two ways:

- Set it as the organization default at [claude.ai/admin-settings/claude-code](https://claude.ai/admin-settings/claude-code).
- [Set it on the channel](https://claude.com/docs/claude-tag/admins/troubleshooting#channel-sessions-use-the-wrong-environment-or-can%E2%80%99t-find-one) in the Claude Tag admin settings.

If you’re not an Owner, send this entry to one.

[](#repository-not-showing)

Repository not showing

1. Connect the repository at [claude.ai/code](https://claude.ai/code)
2. Verify your GitHub permissions for that repository
3. Try disconnecting and reconnecting your GitHub account

[](#wrong-repository-selected)

Wrong repository selected

1. Click the “Change Repo” button to select a different repository
2. Include the repository name in your request for more accurate selection

[](#authentication-errors)

Authentication errors

1. Disconnect and reconnect your Claude account in the App Home
2. Ensure you’re signed into the correct Claude account in your browser
3. Check that your Claude plan includes Claude Code access

[](#current-limitations)

Current limitations

- **GitHub only**: repositories must be on GitHub.
- **One PR at a time**: each session can create one pull request.
- **Cloud session access required**: users need access to [cloud sessions](../02-Claude-Code-CLI/claude-code-on-the-web.md); without it, Claude replies with standard chat responses.

[](#related-resources)

Related resources

## Claude Code in the cloud

Learn more about cloud sessions

## Claude for Slack

General Claude for Slack documentation

## Claude Tag

Organization-managed @Claude in Slack with admin-configured access

## Slack App Marketplace

Install the Claude app from the Slack Marketplace

## Claude Help Center

Get additional support

---

## Use Claude for Outlook - Claude.ai Documentation

Source: https://support.claude.com/en/articles/14855664-use-claude-for-outlook
Path: 14-Connectors/use-claude-for-outlook.md

## On this page

- [What you can do](#what-you-can-do)
- [Get started with Claude for Outlook](#get-started-with-claude-for-outlook)
- [Supported versions](#supported-versions)
- [Install for yourself](#install-for-yourself)
- [Deploy to your organization](#deploy-to-your-organization)
- [Install from a manifest file](#install-from-a-manifest-file)
- [Grant Microsoft Graph consent](#grant-microsoft-graph-consent)
- [Use your own Entra app instead](#use-your-own-entra-app-instead)
- [Deploy in a US Government or national cloud](#deploy-in-a-us-government-or-national-cloud)
- [Connect through a third-party platform](#connect-through-a-third-party-platform)
- [Triage your inbox](#triage-your-inbox)
- [Draft replies in your voice](#draft-replies-in-your-voice)
- [Summarize long threads](#summarize-long-threads)
- [Read attachments inline](#read-attachments-inline)
- [Search your mailbox](#search-your-mailbox)
- [Find time and create events](#find-time-and-create-events)
- [Prep for meetings](#prep-for-meetings)
- [Work across M365 apps](#work-across-m365-apps)
- [Model availability](#model-availability)
- [How Claude accesses your mailbox](#how-claude-accesses-your-mailbox)
- [When you sign in with a Claude account](#when-you-sign-in-with-a-claude-account)
- [When you connect through a third-party platform](#when-you-connect-through-a-third-party-platform)
- [Chat history](#chat-history)
- [Data retention and audit](#data-retention-and-audit)
- [Prompt injection risks](#prompt-injection-risks)
- [Recommended use during beta](#recommended-use-during-beta)

# Use Claude for Outlook

Copy pageCopy page

An Outlook add-in that integrates Claude into your inbox and calendar, for Pro, Max, Team, and Enterprise plans.

Copy pageCopy page

Claude for Outlook is an add-in that brings Claude into your Outlook inbox and calendar. It is built for professionals whose work runs through email, including private equity and investment banking associates managing deal flow, in-house legal teams running counterparty negotiations, and consultants tracking multiple client threads.

Claude for Outlook is currently in beta and available to Pro, Max, Team, and Enterprise plans.

[](#what-you-can-do)

What you can do

With Claude for Outlook, you can:

- Triage your unread inbox into what needs you, what Claude can handle, and what is noise.
- Draft replies, reply-alls, and forwards in your voice, landed unsent in Outlook’s compose pane.
- Summarize long threads into decisions made, open items, and who owes what, with per-email citations.
- Read `.docx` and `.xlsx` attachments inline without opening them.
- Find meeting times across attendees and draft invites into Outlook’s native appointment form.
- Prep for your next meeting with a one-page brief of recent threads and attached documents.

[](#get-started-with-claude-for-outlook)

Get started with Claude for Outlook

[](#supported-versions)

Supported versions

Claude for Outlook runs on the following Outlook clients.

- Outlook on the web
- Outlook on Windows, both new Outlook and classic Outlook, with a Microsoft 365 subscription
- Outlook on Mac with a Microsoft 365 subscription

The following are not supported: Outlook 2016 and 2019 perpetual or volume-licensed editions, Outlook on iOS, Outlook on Android, and mailboxes hosted on Exchange on-premises. Exchange Online through Microsoft 365 is required.

[](#install-for-yourself)

Install for yourself

Open the marketplace listing

Go to the [Claude for Outlook listing on Microsoft AppSource](https://appsource.microsoft.com/).

Install the add-in

Select “Get it now” to install.

Open Claude in Outlook

Open Outlook, open any email, select the Claude button in the message ribbon, and sign in with your Claude account.

If you do not see the Claude button on the message, open the overflow menu on the reading pane, choose Customize actions, and check Claude under Apps. It then appears on every message and in the Home ribbon.

[](#deploy-to-your-organization)

Deploy to your organization

Organization admins can deploy Claude for Outlook through the Microsoft 365 Admin Center.

Allow Office Store access

In the [Microsoft 365 Admin Center](https://admin.microsoft.com), go to Settings, Org Settings, User owned apps and services, and turn on [“Let users access the Office Store”](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-addins-in-the-admin-center).

Open Integrated apps

Go to Settings, then Integrated apps.

Find the add-in

Search for “Claude for Outlook” in Microsoft AppSource.

Deploy

Deploy the add-in to your organization or to specific people. See [Microsoft’s deployment guide](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-deployment-of-add-ins) for assignment options.

Grant Microsoft Graph consent

Complete the [Microsoft Graph admin consent](#grant-microsoft-graph-consent) step below so users are not prompted individually.

If your organization uses Microsoft Entra Privileged Identity Management (PIM) for admin roles, the Integrated apps page does not recognize roles activated through PIM, so deployment fails. This is a [known Microsoft issue](https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues), tracking ID 11126536. To work around it, deploy from an admin account with the required role assigned as permanently active rather than PIM-eligible. See [Microsoft’s troubleshooting guidance](https://learn.microsoft.com/en-us/troubleshoot/microsoft-365/admin/miscellaneous/cannot-deploy-add-in-integrated-apps-menu). Individual users can still [install the add-in themselves](#install-for-yourself).

After installation, team members open Outlook, open any email, select the Claude button in the message ribbon, and sign in with their Claude credentials. Pinning the task pane keeps it open as you move between messages.

Organizations that have disabled “Let users access the Office Store” may find that admin-deployed add-ins don’t appear for users. To work around this, deploy using the manifest XML file described below.

[](#install-from-a-manifest-file)

Install from a manifest file

If your organization blocks the Microsoft Store, an IT administrator can deploy the add-in by uploading its manifest file directly.

Download the manifest

Download the [Claude for Outlook manifest](https://pivot.claude.ai/manifest-outlook.xml) and save it to a secure location.

Open Integrated apps

In the [Microsoft 365 Admin Center](https://admin.microsoft.com), go to Settings, then Integrated apps.

Upload the add-in

Select Upload custom apps, then Office Add-in. Choose “I have a manifest file on this device”, select the file you downloaded, and upload it.

Assign people

Choose your deployment scope: the entire organization, specific people, specific groups, or just yourself for testing.

Deploy

Review the settings and select Deploy. The add-in appears within minutes for most people. Full organization rollout can take up to 24 hours on the Microsoft 365 side.

Grant Microsoft Graph consent

Complete the consent step in the next section.

[](#grant-microsoft-graph-consent)

Grant Microsoft Graph consent

Claude for Outlook reads mail and calendar data through Microsoft Graph. This requires a one-time tenant-wide grant from a Global Administrator and is separate from the Integrated apps deployment. Have a Global Administrator open the following admin consent link in a browser where they are signed in to your Microsoft 365 tenant.

```python
https://login.microsoftonline.com/organizations/v2.0/adminconsent?client_id=c2995f31-11e7-4882-b7a7-ef9def0a0266&scope=https://graph.microsoft.com/Mail.ReadWrite%20https://graph.microsoft.com/Calendars.Read%20https://graph.microsoft.com/User.Read%20offline_access&redirect_uri=https://pivot.claude.ai/auth/callback
```

The administrator sees a Microsoft permissions screen listing `Mail.ReadWrite`, `Calendars.Read`, `User.Read`, and `offline_access`. After they select Accept, all users in the organization can use Claude for Outlook without additional Microsoft prompts. The grant takes effect immediately. Only the add-in rollout in the previous step can take up to 24 hours. If this step is skipped, every user sees a “Need admin approval” message when Claude first tries to read mail or calendar data. The redirect to `pivot.claude.ai` after consent carries only the consent outcome, never a token or authorization code. See [Why sign-in redirects through pivot.claude.ai](https://support.claude.com/docs/office-agents/third-party-platforms#why-sign-in-redirects-through-pivotclaudeai) for what each redirect carries and how to verify it in a network capture.

[](#use-your-own-entra-app-instead)

Use your own Entra app instead

If your organization’s policy does not permit consenting to a third-party multi-tenant application, register a single-tenant application in the Microsoft Entra admin center and have the add-in use it instead. The data flow is identical; the Graph token stays in the user’s Outlook client either way. The difference is that approval and Conditional Access policy live entirely under an application your organization owns.

In the Entra admin center, go to App registrations and create a new registration. Choose “Accounts in this organizational directory only”.

Configure authentication

Under Authentication, add a Single-page application platform with redirect URI `brk-multihub://pivot.claude.ai`. In Advanced settings, set “Allow public client flows” to Yes.

Add Graph permissions

Under API permissions, add the Microsoft Graph delegated permissions `Mail.ReadWrite`, `Calendars.Read`, `User.Read`, and `offline_access`. Select “Grant admin consent” for your tenant.

Append the client ID to the manifest URL

Copy the application’s client ID from the Overview page. Append `?graph_client_id=YOUR_CLIENT_ID` to the manifest URL from the [Install from a manifest file](#install-from-a-manifest-file) section and use that URL when downloading the manifest.

With this option, skip the admin consent link entirely. Users do not see a Microsoft permissions prompt because your tenant has already consented to your own application.

[](#deploy-in-a-us-government-or-national-cloud)

Deploy in a US Government or national cloud

If your Microsoft 365 tenant is in GCC High, DoD, or 21Vianet, register your own Entra application with `graph_client_id` as described above (Anthropic’s multi-tenant application exists only in the global cloud) and set `graph_cloud` to the matching value:

| Tenant | `graph_cloud` |
|-------------------|------------------------------------|
| Commercial or GCC | `global` (default; may be omitted) |
| GCC High | `us-gov-high` |
| DoD | `us-gov-dod` |
| 21Vianet (China) | `china` |

For a DoD tenant the manifest URL ends with:

```python
?graph_client_id=YOUR_CLIENT_ID&graph_cloud=us-gov-dod
```

For GCC High and 21Vianet tenants, `graph_cloud` may be omitted: the add-in detects those clouds at sign-in from the authority host Outlook reports. Setting it explicitly is still recommended when your compliance program requires the endpoints to be fixed in the reviewed manifest rather than derived at runtime. DoD tenants share an authority host with GCC High, so `graph_cloud=us-gov-dod` is always required for DoD.

[](#connect-through-a-third-party-platform)

Connect through a third-party platform

If your organization routes API traffic through an internal LLM gateway, Amazon Bedrock, Google Cloud Vertex AI, or Azure AI Foundry, you can use the add-in without Claude accounts. This is the same gateway pattern used by Claude Code. For setup instructions and gateway requirements, see [Use Claude for M365 with third-party platforms](https://support.claude.com/docs/office-agents/third-party-platforms).

[](#triage-your-inbox)

Triage your inbox

Ask Claude what needs your attention. Claude reads your unread mail and attachments and sorts them into three groups: action items for you, items Claude can handle for your review, and noise you can archive in one selection. Each action item carries a one-line reason. Items Claude can handle, such as scheduling asks, acknowledgments, and standard-form documents, arrive pre-drafted. Prompts to try:

- “What needs me?”
- “Draft replies for everything you can handle”
- “Archive all the calendar responses and newsletters”

[](#draft-replies-in-your-voice)

Draft replies in your voice

Tell Claude what you want to say. It drafts the reply into Outlook’s native compose pane, unsent. Tone is learned from your sent folder, so the draft matches your sentence length and formality register. Claude leaves the closing off so Outlook can append your configured signature without duplication. Claude chooses reply versus reply-all deliberately and warns before adding anyone who was not on the thread. Prompts to try:

- “Reply to this and agree to the extension, push back on the fee”
- “Reply-all thanking everyone and confirming Thursday works”
- “Forward this to Dana with a two-line summary”

[](#summarize-long-threads)

Summarize long threads

Claude reads the entire conversation, including every reply and forward, and tells you what has been decided, what is still open, and who owes what. Every claim cites the specific email it came from. Selecting a citation opens that message in Outlook. Prompts to try:

- “What’s been decided and what’s still open?”
- “Who owes what on this thread?”

[](#read-attachments-inline)

Read attachments inline

Claude reads `.docx` and `.xlsx` attachments on the open email without you opening them. For `.pptx` attachments, open the deck in PowerPoint with the thread loaded as context using [Work across M365 apps](https://support.claude.com/docs/office-agents/work-across-apps). PDF attachments are not currently read inline; save the file and upload it through the sidebar instead. Prompts to try:

- “Summarize the attached memo”
- “What’s in the spreadsheet on this email?”

[](#search-your-mailbox)

Search your mailbox

Ask Claude to find a past conversation by topic, not only by keywords. Results return as citations that open the source message in Outlook so you can verify every answer against the original email. Prompts to try:

- “When did we last discuss the cap with Fernwood?”
- “Find the email where Dana sent the revised term sheet”

[](#find-time-and-create-events)

Find time and create events

Claude checks free/busy for everyone whose calendar you can see and proposes slots that respect working hours and existing holds. The invite is drafted into Outlook’s native appointment form with attendees, subject, and agenda for you to review and send. Prompts to try:

- “Find 30 minutes with Dana and the Fernwood team next week”
- “Block Thursday afternoon for deep work”

[](#prep-for-meetings)

Prep for meetings

For your next event, Claude pulls the last thread with each attendee and any attached documents into a one-page brief, so you walk in knowing the open items and what each person last said. Prompts to try:

- “Prep me for my 2pm”
- “What’s open with Dana before our call?”

[](#work-across-m365-apps)

Work across M365 apps

Claude for Outlook shares context with Claude for Excel, PowerPoint, and Word, so Claude can work across your open Office apps in a single conversation. For example, you can open an attached letter of intent in Word with the email thread already loaded as context, or pull numbers from an email into an open Excel model, without copying between apps. For setup instructions, see [Work across M365 apps](https://support.claude.com/docs/office-agents/work-across-apps).

[](#model-availability)

Model availability

When you sign in with a Claude account, you can choose between Claude Opus 4.7, Opus 4.6, and Sonnet 4.6. When you connect through a third-party platform such as Vertex AI, Azure AI Foundry, or an LLM gateway, Opus 4.7 is the only officially supported model.

[](#how-claude-accesses-your-mailbox)

How Claude accesses your mailbox

Claude reads the email or event you have open via Office.js. For anything that spans your mailbox or calendar, including thread retrieval, search, free/busy lookups, and move or flag operations, Claude uses Microsoft Graph. All Graph calls run in your browser, and the Graph access token stays in the browser’s MSAL cache and is never sent to Anthropic. Claude never sends mail or invites on its own. The add-in does not request the `Mail.Send` permission. Every draft lands unsent in Outlook’s compose or appointment form, and you click Send.

Where mailbox content goes after Claude reads it depends on how you sign in.

[](#when-you-sign-in-with-a-claude-account)

When you sign in with a Claude account

Mailbox content that Claude reads becomes part of the prompt sent to `api.anthropic.com`. Standard API retention applies: see [Data retention and audit](#data-retention-and-audit). The add-in does not keep a server-side copy or index of your mailbox.

[](#when-you-connect-through-a-third-party-platform)

When you connect through a third-party platform

The prompt goes only to the inference endpoint you configured, such as Amazon Bedrock, Vertex AI, Azure AI Foundry, or an LLM gateway. On Amazon Bedrock, Vertex AI, or a gateway that routes to them, no mailbox content reaches Anthropic. On Azure AI Foundry, Anthropic operates the Claude models and processes prompts as an independent processor for Microsoft, as described in [Claude in Microsoft Foundry](https://support.claude.com/en/20-Models/build-with-claude-claude-in-microsoft-foundry-cac680095c.md). See [Use Claude for M365 with third-party platforms](https://support.claude.com/docs/office-agents/third-party-platforms) for configuration details. The add-in does not keep a server-side copy or index of your mailbox.

[](#chat-history)

Chat history

Chat history is stored locally in your browser using IndexedDB. Conversations are not stored on Anthropic’s servers and are not synced across devices or browsers. You can clear all chat history from Settings at any time. The local store is also cleared when you clear your browser data. Chat history is specific to the combination of the add-in surface, your user ID, and your organization ID, so your Excel and Outlook histories are separate. Reinstalling the add-in or switching between Claude add-ins does not remove it. See [Data storage and retention](https://support.claude.com/docs/office-agents/data-storage) for where it sits on disk and how long it is kept.

[](#data-retention-and-audit)

Data retention and audit

For Claude for Outlook use, inputs and outputs are deleted on Anthropic’s backend within 30 days of receipt or generation, except as described in [How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data) Enterprise organizations can route full audit telemetry from Claude for Outlook to their own OpenTelemetry collector for integration with a SIEM or observability platform. See [Configure a custom OpenTelemetry collector](https://support.claude.com/docs/office-agents/enterprise-readiness) for setup. On Pro, Max, and Team plans, observability and audit export are not available. Claude for Outlook does not inherit custom data retention settings your organization may have configured and is not included in Enterprise audit logs. For Enterprise organizations with the [Compliance API](../04-API-Reference/Other/manage-claude-compliance-api.md) enabled, Claude for Outlook sessions are included in the Compliance API. This coverage is in public beta and requires no additional setup: the same Compliance Access Keys apply.

[](#prompt-injection-risks)

Prompt injection risks

Be cautious with email from external or untrusted senders. Email bodies and attachments are untrusted input and may contain instructions intended to manipulate Claude rather than you. Prompt injection refers to malicious instructions hidden in an email body, signature, or attachment that try to trick the AI into taking unintended actions. For example, a routine inbound email might contain hidden text instructing Claude to forward a thread or draft a reply you did not ask for. Claude may interpret these instructions as legitimate requests. Review every draft and inbox action before accepting it, especially when working with email from external or untrusted senders.

[](#recommended-use-during-beta)

Recommended use during beta

As a beta feature, Claude for Outlook is not recommended for:

- Unattended sending. Claude never sends mail or invites on its own; every draft lands unsent for your review.
- Client-facing or counterparty correspondence without reading the draft first.
- Replacing your judgment on which emails matter or how to handle a relationship.
- Mailboxes containing privileged or regulated data without appropriate organizational controls.

To use Claude for Outlook safely and effectively:

- Review drafted replies and invites before sending, especially recipient lists.
- Verify thread summaries against the cited source emails for high-stakes conversations.
- Apply appropriate Microsoft 365 permissions and Conditional Access policies for the add-in.
- Maintain human oversight for anything leaving your organization.

---

## Use connectors to extend Claude's capabilities | Claude Help Center

Source: https://support.claude.com/en/articles/11176164-pre-built-web-connectors-using-remote-mcp
Path: 14-Connectors/use-connectors-to-extend-claude-s-capabilities.md

# Use connectors to extend Claude's capabilities

August 20, 2026

This guide explains how to enable and use connectors with Claude to enhance its capabilities.

Web connectors are available for all users on Claude, Cowork, Claude Desktop, and Claude Mobile (iOS and Android). Desktop extensions are available to all users on Claude Desktop.

## What are connectors?

Connectors let Claude access your apps and services, retrieve your data, and take actions within connected services. Claude inherits each person's permissions from the connected service. If someone can't access a specific file, channel, or record in the source system, the connector can't reach it from Claude either.

For example, you can connect Claude to Linear to create issues, to Slack to send messages, or to Google Drive to search your files. Connectors work across Claude, Claude Desktop, Claude Code, and the API (via the **[MCP Connector](../04-API-Reference/Agents-Tools/agents-and-tools-mcp-connector.md)**). Setup details for individual pre-built connectors are in **[Claude Docs: Connectors](https://claude.com/docs/connectors/overview)**.

You can find available connectors in the **[Connectors Directory](https://claude.ai/connectors)**, where each connector has a page detailing its use cases, read/write capabilities, and availability. You can also add custom connectors or connect to any service that supports MCP.

## How Claude suggests connected apps

Once you've connected an app, Claude can bring it into a conversation on its own when it fits what you're asking for—you don't have to name it every time. For details on how that works, including what happens when more than one app could help, see **[How Claude suggests connected apps](../15-Claude-AI-Features/how-claude-suggests-connected-apps.md)**.

## Browse available connectors

You can browse the Connectors Directory on Claude, Claude Desktop, and Claude for iOS/Android.

You can browse the directory from two areas:

**From a chat**

1. Click the "+" button in the lower left corner of your chat, or type "/" to open the menu.

2. Hover over “Connectors.”

3. Select “Manage connectors.”

4. Click the “+” button next to **Connectors**.

5. This opens a **Connectors** modal where you can see available connectors by category or scroll through the complete list.

**From settings**

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Click the “+” button next to **Connectors**.

3. Browse available connectors by category or scroll through the complete list.

------------------------------------------------------------------------

## Connect a service to Claude

You can connect Claude to a new service on Claude, Claude Desktop, and Claude for iOS and Android. Installing connectors on mobile is currently in beta—Claude Desktop and web remain the primary path for custom connectors.

To connect a service from the directory:

1. Click on the connector you want to add.

2. Review the connector's description and capabilities.

3. Click “Connect” or “Install” to begin the setup process.

4. Follow the authentication prompts to grant Claude access to your account.

5. Configure any specific settings or permissions as needed.

**Important:** When connecting to a service, you're granting Claude permission to access and potentially modify data within that service based on your account permissions. Only connect services you trust and need for your workflows.

## Connect a service on Team and Enterprise plans

Before members of Team and Enterprise plans can use connectors, an Owner or Primary Owner needs to enable them for the organization. Enabling a connector makes it available to your team, but it doesn't automatically grant anyone access. Each person still needs to authenticate individually before they can use it.

**Note:** With Enterprise-managed auth, you authorize a connector once for your entire organization, and your team inherits access automatically on first login. Enterprise-managed auth is available in beta for Team and Enterprise plans on Claude. Learn about **[authorizing MCP connectors for your entire organization](https://support.claude.com/en/articles/15537633)**.

1. Navigate to **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

2. Click “Browse connectors” at the bottom of the page.

3. Select the connector from the list and click “Add to your team.”

4. Individual users can then authenticate with the connector to start using it with Claude.

Once enabled at the org level, individual users follow the same steps described above to connect and authenticate.

**Note:** On Enterprise plans, Owners and Primary Owners can prevent services on their verified domains from being connected to Claude accounts outside the organization. Learn more about **[restricting verified-domain connectors to your enterprise](../13-Enterprise-Admin/restrict-verified-domain-connectors-to-your-enterprise.md)**.

### Restrict actions within connected services

Owners on Team and Enterprise plans can limit which actions a connected service can take across your organization. For example, you can allow a connector to read data from a service while preventing it from writing any changes back. This applies org-wide to everyone using the connector—individual users can't override it.

Common use cases:

- Allow Claude to search and summarize email, but prevent it from sending messages.

- Allow Claude to read files in Google Drive, but prevent it from creating or editing documents.

- Allow Claude to view Linear issues, but prevent it from creating new ones or changing status.

To configure action restrictions:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors).**

2. Select the connector to see **Tool permissions**.

3. The permissions will be categorized by type (for example, read-only tools, write/delete tools).

4. For each permission category or individual permission, select Always allow, Needs approval, or Blocked.

**Note:** Action restrictions work alongside source-system permissions. Even when you allow a write action in Claude, a person still needs the underlying permission in the source system to make that change. Restricting actions in Claude never grants more access than the source system permits—it only narrows it.

------------------------------------------------------------------------

## Use connected services

Once you connect to a service on Claude or Claude Desktop, it will be available to use the next time you log in to your account on Claude for iOS or Android.

Once connected, services become available in your conversations:

1. Click the “+” button in the lower left of the chat interface (you can also type “/” to open this menu).

2. Hover over “Connectors” to open the menu.

3. Enable the specific services you want Claude to use for that conversation by toggling them on.

4. Claude will now be able to use these services when relevant to your requests.

For example, after connecting Linear, you can ask Claude to "Create a new issue for the login bug" and Claude will use Linear to create the issue in your workspace.

Some connectors are interactive and can render live interfaces—like dashboards, task boards, and design tools—directly within your conversation. Look for the **Interactive** badge in the Connectors Directory to find connectors with this capability.

------------------------------------------------------------------------

## Choose how connectors load in your conversation

When you add many connectors, Claude gives you control over how they load. You can find the **Tool access** setting by clicking the “+” button in the lower left corner of your chat, or typing “/” to open the menu. Hover over “Connectors,” then “Tool access” to choose your preferred mode. For most users, **Auto** (the default) works well. If you have 10 or more connectors active, consider switching to **On demand** to give your conversations more room.

Learn more about tool access modes: **[Manage Claude's tool access](../22-Safety-Policy/manage-claude-s-tool-access.md)**.

------------------------------------------------------------------------

## Manage your connectors

To manage your connected services:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. View all your connected services in the **Connectors** section.

3. For each service, you can disconnect it, modify connection settings, or review permissions and access levels.

------------------------------------------------------------------------

## Custom connectors

Custom connectors using remote MCP are available on Claude, Cowork, and Claude Desktop for users on free, Pro, Max, Team, and Enterprise plans. Free users are limited to one custom connector.

In addition to directory connectors, you can add custom connectors:

1. Navigate to **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

2. Click the “+” button next to **Connectors**.

3. Select “Add custom connector.”

4. Enter the connector's name and URL.

5. Enter advanced settings (OAuth Client ID and secret) if desired.

6. Click “Add,” then follow the same connection process as directory connectors.

Custom connectors connect to your MCP server from Anthropic's cloud, not from your local device. Your server must be reachable over the public internet. If it's behind a firewall or on a private network, see **[Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166)** for network requirements and private network options.

**Important:** Custom connectors allow you to connect Claude to services that haven't been verified by Anthropic. Only connect to servers from trusted organizations and review authentication permissions carefully.

------------------------------------------------------------------------

## Security and privacy

All data transfers are encrypted. When using connectors, you can only sync content to Claude that you have permission to view in the original source.

Connected services process data on their own infrastructure, under their own terms, which may be located outside the United States. Settings that control where Claude's inference runs, like the US-only inference setting on Enterprise plans, don't change where third-party services operate.

When connecting to services from the directory, review what access the service is requesting during the connection process. Disconnect services you no longer need or use.

**For Team and Enterprise plans:**

- Access permissions are enforced at the user level. Users need to authenticate with the third-party service when first using the connector, even after an Owner or Primary Owner enables it.

- Connectors are only available in private projects.

- Chats with synced content can't be shared.

------------------------------------------------------------------------

## Troubleshoot connection issues

If you're having trouble connecting to a service, try these steps:

1. Check that you have a stable internet connection.

2. Verify you have an active account with the service.

3. Review any permissions or account type requirements for the service.

4. If authentication fails, try disconnecting and reconnecting from **[Customize \> Connectors](https://claude.ai/customize/connectors)**.

5. For connector-specific requirements and known issues (Slack, GitHub, Google Drive, Gmail, Google Calendar, Microsoft 365), see the connector's page in **[Claude Docs: Connectors](https://claude.com/docs/connectors/overview)**.

### See a message that says, "This corporate identity belongs to an Enterprise that manages access through their own Claude account"?

The service you're trying to connect uses an email address on a domain that an Enterprise organization has verified, and that organization restricts connections to its own Claude accounts only. To use this connection, sign in to your organization's Claude account and connect the service there. If you don't have a Claude account in that organization, contact your admin for access.

Admins can learn more about **[restricting verified-domain connectors to your Enterprise](../13-Enterprise-Admin/restrict-verified-domain-connectors-to-your-enterprise.md)**.

### Custom connector not connecting or timing out?

Custom connectors (remote MCP servers) are reached from Anthropic's cloud infrastructure, not from your local machine. This is true even if you're using Cowork or Claude Desktop, which run locally on your computer. If your MCP server is behind a corporate firewall, on a private network, or not reachable over the public internet, the connection will fail.

To resolve this, you can either allowlist Anthropic's IP ranges in your firewall to create a secure outbound-only connection from your network. For detailed guidance, see the network requirements section in **[Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166)**.

---

## Work with Claude Tag - Claude.ai Documentation

Source: https://support.claude.com/en/articles/12461605-using-claude-in-slack
Path: 14-Connectors/using-claude-in-slack.md

# Work with Claude Tag

Copy pageCopy page

Claude Tag puts Claude in your Slack channels with admin-governed access. See what to hand it, how setup works, and where to start as an admin or end user.

Copy pageCopy page

Public Beta

Tag @Claude in. Get results back in the thread.

Anyone in a Slack channel can tag Claude into a problem and hand it work: reproduce a bug and open a pull request, turn a decision thread into a doc, assemble the state of a project. It posts a checklist in the thread as it goes, and the whole exchange stays visible to the channel.

[I’m setting it up →](https://support.claude.com/docs/claude-tag/admins/setup-overview)[Use it in your channel ↓](#put-claude-tag-to-work)

\# platform-eng38 members

Dana2:14 PM

checkout has felt slow all morning — anyone else seeing it?

Leo2:15 PM

same. @Claude can you investigate? Compare latency against this morning’s deploy and find what’s causing it.

ClaudeAPP2:15 PM

On it. I’ll compare latency before and after the deploy, track down the cause, and report back here.

Done: Pulled p99 latency from DatadogDone: Diffed deploy 4f2c1 against mainDone: Reproduced the slow query locallyIn progress: Opening a pull request with the fix…

[](#plans-that-include-claude-tag)

Plans that include Claude Tag

Claude Tag is available on Team and Enterprise plans, on Anthropic’s first-party service. It isn’t available on individual plans (Free, Pro, or Max), or for third-party deployments. To use it, your organization pairs its Slack workspace with its Claude organization; see [the setup overview](https://support.claude.com/docs/claude-tag/admins/setup-overview) for the full prerequisites. If you’re choosing between Claude products for Slack-shaped work, [how Claude Tag differs from Cowork and Claude Code](https://support.claude.com/docs/claude-tag/concepts/how-it-works#how-claude-tag-differs-from-cowork-and-claude-code) compares them directly: team work in shared channels is Claude Tag; personal work on your own files is Cowork or Claude Code.

[](#who-needs-a-claude-seat)

Who needs a Claude seat

Slack users don’t each need a Claude seat to work with Claude in channels.

- **In channels**: by default, anyone in the paired Slack workspace can tag `@Claude` in a channel, and an Owner can [restrict who can use Claude](https://support.claude.com/docs/claude-tag/admins/restrict-access#restrict-who-can-use-claude) to people in your Claude organization or, on Enterprise, to specific roles. Channel work bills by usage to your organization’s usage balance, under a [spend limit](https://support.claude.com/docs/claude-tag/admins/set-spend-limit) an Owner sets.
- **In DMs**: a DM from a member who has connected a Claude account runs on that account and bills to that person’s seat. The seat must include Claude Code, or, on the Enterprise plan, be a **Standard** or **Usage-Based Chat** seat held by someone who also has Cowork. A [DM from a member who hasn’t connected a Claude account](https://support.claude.com/docs/claude-tag/admins/restrict-access#direct-messages-from-members-without-a-claude-account) can bill to your organization for a limited time.

[](#where-claude-tag-runs)

Where Claude Tag runs

Claude Tag works in Slack. You interact with it by writing in a Slack channel, thread, or direct message, and it replies there. Mention `@Claude` in a channel to guarantee it picks the message up. When Claude works on a task, it runs in an ephemeral sandbox, not on your computer. The sandbox is created when a conversation starts, holds any code or files Claude is working with, and is discarded when the conversation goes idle. See [how Claude Tag works](https://support.claude.com/docs/claude-tag/concepts/how-it-works) for the full lifecycle. You extend what Claude can reach, like your repositories, ticketing systems, data warehouses, and custom tools, through [connections](https://support.claude.com/docs/claude-tag/admins/add-connections), [plugins, and skills](https://support.claude.com/docs/claude-tag/admins/customize). An Owner configures these per scope (a channel, a workspace, or the whole organization). Members’ own claude.ai connectors are separate from that configuration; Claude can use them in a channel for the member’s own requests, as [personal connectors in channels](https://support.claude.com/docs/claude-tag/concepts/personal-connectors) describes.

[For administratorsSet up Claude Tag](https://support.claude.com/docs/claude-tag/admins/setup-overview)

[Where do I start?Pair your Slack workspace, connect the services Claude will work in, launch, and test that it works](https://support.claude.com/docs/claude-tag/admins/setup-overview)[What can Claude Tag access?How admins set access per channel, and where credentials are stored](https://support.claude.com/docs/claude-tag/concepts/agent-identity)[How do I connect each service?Credential types, allowed hosts, and what each connection lets Claude reach](https://support.claude.com/docs/claude-tag/admins/add-connections)

[For end usersPut Claude Tag to work](#put-claude-tag-to-work)

[How do I hand Claude Tag a task?Mention Claude in any channel it’s in, with nothing to install](https://support.claude.com/docs/claude-tag/users/getting-started)[What is Claude Tag good at?Use cases for coding, data, incidents, and go-to-market](https://support.claude.com/docs/claude-tag/users/use-cases)[How do I get good results?Good habits for scoping and reviewing work](https://support.claude.com/docs/claude-tag/users/good-habits)[What does Claude Tag remember?Channel memory, what’s shared across the workspace, and who can see what](https://support.claude.com/docs/claude-tag/users/memory)[Can Claude Tag run tasks on a schedule?Scheduled jobs, channel watching, and triggers](https://support.claude.com/docs/claude-tag/users/proactivity)

[](#billing-and-spend-limits)

Billing and spend limits

Adding Claude to Slack doesn’t add a per-seat charge. Channel and thread work is billed by usage instead: it draws from a **usage balance**, an amount in your organization’s billing currency that an Owner funds. A [spend limit](https://support.claude.com/docs/claude-tag/admins/set-spend-limit) caps how much of that balance Claude Tag can use each billing period. Direct messages from members who have connected a Claude account don’t draw from this balance. Such a DM runs on the sender’s own claude.ai account and follows that seat’s usual usage limits, so the organization spend limit doesn’t apply to it. A [DM from a member who hasn’t connected a Claude account](https://support.claude.com/docs/claude-tag/admins/restrict-access#direct-messages-from-members-without-a-claude-account) can draw from this balance. To learn what your team’s usage costs, run a pilot with a spend limit set and watch the per-channel breakdown on the [usage page in your admin settings](https://claude.ai/admin-settings/usage/claude-tag). Your organization may already have a [launch usage credit](https://support.claude.com/en/articles/15575654-claude-tag-launch-promo-for-claude-team-and-enterprise) to run that pilot against before it funds the balance itself. The usage page doesn’t count usage that a credit covers, so that usage shows as \$0.00 there. While the credit covers your pilot, watch the **List price** column of the **Spend by channel** table at [`claude.ai/analytics/claude-tag`](https://claude.ai/analytics/claude-tag) instead. That column shows each channel’s list-price spend for the current month, including covered usage. [Set a spend limit](https://support.claude.com/docs/claude-tag/admins/set-spend-limit) covers how to fund the balance on each plan, set the limit, and what happens when usage reaches it.

For end users

[](#put-claude-tag-to-work)

Put Claude Tag to work

If Claude Tag is in your channel, you can use it now. (If it isn’t there yet, an Owner in your Claude organization runs setup: see [Set up Claude Tag](https://support.claude.com/docs/claude-tag/admins/setup-overview).) Anyone in the channel can hand it work, and channel work bills to the organization, not to you. What it can reach starts with the channel you’re in. The fastest way to find out is to ask it: `@Claude what can you access from this channel?` Or, if you’re signed in to your Claude organization, click **Configure** in the footer of a Claude reply in the channel to see its [connections](https://support.claude.com/docs/claude-tag/concepts/glossary#connection), the external services an admin has connected for that channel. Replies in org-shared channels have no Configure link. For your own requests, Claude can also [use the connectors on your claude.ai account](https://support.claude.com/docs/claude-tag/concepts/personal-connectors), after you allow it. The one exception is a DM, where it runs on your own claude.ai account instead of the channel’s setup. Owners can disable DMs organization-wide; see [Allow or disable direct messages](https://support.claude.com/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages).

[](#common-uses)

Common uses

The list below covers common ways teams use Claude Tag. Each link opens a guide with the prompts to paste and the connections the task needs.

- [Watch monitors and alerts](https://support.claude.com/docs/claude-tag/users/use-cases/watch-monitors): scheduled dashboard checks, and alerts investigated as they arrive. Needs a monitoring connection like Datadog, Sentry, or PagerDuty.
- [Triage requests](https://support.claude.com/docs/claude-tag/users/use-cases/triage-requests): an intake channel where Claude answers what it can, flags duplicates, and routes the rest. Works on Slack content alone.
- [Find answers in your docs](https://support.claude.com/docs/claude-tag/users/use-cases/find-answers): policy and runbook questions answered with the source. Needs a docs connection like Google Drive, Notion, or Confluence.
- [Answer data questions](https://support.claude.com/docs/claude-tag/users/use-cases/answer-data-questions): a plain-language question becomes a warehouse query and a chart. Needs a data warehouse connection.
- [Track projects and chase approvals](https://support.claude.com/docs/claude-tag/users/use-cases/track-projects): standing status digests and follow-ups that run until an approval lands
- [Turn threads into docs and tickets](https://support.claude.com/docs/claude-tag/users/use-cases/create-artifacts): a settled discussion becomes the decision doc, the customer reply, or the filed tickets
- [Fix bugs](https://support.claude.com/docs/claude-tag/users/use-cases/fix-bugs): a bug reported in the channel comes back as a draft pull request. Needs GitHub.
- [Work from your own channel](https://support.claude.com/docs/claude-tag/users/use-cases/your-own-channel): scratch questions, digests of channels you don’t follow, and follow-ups on what you said you’d do

[Get started](https://support.claude.com/docs/claude-tag/users/getting-started) covers your first message, what you see while Claude works, and how to shape Claude’s behavior in your channel.

For administrators

[](#set-claude-tag-up-once-for-everyone)

Set Claude Tag up once for everyone

You set up Claude Tag once, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), and you must be an Owner in your Claude organization to do it. The setup page at that URL walks you through it:

- **Pair your Slack workspace**: send `@Claude connect` in Slack to get a pairing code, then enter it on the setup page.
- **Connect the services Claude will work in**: for each one, such as your issue tracker or data warehouse, create an account for Claude and enter its credential.
- **Grant repositories**: choose which repositories the Claude GitHub App can reach.
- **Set a monthly spend limit and launch**.

Claude Tag starts with no access to your external systems. The services you connect during setup form an [Access bundle](https://support.claude.com/docs/claude-tag/concepts/glossary#access-bundle), the set of tools Claude can reach, attached to the workspace or channels you paired. Once you launch, everyone in a channel Claude is in can use Claude Tag immediately, with no per-user setup. [Set up Claude Tag](https://support.claude.com/docs/claude-tag/admins/setup-overview) walks through those steps with what to have ready, what each choice means, and how to verify Claude Tag works once you launch.

Security review

[Security and data handling](https://support.claude.com/docs/claude-tag/concepts/security-and-data)

The security model, what admins can and can’t restrict, audit trails, and network requirements.

[](#where-to-start-with-claude-tag)

Where to start with Claude Tag

## Set up Claude Tag

Admins: pair your Slack workspace, connect the services Claude will work in, and launch

## Hand Claude Tag your first task

It’s already in your channel: send your first message

## How Claude Tag works

The session model, what it can read, and how memory follows places

## Use case library

Prompts to paste, by team and connection

---

## Use interactive connectors in Claude | Claude Help Center

Source: https://support.claude.com/en/articles/13454812-using-interactive-connectors-in-claude
Path: 14-Connectors/using-interactive-connectors-in-claude.md

# Use interactive connectors in Claude

August 11, 2026

Interactive connectors are available for all users on Claude, Cowork, Claude Desktop, and Claude for iOS/Android.

## What are interactive connectors?

Some connectors can now display live, interactive apps directly within your Claude conversations. Instead of returning text-only responses, these connectors render interfaces—like analytics dashboards, task boards, or design tools—that you can interact with without leaving the chat.

For example, you might ask Claude about your project status, and instead of just describing it, Claude opens your Asana board right in the conversation. You can check off tasks, update statuses, and keep chatting with Claude—all in one place.

Claude can also generate its own custom visuals—diagrams, charts, and simple interactive elements built from scratch for your question. When a connected service offers an interactive interface that handles your request, like an MCP app, Claude will use it. Custom visuals fill the gaps when no connector interface fits what you’re asking for.

For more on Claude-generated visuals, see **[Custom visuals in chat](https://support.claude.com/en/articles/13979539-custom-visuals-in-chat)**.

------------------------------------------------------------------------

## How interactive connectors appear

Interactive connectors display in two ways:

**Inline cards** are compact components embedded directly in the conversation. They're ideal for quick summaries, confirmations, and single actions—like a status update or a message draft ready to send.

**Fullscreen view** provides an immersive interface for complex interactions like data visualizations, document editing, or detailed project views. The conversation input remains available so you can continue talking to Claude while interacting with the connector.

## Interact with connectors

You can interact directly with elements inside the connector:

- Filter, sort, or drill into data

- Toggle settings, check boxes, or make selections

- Confirm and execute actions (mark complete, send, save)

- Expand and collapse content sections

If you need to ask Claude to modify something, refine a result, or navigate to a different context, type in the conversation input—Claude can interpret your request and update the interface accordingly.

## Which connectors are interactive?

In the **[Connectors Directory](https://claude.ai/directory)**, connectors with this capability are marked with an "Interactive” badge. Current interactive connectors include:

- **Amplitude** — View and interact with analytics dashboards

- **Asana** — Manage tasks and project boards

- **Box** — Work with documents and files

- **Canva** — Create and edit designs

- **Clay** — Manage contacts and outreach

- **Figma** — Review and annotate designs

- **Hex** — Explore data and notebooks

- **Slack** — Draft and send messages

We’re adding support for more interactive connectors over time.

## Get started with interactive connectors

1. Navigate to the **[Connectors Directory](https://claude.ai/directory)**.

2. Look for connectors marked with the "Interactive" badge.

3. Connect and authenticate with the connector.

4. Start a conversation with Claude and ask about something the connector handles—the interactive elements will appear automatically when relevant.

**Note:** Interactive connectors are default on when you have the relevant connector enabled. No additional setup is needed.

## Considerations for Team and Enterprise plans

### Can Team and Enterprise owners control interactive connectors separately from standard connectors?

Yes. Team and Enterprise owners can disable the specific tool calls that render interactive connectors within **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**. This does not disable the connector itself — text-based tool functionality continues to work normally.

------------------------------------------------------------------------

## Permissions and security

### How are interactive connectors secured?

Interactive connectors run in sandboxed iframes with strict Content Security Policies. All communication between the interface and Claude uses auditable JSON-RPC messaging. Servers must predeclare which external domains they need, and the host can review HTML content before rendering.

### Do interactive connectors require additional permissions beyond the connector itself?

No. Interactive connectors use the same permissions you granted when connecting the tool. They don't request additional access to your data.

### Can interactive connectors make purchases or financial transactions?

No. Purchases through third-party interactive connectors are not supported.

------------------------------------------------------------------------

## Troubleshooting

### The interface isn't appearing

- Check that the connector is connected and enabled for your current conversation.

- Try starting a new conversation and asking Claude a question that the connector handles.

### The connector isn't responding to interactions

- Check your internet connection.

- Try refreshing the page or restarting Claude Desktop.

- If the issue persists, disconnect and reconnect the connector in **[Settings \> Connectors](https://claude.ai/settings/connectors)**.

### I want to disable interactive connectors

- **Team and Enterprise users:** Ask your organization owner to disable the relevant tool calls in **[Organization settings \> Connectors](https://claude.ai/admin-settings/connectors)**.

- **Individual users:** You can disable specific connector tools via the "Search and tools" menu in your conversation.

------------------------------------------------------------------------

## I'm a developer. Where can I learn about building MCP Apps?

MCP Apps is the open-source extension to the Model Context Protocol that powers interactive apps. If you are building your own interactive connector, note that it must meet additional design, security, and testing requirements. For details, see **[Submitting to the Connectors Directory](https://claude.com/docs/connectors/building/submission)** on Claude Docs.

---

## Using Research and Google Workspace | Claude by Anthropic

Source: https://support.claude.com/en/articles/11101545-using-research-and-google-workspace
Path: 14-Connectors/using-research-and-google-workspace.md

# Using Research and Google Workspace

Learn how to leverage Claude's Research capabilities alongside Google Workspace integrations to access emails, calendar data, documents, and web information for comprehensive analysis.

Professional

Claude.ai

Watch time

min

[Copy link](#)
https://claude.com/resources/tutorials/using-research-and-google-workspace

## Related tutorials

[How to choose between voice mode and dictation](https://support.claude.com/resources/tutorials/how-to-choose-between-voice-mode-and-dictation)

How to choose between voice mode and dictation

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/how-to-choose-between-voice-mode-and-dictation)

Tutorial

[Delegating and scheduling tasks in Claude Cowork](https://support.claude.com/resources/tutorials/delegating-and-scheduling-tasks-in-claude-cowork)

Delegating and scheduling tasks in Claude Cowork

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/delegating-and-scheduling-tasks-in-claude-cowork)

Tutorial

[Tasks to try with @Claude in your workspace](https://support.claude.com/resources/tutorials/tasks-to-try-with-claude-tag-in-your-workspace)

Tasks to try with @Claude in your workspace

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/tasks-to-try-with-claude-tag-in-your-workspace)

Tutorial

[Best practices for using @Claude](https://support.claude.com/resources/tutorials/best-practices-using-claude-tag)

Best practices for using @Claude

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/best-practices-using-claude-tag)

Tutorial

[Homepage](https://claude.com)

Homepage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Write

[Button Text](#)

Button Text

Learn

[Button Text](#)

Button Text

Code

[Button Text](#)

Button Text

Write

- Help me develop a unique voice for an audience

- Improve my writing style

- Brainstorm creative ideas

Learn

- Explain a complex topic simply

- Help me make sense of these ideas

- Prepare for an exam or interview

Code

- Explain a programming concept

- Look over my code and give me tips

- Vibe code with me

- Write case studies

This is another test

- Write grant proposals

- Write video scripts

this is a test

[Anthropic](https://www.anthropic.com/)

Anthropic

Products

- Claude

[Claude](https://support.claude.com/product/overview)
Claude

- Claude Code

[Claude Code](https://support.claude.com/product/claude-code)
Claude Code

- Claude Code for Enterprise

[Claude Code for Enterprise](https://support.claude.com/product/claude-code/enterprise)
Claude Code for Enterprise

- Claude Cowork

[Claude Cowork](https://support.claude.com/product/cowork)
Claude Cowork

- @Claude

[@Claude](https://support.claude.com/product/tag)
@Claude

- Claude Design

[Claude Design](https://support.claude.com/product/design)
Claude Design

- Claude Science

[Claude Science](https://support.claude.com/product/claude-science)
Claude Science

- Claude Security

[Claude Security](https://support.claude.com/product/claude-security)
Claude Security

- Download app

[Download app](https://support.claude.com/download)
Download app

- Pricing

[Pricing](https://support.claude.com/pricing)
Pricing

- Log in

[Log in](https://claude.ai/login)

Features

- Claude in Chrome

[Claude in Chrome](https://support.claude.com/claude-in-chrome)
Claude in Chrome

- Claude for Microsoft 365

[Claude for Microsoft 365](https://support.claude.com/claude-for-microsoft-365)
Claude for Microsoft 365

- Skills

[Skills](https://support.claude.com/skills)
Skills

Models

- Mythos

[Mythos](../15-Claude-AI-Features/claude-mythos.md)
Mythos

- Fable

[Fable](../15-Claude-AI-Features/claude-fable.md)
Fable

- Opus

[Opus](https://support.claude.com/en/15-Claude-AI-Features/claude-opus-4-6-anthropic.md)
Opus

- Sonnet

[Sonnet](https://support.claude.com/en/15-Claude-AI-Features/claude-sonnet-4-6-anthropic.md)
Sonnet

- Haiku

[Haiku](https://support.claude.com/en/15-Claude-AI-Features/claude-haiku-4-5-anthropic.md)
Haiku

Solutions

- AI agents

[AI agents](https://support.claude.com/solutions/agents)
AI agents

- Code modernization

[Code modernization](https://support.claude.com/solutions/code-modernization)
Code modernization

- Coding

[Coding](https://support.claude.com/solutions/coding)
Coding

- Customer support

[Customer support](https://support.claude.com/solutions/customer-support)
Customer support

- Cybersecurity

[Cybersecurity](https://support.claude.com/solutions/cybersecurity)
Cybersecurity

- Enterprise

[Enterprise](https://support.claude.com/solutions/enterprise)
Enterprise

- Financial services

[Financial services](https://support.claude.com/solutions/financial-services)
Financial services

- Government

[Government](https://support.claude.com/solutions/government)
Government

- Healthcare

[Healthcare](https://support.claude.com/solutions/healthcare)
Healthcare

- Higher education

[Higher education](https://support.claude.com/solutions/education)
Higher education

- K-12 teachers

[K-12 teachers](https://support.claude.com/solutions/teachers)
K-12 teachers

- Legal

[Legal](https://support.claude.com/solutions/legal)
Legal

- Life sciences

[Life sciences](https://support.claude.com/solutions/life-sciences)
Life sciences

- Nonprofits

[Nonprofits](https://support.claude.com/solutions/nonprofits)
Nonprofits

- Small business

[Small business](https://support.claude.com/solutions/small-business)
Small business

Claude Platform

- Overview

[Overview](https://support.claude.com/platform/api)
Overview

- Developer docs

[Developer docs](../04-API-Reference/Other/home.md)
Developer docs

- Pricing

[Pricing](../17-Billing-Plans/pricing.md#api)
Pricing

- Ecosystem

[Ecosystem](https://support.claude.com/ecosystem)
Ecosystem

- Marketplace

[Marketplace](https://support.claude.com/platform/marketplace)
Marketplace

- Claude on AWS

[Claude on AWS](https://support.claude.com/partners/claude-on-aws)
Claude on AWS

- Google Cloud

[Google Cloud](https://support.claude.com/partners/google-cloud)
Google Cloud

- Microsoft Foundry

[Microsoft Foundry](https://support.claude.com/partners/microsoft-foundry)
Microsoft Foundry

- Regional compliance

[Regional compliance](https://support.claude.com/regional-compliance)
Regional compliance

- Console login

[Console login](../04-API-Reference/Other/usage-limits.md)
Console login

Resources

- Blog

[Blog](https://support.claude.com/blog)
Blog

- Claude partner network

[Claude partner network](https://support.claude.com/partners)
Claude partner network

- Community

[Community](https://support.claude.com/community)
Community

- Connectors

[Connectors](https://support.claude.com/connectors)
Connectors

- Courses

[Courses](https://www.anthropic.com/learn)
Courses

- Customer stories

[Customer stories](https://support.claude.com/customers)
Customer stories

- Engineering at Anthropic

[Engineering at Anthropic](https://www.anthropic.com/engineering)
Engineering at Anthropic

- Events

[Events](https://www.anthropic.com/events)
Events

- Plugins

[Plugins](https://support.claude.com/plugins)
Plugins

- Powered by Claude

[Powered by Claude](https://support.claude.com/partners/powered-by-claude)
Powered by Claude

- Service partners

[Service partners](#)
Service partners

- Tutorials

[Tutorials](https://support.claude.com/resources/tutorials)
Tutorials

- Use cases

[Use cases](https://support.claude.com/resources/use-cases)
Use cases

Company

- Anthropic

[Anthropic](https://www.anthropic.com/)
Anthropic

- Careers

[Careers](https://www.anthropic.com/careers)
Careers

- Policy

[Policy](https://www.anthropic.com/policy)
Policy

- Economic Futures

[Economic Futures](https://www.anthropic.com/economic-futures)
Economic Futures

- Research

[Research](../19-Reference/anthropic-com-research.md)
Research

- News

[News](../19-Reference/news.md)
News

- Policy on the AI Exponential

---

## Claude Help Center

Source: https://support.claude.com/en/articles/12614810-using-the-benchling-connector-in-claude
Path: 14-Connectors/using-the-benchling-extension-in-claude.md

# Search for answers or browse by topic

Search for articles...

Uh oh. That page doesn’t exist.

Try searching for your answer or just send us a message.

---

## Using the Benevity connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12923227-using-the-benevity-connector-in-claude
Path: 14-Connectors/using-the-benevity-connector-in-claude.md

# Using the Benevity connector in Claude

Connect Claude to Benevity's database of 2.5M+ nonprofits to discover and research charitable organizations.

9 minClaude.ai

[Open Claude](https://claude.ai/new)

The Benevity connector gives Claude access to a database of 2.5M+ nonprofit organizations. Search by cause, location, or keyword, and get detailed profiles including mission statements, program descriptions, and geographic focus.

The Benevity integration relies on Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/use-connectors-to-extend-claude-s-capabilities-d041e8447b.md).

## What this connector provides[](#what-this-connector-provides)

- Access to 2.5M+ nonprofit organizations
- Detailed profiles including mission statements, program descriptions, and geographic focus
- Keyword search for local and international organizations
- Direct website links to organizations

## Who can use this[](#who-can-use-this)

Available to all paid Claude plan users (Pro, Max, Team, or Enterprise). No Benevity account or authentication is required.

## Setting up the connector[](#setting-up-the-connector)

### For organization owners (Team and Enterprise)[](#for-organization-owners-team-and-enterprise)

1. Navigate to [Admin settings(opens in new tab)](https://claude.ai/admin-settings) \> Connectors
2. Select `Browse connectors`
3. Find and select Benevity
4. Select `Add to your team`

### For individual users[](#for-individual-users)

1. Navigate to [Settings(opens in new tab)](https://claude.ai/settings) \> Connectors
2. Select `Browse connectors`
3. Find and select Benevity
4. Follow the instructions to enable

## Example use cases[](#example-use-cases)

**Interest-based discovery:**

Find nonprofits working on ocean conservation in the Pacific Northwest



Open in Claude

**Local charity research:**

What community organizations serve homeless populations in Denver?



Open in Claude

**Pre-donation research:**

Tell me about the mission and programs of \[organization name\]



Open in Claude

**Corporate giving:**

Find verified nonprofits focused on STEM education for workplace giving programs



Open in Claude

## Frequently asked questions[](#frequently-asked-questions)

### Does it cost extra?[](#does-it-cost-extra)

No. The integration is free for all paid Claude plans. No separate Benevity account is needed.

### Can I donate through Claude?[](#can-i-donate-through-claude)

The connector supports research only. To donate, visit the nonprofit's website directly.

### How current is the data?[](#how-current-is-the-data)

Claude accesses Benevity's database in real time. Organization profiles are updated regularly.

### Does it include international organizations?[](#does-it-include-international-organizations)

Yes. The database includes nonprofit organizations worldwide.

---

## Using the BioRender Connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12614795-using-the-biorender-connector-in-claude
Path: 14-Connectors/using-the-biorender-connector-in-claude.md

# Using the BioRender Connector in Claude

Set up and use the BioRender integration with Claude to search scientific figure templates and icon collections.

9 minClaude.ai

[Open Claude](https://claude.ai/new)

The BioRender integration searches BioRender’s extensive scientific figure template and icon collection for relevant content to create figures faster. This article explains how to set up and use the BioRender integration with Claude to accelerate scientific content creation.

The BioRender integration relies upon Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities).

## What this integration provides[](#what-this-integration-provides)

This integration allows you to search BioRender’s extensive library of vetted scientific figures to quickly find scientifically-accurate content for your presentations, posters, grant proposal figures, journal graphical abstracts and more. Simply describe your needs and receive recommended scientific icons, figures and templates in return.

This integration provides access to BioRender’s scientific Icons and Template, which includes:

- 50,000+ verified scientific icons across all fields of life sciences
- Professionally designed figure templates for meetings, presentations, research posters, grant applications, publications, patience material, internal workflows, etc.
- Regularly updated visual assets curated by world class medical illustrators

## Who can access the BioRender integration[](#who-can-access-the-biorender-integration)

- The BioRender integration is available to all BioRender users with an active account.
- Users must log in using their BioRender credentials to authenticate the connection.
- Once connected, they can search BioRender’s scientific icon and template library directly.
- Access to specific icons and templates will depend on the user’s subscription tier:
- Free and Individual Plans - Access to a limited set of icons and templates
- Premium and Team Plans - Access to the full BioRender library, including advanced templates and specialized scientific content
- No additional licensing or set up fees are required to access the BioRender integration

More details on accessing the integration can be found in [BioRender’s MCP Server Documentation(opens in new tab)](https://help.biorender.com/hc/en-gb/articles/30870978672157-How-to-use-the-BioRender-MCP-connector).

## Setting up the BioRender integration[](#setting-up-the-biorender-integration)

**For Organization Owners (Team and Enterprise)**

1. Navigate to Admin settings \> Connectors
2. Click "Browse connectors"
3. Click “**BioRender**”
4. Click “Add to your team”

**For Individual Claude Users**

1. Navigate to Settings \> Connectors
2. Click “Connect”
3. Follow the instructions to authenticate with your BioRender account

Learn about [finding and connecting tools(opens in new tab)](browse-skills-connectors-and-plugins-in-one-directory.md) in Claude.

**For Claude Code Users**

1. Command: `/plugin marketplace add anthropics/life-sciences`
2. Command: `/plugin install biorender@life-sciences`
3. Restart Claude Code
4. Verify that the server is connected with `/mcp`

Technical details of the BioRender integration can be found in [BioRender’s MCP Server Documentation(opens in new tab)](https://help.biorender.com/hc/en-gb/articles/30870978672157-How-to-use-the-BioRender-MCP-connector).

## Common use cases[](#common-use-cases)

- **Grant proposal figures** - describe your research or experimental design and get relevant template and icon suggestions to create clear proposal figures for reviewers

I'm working on a figure for a grant proposal about chimeric CAR T cell therapy targeting solid tumors. I need two panels: 1. T cells engineered with chimeric antigen receptors 2. CAR T cells mediate cancer cell death. Can you help me find templates that show CAR T cells receptors and CAR T cells trafficking and targeting cancer cells?



Open in Claude

- **Journal figures & graphical abstracts** - use the text of your paper’s key findings to get template and icon suggestions for creating publication visuals

I need to create a graphical abstract about CRISPR-Cas9 gene editing in plant cells. I want to show the Cas9 protein, guide RNA, DNA double-strand break, and the DNA repair process. Can you find me templates for CRISPR mechanisms and plant cell structures?



Open in Claude

- **Presentations for conferences & internal lab meetings** - describe your experimental workflow or steps to get icon and template recommendations for use in internal lab teams meetings and for creating presentations and posters for use at conferences

I need to explain the experimental workflow for protein crystallization during a presentation. Can you find templates showing the process, including protein expression and purification, protein crystallization, and X-ray diffraction?



Open in Claude

- [What this integration provides](#what-this-integration-provides)
- [Who can access the BioRender integration](#who-can-access-the-biorender-integration)
- [Setting up the BioRender integration](#setting-up-the-biorender-integration)
- [Common use cases](#common-use-cases)

---

## Using the Blackbaud connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12923221-using-the-blackbaud-connector-in-claude
Path: 14-Connectors/using-the-blackbaud-connector-in-claude.md

# Using the Blackbaud connector in Claude

Connect Claude to Raiser's Edge NXT to access donor records, gift history, events, and draft personalized communications.

10 minClaude.ai

[Open Claude](https://claude.ai/new)

The Blackbaud connector gives Claude secure access to your Raiser's Edge NXT fundraising data. Look up donor profiles, review gift history, search events, and draft personalized communications through natural language.

The Blackbaud integration relies on Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/use-connectors-to-extend-claude-s-capabilities-d041e8447b.md).

## What this connector provides[](#what-this-connector-provides)

- **Constituent profiles:** Access detailed donor records including contact information, affiliations, and giving history
- **Constituent search:** Search donors by full or partial name across your database
- **Event discovery:** Search fundraising events by name or keyword and retrieve details like dates, locations, and funds raised
- **Gift records:** View donation amounts, dates, donors, and associated campaigns
- **Communications:** Draft personalized thank-you notes and donor outreach referencing specific gifts
- **Real-time data:** Fetch current information directly from Raiser's Edge NXT

## Setting up the connector[](#setting-up-the-connector)

### For Blackbaud marketplace admins[](#for-blackbaud-marketplace-admins)

1. Navigate to the Claude for Blackbaud app in the Blackbaud Marketplace
2. Connect to your Blackbaud environment
3. Approve scopes for constituent and event data access

### For organization owners[](#for-organization-owners)

1. Go to [Claude.ai Settings(opens in new tab)](https://claude.ai/settings)
2. Select Connectors or Integrations
3. Choose `Add server` or `Browse connectors`
4. Search for and select Blackbaud
5. Select `Add to your team`
6. Confirm authorization

### For individual users[](#for-individual-users)

1. Log in to Claude with your enterprise account
2. Access [Settings(opens in new tab)](https://claude.ai/settings) \> Connectors
3. Select the Blackbaud connector and authorize
4. Sign in with your Blackbaud ID and grant permissions
5. Your account displays as "Linked" when complete

## Common use cases[](#common-use-cases)

### Donor lookup[](#donor-lookup)

Show me the profile for Jane Smith, including her contact information and recent donations.



Open in Claude

*When to use: Preparing for donor meetings, reviewing relationships, verifying contact details.*

### Gift history analysis[](#gift-history-analysis)

What are the details of John Doe's donations over the past year? Include amounts, dates, and campaigns.



Open in Claude

*When to use: Reviewing engagement, preparing acknowledgments, analyzing patterns. Works well with 1–3 year timeframes.*

### Event research[](#event-research)

Find any events titled 'Annual Gala' and show details including attendance and funds raised.



Open in Claude

*When to use: Planning future events, comparing performance, researching past activities.*

### Thank-you letter drafting[](#thank-you-letter-drafting)

Draft a personalized thank-you email to Sarah Johnson for her recent \$500 donation to the Building Fund campaign.



Open in Claude

*When to use: Following up on donations, acknowledging major gifts. Claude retrieves donor info and gift details for personalized communications.*

### Constituent search[](#constituent-search)

Find all constituents named Williams in our database.



Open in Claude

*When to use: Locating donors with partial names, finding family members.*

## Tips for using the connector[](#tips-for-using-the-connector)

- Use full donor names for accurate constituent lookups
- Specify time periods in gift history requests
- Ask naturally, as if asking a colleague
- Combine multiple requests when helpful
- Review AI-generated communications before sending, especially with sensitive donor data
- Claude only accesses data your Blackbaud account authorizes

- [What this connector provides](#what-this-connector-provides)
- [Setting up the connector](#setting-up-the-connector)
- [Common use cases](#common-use-cases)
- [Tips for using the connector](#tips-for-using-the-connector)

---

## Using the Candid connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12923235-using-the-candid-connector-in-claude
Path: 14-Connectors/using-the-candid-connector-in-claude.md

# Using the Candid connector in Claude

Connect Claude to Candid's database of 1.9M+ nonprofits and foundations for organizational research, grant discovery, and sector analysis.

10 minClaude.ai

[Open Claude](https://claude.ai/new)

The Candid connector gives Claude access to comprehensive nonprofit and philanthropic data, including 1.9M+ nonprofits and foundations, expert knowledge resources, and the Philanthropy Classification System taxonomy.

The Candid integration relies on Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/use-connectors-to-extend-claude-s-capabilities-d041e8447b.md).

*Note: This connector is currently in beta with core functionality available.*

## What this connector provides[](#what-this-connector-provides)

- **Search organizations:** Find nonprofits and foundations by name, mission, location, work area, transparency seal, or leadership demographics (women, BIPOC, LGBTQ+, people with disabilities)
- **Find mentioned organizations:** Automatically identifies organization names in conversation and links them to official Candid profiles
- **Knowledge search:** Access Candid's expert knowledge base including research reports, training materials, blog posts, and curated daily news
- **Find relevant taxonomic terms:** Uses AI to identify relevant terms from Candid's Philanthropy Classification System based on your descriptions

## Who can use this[](#who-can-use-this)

Available to all paid Claude plan users. Basic search requires no separate Candid account, though some advanced features may require additional authentication.

## Setting up the connector[](#setting-up-the-connector)

### For organization owners (Team and Enterprise)[](#for-organization-owners-team-and-enterprise)

1. Navigate to [Admin settings(opens in new tab)](https://claude.ai/admin-settings) \> Connectors
2. Select `Browse connectors`
3. Search and select Candid
4. Select `Add to your team`

### For individual users[](#for-individual-users)

1. Navigate to [Settings(opens in new tab)](https://claude.ai/settings) \> Connectors
2. Select `Browse connectors`
3. Search and select Candid
4. Follow the instructions to enable

## Example use cases[](#example-use-cases)

### Finding local organizations[](#finding-local-organizations)

Find foundations in California that fund youth education programs.



Open in Claude

Claude searches with location and subject filters, returning matching foundations with Candid profile links, mission focus, and transparency seal details.

### Researching sector trends[](#researching-sector-trends)

What are the latest trends in climate philanthropy?



Open in Claude

Claude searches Candid's knowledge base for recent articles and research, links mentioned organizations, and synthesizes findings.

### Finding by mission and criteria[](#finding-by-mission-and-criteria)

Find nonprofits working on food access in Seattle that are highly transparent.



Open in Claude

Claude identifies the geographic area, relevant taxonomy terms, and filters by location, subject, and transparency seals.

### Learning resources[](#learning-resources)

I'm new to grant writing. What are best practices?



Open in Claude

Claude searches Candid's learning and help sources for expert guidance, training materials, and relevant articles.

## Tips for best results[](#tips-for-best-results)

### Be specific with locations[](#be-specific-with-locations)

- [x] `nonprofits in Brooklyn, New York`
- [x] `foundations serving rural Montana communities`
- ✗ `organizations in the Northeast` (too broad)

### Describe work, not just keywords[](#describe-work-not-just-keywords)

- [x] `organizations helping homeless youth find permanent housing`
- [x] `funders supporting immigrant and refugee integration programs`

### Combine multiple filters[](#combine-multiple-filters)

- `Environmental organizations in California with BIPOC leadership`
- `Healthcare nonprofits in Texas with Platinum transparency seals`

### Ask follow-up questions[](#ask-follow-up-questions)

- `Tell me more about [organization name]`
- `Are there similar organizations in other states?`

## Understanding seals of transparency[](#understanding-seals-of-transparency)

- **Platinum:** Most comprehensive information including impact metrics
- **Gold:** Detailed financials and demographics
- **Silver:** Program information and organizational details
- **Bronze:** Basic core organization information

## Frequently asked questions[](#frequently-asked-questions)

### Does it cost extra?[](#does-it-cost-extra)

Basic search is free for all paid Claude plans. Advanced features may require additional authentication.

### How current is the data?[](#how-current-is-the-data)

Organization data is updated regularly from IRS filings, official registrations, and direct input. The knowledge base and news feed are updated continuously.

### Does it include international organizations?[](#does-it-include-international-organizations)

Candid has the most comprehensive coverage of US organizations, particularly IRS-registered 501(c)(3) organizations and US grantmaking foundations.

### Can't find a specific organization?[](#cant-find-a-specific-organization)

Try searching by EIN, alternate names or acronyms, or broadening your search terms. Coverage is strongest for US-registered nonprofits.

## Privacy and data usage[](#privacy-and-data-usage)

- The connector accesses publicly available nonprofit information only
- No personal user data is shared with Candid
- Search queries are used only to retrieve relevant results

For Candid-specific questions, email [partnerships@candid.org(opens in new tab)](mailto:partnerships@candid.org).

- [What this connector provides](#what-this-connector-provides)
- [Who can use this](#who-can-use-this)
- [Setting up the connector](#setting-up-the-connector)
- [Example use cases](#example-use-cases)
- [Tips for best results](#tips-for-best-results)
- [Understanding seals of transparency](#understanding-seals-of-transparency)
- [Frequently asked questions](#frequently-asked-questions)
- [Privacy and data usage](#privacy-and-data-usage)

---

## Use the GitHub integration | Claude Help Center

Source: https://support.claude.com/en/articles/10167454-using-the-github-integration
Path: 14-Connectors/using-the-github-integration.md

# Use the GitHub integration

For more information on enabling GitHub within your account, see **[Use connectors to extend Claude's capabilities](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities)**.

Connect your GitHub repositories directly to Claude to provide comprehensive context for your software development tasks. You can easily add repositories by selecting them from a list, helping Claude better understand and assist with your codebase.

## How to add GitHub repositories

**Note:** If you're currently unauthenticated with GitHub, you'll be redirected to GitHub to authenticate before you can use this integration.

### Chats

1. Click the "+" button on the lower left corner of the chat interface.

2. Select "Add from GitHub" from the drop-down.

3. Use the file browser to select specific files and folders.

4. When you send your message, Claude will access and process the content to inform its response.

### Projects

1. Click the "+" button in the upper right corner of your project knowledge section.

2. Select "GitHub" from the drop-down.

3. Search through your accessible repositories, or paste a repository URL.

4. Use the file browser to select specific files and folders.

5. Your selected content will be added to the project knowledge for Claude to access and process.

6. You can use the "Sync" icon to ensure you're working with the most up-to-date version of your codebase.

7. You can use the "Configure files" icon to modify which files and folders Claude analyzes.

## Connect to private repositories

- **If Claude cannot access a repository after you enter a valid URL, it most likely means you're attempting to connect Claude to a private repository**: Follow the link to our GitHub App, where you can grant access to repos if you're a GitHub administrator, or send a request to your GitHub organization's administrators.

- **Grant access yourself if you can**: You can choose between letting Claude access all repos or specific ones.

- **Request access if you don't have the necessary permissions**: The administrators of your GitHub organization will receive an email notification about your request. Once they approve the request, you'll be able to sync and access the repository in Claude.

------------------------------------------------------------------------

## Best practices

1. **Start small**: Begin by selecting a small subset of your codebase to analyze. This will help you get familiar with how Claude interprets and discusses your code.

2. **Iterate and refine**: If Claude's initial response doesn't fully address your question, don't hesitate to ask follow-up questions or request clarification.

3. **Combine with human expertise**: Use Claude's insights as a starting point for further investigation and discussion with your team. Please review Claude's work.

4. **Thoughtful file selection**: When using "Configure files," be strategic about your selections. Include key files and directories that are central to your current task or project, but avoid selecting unnecessary files to keep within token limits and maintain focus.

5. **Regular updates**: Remember to refresh your project's GitHub sync periodically to ensure Claude is working with the most up-to-date version of your codebase and especially before starting a new analysis or when you know there have been significant changes to your repo.

------------------------------------------------------------------------

## Troubleshooting

### Repositories from an organization don't appear after connecting

If your GitHub connection shows as connected but private repositories from a specific organization don't appear, that organization may require single sign-on (SSO). When SSO is required, each user must separately authorize the Claude app for that organization. Until you do, GitHub filters that organization's private repositories from your view, even though your connection is otherwise working.

When Claude detects this state, the repository picker shows a banner prompting you to authorize SSO. To authorize the Claude app for your organization:

1. Go to **[github.com/settings/applications](https://github.com/settings/applications)** and open the **Claude** entry.

2. Under **Organization access**, click "Grant" next to the relevant GitHub organization.

3. If the button reads "Request" instead of "Grant," you don't have permission to authorize the app yourself. A GitHub organization admin must approve your request from the organization's OAuth application policy settings.

**Important:** Disconnecting and reconnecting GitHub in your Claude settings won't fix this. A fresh connection doesn't automatically authorize organizations that require SSO, so you'll need to complete the authorization steps above.

If your organization uses GitHub Enterprise Cloud with Enterprise Managed Users (EMU), connect GitHub while you're signed in with your managed account and have an active SSO session. An organization owner can check the Claude app under Settings \> Third-party Access \> GitHub Apps in your GitHub organization, and confirm that it has access to the repositories you need and has no pending permission requests.

------------------------------------------------------------------------

## Frequently asked questions

### What information is retrieved from GitHub?

Only files (names and contents) in a repo on a specific branch are synced. We do not retrieve commit history, PRs, or other metadata.

### What happens if my repository is updated after adding it to a project?

You can click "Sync now" to fetch the latest changes from your repository. This will update all previously selected files and folders.

### Can I add multiple repositories to a single project or chat?

Yes, you can add multiple repositories to provide Claude with comprehensive context for your development tasks. The repositories must fit within Claude's context window.

### What happens if I lose access to a repository?

If you lose access to a repository, you won't be able to view its contents in projects where it was previously added. The repository preview will be removed, though the conversation history will be maintained.

Browse all available connectors in the **[Connectors Directory](https://claude.ai/directory)**.

---

## Using the Google Docs integration | Claude by Anthropic

Source: https://support.claude.com/en/articles/10389539-using-the-google-docs-integration
Path: 14-Connectors/using-the-google-docs-integration.md

# Using the Google Docs integration

Learn how to connect and use the Google Docs integration to seamlessly incorporate your documents into conversations with Claude.

Professional

Claude.ai

Watch time

min

[Copy link](#)
https://claude.com/resources/tutorials/using-the-google-docs-integration

## Related tutorials

[How to choose between voice mode and dictation](https://support.claude.com/resources/tutorials/how-to-choose-between-voice-mode-and-dictation)

How to choose between voice mode and dictation

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/how-to-choose-between-voice-mode-and-dictation)

Tutorial

[Delegating and scheduling tasks in Claude Cowork](https://support.claude.com/resources/tutorials/delegating-and-scheduling-tasks-in-claude-cowork)

Delegating and scheduling tasks in Claude Cowork

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/delegating-and-scheduling-tasks-in-claude-cowork)

Tutorial

[Tasks to try with @Claude in your workspace](https://support.claude.com/resources/tutorials/tasks-to-try-with-claude-tag-in-your-workspace)

Tasks to try with @Claude in your workspace

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/tasks-to-try-with-claude-tag-in-your-workspace)

Tutorial

[Best practices for using @Claude](https://support.claude.com/resources/tutorials/best-practices-using-claude-tag)

Best practices for using @Claude

Tutorial

[Tutorial](https://support.claude.com/resources/tutorials/best-practices-using-claude-tag)

Tutorial

[Homepage](https://claude.com)

Homepage

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Write

[Button Text](#)

Button Text

Learn

[Button Text](#)

Button Text

Code

[Button Text](#)

Button Text

Write

- Help me develop a unique voice for an audience

- Improve my writing style

- Brainstorm creative ideas

Learn

- Explain a complex topic simply

- Help me make sense of these ideas

- Prepare for an exam or interview

Code

- Explain a programming concept

- Look over my code and give me tips

- Vibe code with me

- Write case studies

This is another test

- Write grant proposals

- Write video scripts

this is a test

[Anthropic](https://www.anthropic.com/)

Anthropic

Products

- Claude

[Claude](https://support.claude.com/product/overview)
Claude

- Claude Code

[Claude Code](https://support.claude.com/product/claude-code)
Claude Code

- Claude Code for Enterprise

[Claude Code for Enterprise](https://support.claude.com/product/claude-code/enterprise)
Claude Code for Enterprise

- Claude Cowork

[Claude Cowork](https://support.claude.com/product/cowork)
Claude Cowork

- @Claude

[@Claude](https://support.claude.com/product/tag)
@Claude

- Claude Design

[Claude Design](https://support.claude.com/product/design)
Claude Design

- Claude Science

[Claude Science](https://support.claude.com/product/claude-science)
Claude Science

- Claude Security

[Claude Security](https://support.claude.com/product/claude-security)
Claude Security

- Download app

[Download app](https://support.claude.com/download)
Download app

- Pricing

[Pricing](https://support.claude.com/pricing)
Pricing

- Log in

[Log in](https://claude.ai/login)

Features

- Claude in Chrome

[Claude in Chrome](https://support.claude.com/claude-in-chrome)
Claude in Chrome

- Claude for Microsoft 365

[Claude for Microsoft 365](https://support.claude.com/claude-for-microsoft-365)
Claude for Microsoft 365

- Skills

[Skills](https://support.claude.com/skills)
Skills

Models

- Mythos

[Mythos](../15-Claude-AI-Features/claude-mythos.md)
Mythos

- Fable

[Fable](../15-Claude-AI-Features/claude-fable.md)
Fable

- Opus

[Opus](https://support.claude.com/en/15-Claude-AI-Features/claude-opus-4-6-anthropic.md)
Opus

- Sonnet

[Sonnet](https://support.claude.com/en/15-Claude-AI-Features/claude-sonnet-4-6-anthropic.md)
Sonnet

- Haiku

[Haiku](https://support.claude.com/en/15-Claude-AI-Features/claude-haiku-4-5-anthropic.md)
Haiku

Solutions

- AI agents

[AI agents](https://support.claude.com/solutions/agents)
AI agents

- Code modernization

[Code modernization](https://support.claude.com/solutions/code-modernization)
Code modernization

- Coding

[Coding](https://support.claude.com/solutions/coding)
Coding

- Customer support

[Customer support](https://support.claude.com/solutions/customer-support)
Customer support

- Cybersecurity

[Cybersecurity](https://support.claude.com/solutions/cybersecurity)
Cybersecurity

- Enterprise

[Enterprise](https://support.claude.com/solutions/enterprise)
Enterprise

- Financial services

[Financial services](https://support.claude.com/solutions/financial-services)
Financial services

- Government

[Government](https://support.claude.com/solutions/government)
Government

- Healthcare

[Healthcare](https://support.claude.com/solutions/healthcare)
Healthcare

- Higher education

[Higher education](https://support.claude.com/solutions/education)
Higher education

- K-12 teachers

[K-12 teachers](https://support.claude.com/solutions/teachers)
K-12 teachers

- Legal

[Legal](https://support.claude.com/solutions/legal)
Legal

- Life sciences

[Life sciences](https://support.claude.com/solutions/life-sciences)
Life sciences

- Nonprofits

[Nonprofits](https://support.claude.com/solutions/nonprofits)
Nonprofits

- Small business

[Small business](https://support.claude.com/solutions/small-business)
Small business

Claude Platform

- Overview

[Overview](https://support.claude.com/platform/api)
Overview

- Developer docs

[Developer docs](../04-API-Reference/Other/home.md)
Developer docs

- Pricing

[Pricing](../17-Billing-Plans/pricing.md#api)
Pricing

- Ecosystem

[Ecosystem](https://support.claude.com/ecosystem)
Ecosystem

- Marketplace

[Marketplace](https://support.claude.com/platform/marketplace)
Marketplace

- Claude on AWS

[Claude on AWS](https://support.claude.com/partners/claude-on-aws)
Claude on AWS

- Google Cloud

[Google Cloud](https://support.claude.com/partners/google-cloud)
Google Cloud

- Microsoft Foundry

[Microsoft Foundry](https://support.claude.com/partners/microsoft-foundry)
Microsoft Foundry

- Regional compliance

[Regional compliance](https://support.claude.com/regional-compliance)
Regional compliance

- Console login

[Console login](../04-API-Reference/Other/usage-limits.md)
Console login

Resources

- Blog

[Blog](https://support.claude.com/blog)
Blog

- Claude partner network

[Claude partner network](https://support.claude.com/partners)
Claude partner network

- Community

[Community](https://support.claude.com/community)
Community

- Connectors

[Connectors](https://support.claude.com/connectors)
Connectors

- Courses

[Courses](https://www.anthropic.com/learn)
Courses

- Customer stories

[Customer stories](https://support.claude.com/customers)
Customer stories

- Engineering at Anthropic

[Engineering at Anthropic](https://www.anthropic.com/engineering)
Engineering at Anthropic

- Events

[Events](https://www.anthropic.com/events)
Events

- Plugins

[Plugins](https://support.claude.com/plugins)
Plugins

- Powered by Claude

[Powered by Claude](https://support.claude.com/partners/powered-by-claude)
Powered by Claude

- Service partners

[Service partners](#)
Service partners

- Tutorials

[Tutorials](https://support.claude.com/resources/tutorials)
Tutorials

- Use cases

[Use cases](https://support.claude.com/resources/use-cases)
Use cases

Company

- Anthropic

[Anthropic](https://www.anthropic.com/)
Anthropic

- Careers

[Careers](https://www.anthropic.com/careers)
Careers

- Policy

[Policy](https://www.anthropic.com/policy)
Policy

- Economic Futures

[Economic Futures](https://www.anthropic.com/economic-futures)
Economic Futures

- Research

[Research](../19-Reference/anthropic-com-research.md)
Research

- News

[News](../19-Reference/news.md)
News

- Policy on the AI Exponential

---

## Using the PubMed Connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12614801-using-the-pubmed-connector-in-claude
Path: 14-Connectors/using-the-pubmed-connector-in-claude.md

# Using the PubMed Connector in Claude

Set up and use Claude's PubMed integration for access to millions of biomedical research articles and clinical studies.

25 minClaude.ai

[Open Claude](https://claude.ai/new)

The PubMed integration provides access to millions of biomedical research articles and clinical studies, allowing Claude to access abstracts and full papers to clarify experimental approaches, identify key findings, determine novelty and applicability, and surface specific papers for deeper exploration. This article explains how to set up and use the PubMed integration with Claude to accelerate your research workflows.

The PubMed integration relies upon Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities).

## What this integration provides[](#what-this-integration-provides)

The PubMed integration connects Claude directly to the PubMed database maintained by the U.S. National Library of Medicine. With over 36 million citations for biomedical literature, PubMed is the premier resource for medical research, scientific studies, and health information.

This integration allows you to:

- Search for research articles using keywords, authors, journals, or advanced query syntax
- Get complete article metadata including abstracts, authors, publication dates, citations, and links to the full article
- Access full-text articles from PubMed Central (PMC) when available
- Find related articles across NCBI databases
- Match citations to PubMed IDs for verification and referencing
- Convert between ID formats (PMID, PMC ID, DOI)

## Setting up the PubMed integration[](#setting-up-the-pubmed-integration)

**For Organization Owners (Team and Enterprise)**

1. Navigate to Admin settings \> Connectors
2. Click "Browse connectors"
3. Click "**PubMed**"
4. Click "Add to your team"

**For Individual Claude Users**

1. Navigate to Settings \> Connectors
2. Find "PubMed"
3. Click "Connect"

Learn about [finding and connecting tools(opens in new tab)](browse-skills-connectors-and-plugins-in-one-directory.md) in Claude.

**For Claude Code Users**

1. Command: `/plugin marketplace add anthropics/life-sciences`
2. Command: `/plugin install pubmed@life-sciences`
3. Restart Claude Code
4. Verify that the server is connected with `/mcp`

## Using the PubMed MCP with the Messages API[](#using-the-pubmed-mcp-with-the-messages-api)

Developers can connect to the PubMed integration directly through Claude's Messages API using the MCP connector. This allows you to build applications that leverage PubMed search capabilities programmatically.

### Requirements[](#requirements)

**An Anthropic API key**

The beta header: `anthropic-beta: mcp-client-2025-11-20`

### Setup[](#setup)



1. Add the PubMed MCP server to your API request's `mcp_servers` array
2. Reference the server in your `tools` array using an `mcp_toolset` entry
3. Include the required beta header

### Example Request[](#example-request)

python



``` thin-scrollbar
import anthropic

client = anthropic.Anthropic()

response = client.beta.messages.create(
model="claude-sonnet-4-5",
max_tokens=1000,
messages=[{"role": "user", "content": "Find recent papers on CRISPR gene editing in cancer treatment"}],
mcp_servers=[{"type": "url", "url": "https://pubmed.mcp.claude.com/mcp", "name": "pubmed"}],
tools=[{"type": "mcp_toolset", "mcp_server_name": "pubmed"}],
betas=["mcp-client-2025-11-20"]
)
```

## Common use cases[](#common-use-cases)

**Search for Research Articles**

Ask Claude to find articles on biomedical or scientific topics of interest. Example prompts:

Find recent studies about immunotherapy for melanoma



Open in Claude

Show me research on CRISPR gene editing from the last month



Open in Claude

Find literature related to a proposal or gene that I am working on



Open in Claude

**Get Article Details and Metadata**

Retrieve comprehensive information about specific articles. Example prompts:

What are the most cited papers on this topic?



Open in Claude

Find the most recent papers on this topic and summarize new contributions to the field?



Open in Claude

Who were the authors for that study?



Open in Claude

When was that paper published?



Open in Claude

**Access Full-Text Articles**

For articles available in PubMed Central, retrieve the complete text of the articles to help with your research. Example prompts:

Compare the methods of these two papers



Open in Claude

What were the shared conclusions across these papers, and where did they differ?



Open in Claude

Read these papers and help me identify the most important conclusions for my hypothesis



Open in Claude



**Note:** Only articles in PubMed Central (PMC) have full text available. PubMed might only have access to abstracts of other articles.

**Find Related Articles**

Discover similar research across NCBI databases. Example prompts:

Find similar studies to this one



Open in Claude

Compare the findings of this study to others in the field



Open in Claude

**Match Citations to PubMed IDs**

Verify citations and find PubMed IDs from journal references. Example prompts:

Look up this citation: Smith J, Nature 2020, vol 52, page 811



Open in Claude

Find the PubMed entry for this reference from my bibliography



Open in Claude

I have a citation from a paper, can you find it in PubMed?



Open in Claude

I would like to have a discussion about the paper associated with this PMID



Open in Claude

## Frequently asked questions[](#frequently-asked-questions)

**Is the PubMed integration free to use?**

Yes! The integration is free for all Claude users. PubMed is a free public resource provided by the U.S. National Library of Medicine.

**Can I access full-text articles for any paper?**

PubMed only makes the full text of articles available if they are in PubMed Central (PMC). PubMed contains over 36 million citations with abstracts, but PMC contains approximately 8 million full-text articles. Where the full text of an article is not available, Claude can provide relevant metadata (title, authors, abstract) if available, and can also supply a link to the full article for your review.

**How current is the data?**

PubMed is updated daily with new research. The integration provides real-time access to the latest available data from the NCBI databases.

**Does this work with other NCBI databases?**

The integration primarily accesses PubMed and PubMed Central. However, you can discover related data from other NCBI databases (like Gene, Protein, and Nucleotide databases) by asking Claude to find connections. For example:

Find genes associated with this article



Open in Claude

Show me protein sequences referenced in this paper



Open in Claude

Are there any nucleotide sequences linked to this study?



Open in Claude

**Are there any rate limits I should know about?**

Yes, the server has rate limits to comply with NCBI guidelines. If you receive a rate limit message, wait briefly and try again.

**Where does the data come from?**

All data comes from official NCBI sources, but may not reflect the most current/accurate data available from NLM: PubMed (the National Library of Medicine's MEDLINE database), PubMed Central (free full-text archive of biomedical literature), and the NCBI E-utilities API (official programmatic access to NCBI databases).

## Privacy and Data Usage[](#privacy-and-data-usage)

- The PubMed integration only accesses publicly available research articles
- No personal health information or patient data is accessible through the integration
- Your search queries are used only to retrieve relevant articles
- All data comes from official NCBI sources

## Additional Resources[](#additional-resources)

- PubMed Advanced Search Builder: [https://pubmed.ncbi.nlm.nih.gov/advanced/(opens in new tab)](https://pubmed.ncbi.nlm.nih.gov/advanced/)
- MeSH Database: [https://www.ncbi.nlm.nih.gov/mesh(opens in new tab)](https://www.ncbi.nlm.nih.gov/mesh)
- NCBI E-utilities Documentation: [https://www.ncbi.nlm.nih.gov/books/NBK25501/(opens in new tab)](https://www.ncbi.nlm.nih.gov/books/NBK25501/)

## Need More Help?[](#need-more-help)

If you're experiencing issues with the PubMed integration or have questions not covered here, please [contact Claude support(opens in new tab)](https://support.claude.com/en/articles/9015913-how-to-get-support) or visit our help center for additional troubleshooting guides.

- [What this integration provides](#what-this-integration-provides)
- [Setting up the PubMed integration](#setting-up-the-pubmed-integration)
- [Using the PubMed MCP with the Messages API](#using-the-pubmed-mcp-with-the-messages-api)
- [Common use cases](#common-use-cases)
- [Frequently asked questions](#frequently-asked-questions)
- [Privacy and Data Usage](#privacy-and-data-usage)
- [Additional Resources](#additional-resources)
- [Need More Help?](#need-more-help)

---

## Using the Scholar Gateway Connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12614815-using-the-scholar-gateway-connector-in-claude
Path: 14-Connectors/using-the-scholar-gateway-connector-in-claude.md

# Using the Scholar Gateway Connector in Claude

Set up and use the Scholar Gateway integration by Wiley with Claude for access to over 3 million peer-reviewed scientific articles.

2 minClaude.ai

[Open Claude](https://claude.ai/new)

The Scholar Gateway by Wiley integration provides authenticated access to the most relevant snippets of scientific research papers to utilize within Claude. This article explains how to set up and use the Scholar Gateway integration with Claude to accelerate your research workflows.

The Scholar Gateway integration relies upon Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/use-connectors-to-extend-claude-s-capabilities-d041e8447b.md).

## What this integration provides[](#what-this-integration-provides)

Currently \>3 million journal articles are available through Scholar Gateway with additional collections, databases and new articles being added all the time.

These datasets cover key STEM subjects including articles from a significant number of leading Life Sciences journals. Specifically, Scholar Gateway has over 300 Life Sciences journals that cover over 900,000 research articles.

Scholar Gateway (Beta) enables AI responses grounded in peer-reviewed sources with verifiable citations and DOI links.

Instead of relying on general AI knowledge, Scholar Gateway (Beta) searches current literature from Wiley journals and research databases to deliver evidence-backed answers with complete source metadata.

While the Beta currently provides access to Wiley content only, additional publisher sources will be added soon.

This enables you to verify that claims are backed with sourced research — ensuring your AI-assisted research meets professional research standards.

## Who can access the Scholar Gateway integration[](#who-can-access-the-scholar-gateway-integration)

- Existing subscribers to Wiley journals will need to upgrade their subscription following a trial period to allow AI access.
- New subscribers will need to subscribe subject to a trial period.

More details on accessing the integration can be found in [Wiley’s MCP Server Documentation(opens in new tab)](https://docs.scholargateway.ai/).

## Setting up the Scholar Gateway integration[](#setting-up-the-scholar-gateway-integration)

**For Organization Owners (Team and Enterprise)**

1. Navigate to Admin settings \> Connectors
2. Click "Browse connectors"
3. Click “**Scholar Gateway**”
4. Click “Add to your team”

**For Individual Claude Users**

1. Navigate to Settings \> Connectors
2. Click “Connect”
3. Follow the instructions to authenticate with your Wiley account

Learn about [finding and connecting tools(opens in new tab)](browse-skills-connectors-and-plugins-in-one-directory.md).

**For Claude Code Users**

1. Command: `/plugin marketplace add anthropics/life-sciences`
2. Command: `/plugin install wiley-scholar-gateway@life-sciences`
3. Restart Claude Code
4. Verify that the server is connected with `/mcp`

Technical details of the Scholar Gateway integration can be found in [Wiley’s MCP Server Documentation(opens in new tab)](https://docs.scholargateway.ai/).

## Common use cases[](#common-use-cases)

- Enhanced literature review when planning experiments and research plans, to efficiently identify, summarize, and evaluate relevant literature as individual articles or in aggregation, enabling new ways of doing research and delivering reliable and cited insights in seconds.
- Information on latest research in a certain field of medicine or pharmaceuticals.

- [What this integration provides](#what-this-integration-provides)
- [Who can access the Scholar Gateway integration](#who-can-access-the-scholar-gateway-integration)
- [Setting up the Scholar Gateway integration](#setting-up-the-scholar-gateway-integration)
- [Common use cases](#common-use-cases)

---

## Using the Synapse.org Connector in Claude · Claude Academy

Source: https://support.claude.com/en/articles/12614798-using-the-synapse-org-connector-in-claude
Path: 14-Connectors/using-the-synapse-org-connector-in-claude.md

# Using the Synapse.org Connector in Claude

Set up and use the Synapse.org integration with Claude to discover biomedical data and explore project structures across the Synapse platform.

15 minClaude.ai

[Open Claude](https://claude.ai/new)

The Synapse.org integration by Sage Bionetworks allows researchers to discover biomedical data across all of Synapse, see the structure of projects, and retrieve information on their data assets for authorized users. This article explains how to set up and use the Synapse.org integration with Claude to advance your research and analysis workflows.

The Synapse.org integration relies upon Claude's ability to [use remote connectors(opens in new tab)](https://support.claude.com/en/articles/use-connectors-to-extend-claude-s-capabilities-d041e8447b.md).

## What this integration provides[](#what-this-integration-provides)

Services include search and (meta)data retrieval services. Data access will be governed by the access controls defined for each project. Some data are publicly available, while others require approval from Synapse’s governance team prior to access.

## Who can access the Synapse.org integration[](#who-can-access-the-synapseorg-integration)

- Individuals who have a registered Synapse account ([register for free(opens in new tab)](https://accounts.synapse.org/register1?appId=synapse.org))
- Data access may be subject to use restriction from contributors

More details on accessing the integration can be found in [Synapse’s MCP Server Documentation(opens in new tab)](https://github.com/susheel/synapse-mcp?tab=readme-ov-file#synapse-mcp-server).

## Setting up the Synapse.org integration[](#setting-up-the-synapseorg-integration)

**For Organization Owners (Team and Enterprise)**

1. Navigate to Admin settings \> Connectors
2. Click "Browse connectors"
3. Click “**Synapse.org**”
4. Click “Add to your team”

**For Individual Claude Users**

1. Navigate to Settings \> Connectors
2. Click “Connect”
3. Follow the instructions to authenticate with your Synapse.org account

Learn about [finding and connecting tools(opens in new tab)](browse-skills-connectors-and-plugins-in-one-directory.md) in Claude.

**For Claude Code Users**

1. Command: `/plugin marketplace add anthropics/life-sciences`
2. Command: `/plugin install synapse@life-sciences`
3. Restart Claude Code
4. Verify that the server is connected with `/mcp`

Technical details of the Synapse.org integration can be found in [Synapse’s MCP Server Documentation(opens in new tab)](https://github.com/susheel/synapse-mcp?tab=readme-ov-file#synapse-mcp-server).

## Common use cases[](#common-use-cases)

- Search for reusable scientific data across all of the Synapse.org platform

Find RNA-seq datasets related to Alzheimer's disease in Synapse



Open in Claude

Search Synapse for single-cell transcriptomics datasets



Open in Claude

Find genomic sequencing data for plexiform neurofibromas in the NF Data Portal



Open in Claude

- Authorized users can see hierarchy of folders, files, tables, datasets within projects to help organize and monitor data assets

Explain the files and folders in the public AACR Project GENIE project



Open in Claude

Give me a quick overview of the data assets in the SEA-AD challenge project with agentic track (syn66496696)?



Open in Claude

- Get custom metadata of entities in Synapse

What are the annotations and metadata for file syn4553239?



Open in Claude

Show me the custom metadata fields for dataset syn66364675



Open in Claude

- Get provenance information for entities in Synapse to help understand past data processing

What's the processing history for file syn51543273?



Open in Claude

Show me the data lineage and upstream dependencies for the dataset syn68719289



Open in Claude

- [What this integration provides](#what-this-integration-provides)
- [Who can access the Synapse.org integration](#who-can-access-the-synapseorg-integration)
- [Setting up the Synapse.org integration](#setting-up-the-synapseorg-integration)
- [Common use cases](#common-use-cases)