### Claude for Sheets - Installation and Setup

Source: https://support.claude.com/en/articles/13162029-google-sheets-add-on

Steps to install the Claude for Sheets add-on and connect your Claude API key.

```APIDOC
## Claude for Sheets - Installation and Setup

### Description
This section outlines the process for installing the Claude for Sheets add-on and configuring it with your Claude API key.

### Installation Steps
1. **Get your Claude API key:** Obtain an API key from the [Claude Console](https://console.anthropic.com/keys).
2. **Install the Claude for Sheets extension:** Search for "Claude for Sheets" in the Google Workspace Marketplace, click `Install`, and accept the required permissions.
   * **Permissions Explained:**
     * `View and manage spreadsheets...`: Allows running prompts and returning results.
     * `Connect to an external service`: Enables calls to Claude API endpoints.
     * `Allow this application to run when you are not present`: Facilitates background cell recalculations.
     * `Display and run third-party web content...`: Used for the sidebar and post-install prompts.
3. **Connect your API key:** Navigate to `Extensions` > `Claude for Sheets™` > `Open sidebar` > `☰` > `Settings` > `API provider` and enter your API key. You may need to refresh the menu.

**Note:** The API key must be re-entered for each new Google Sheet.
```

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

### Manual Setup: Enable in Claude Admin Settings

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

Steps for an organization Owner to enable the Microsoft 365 connector in Claude's admin settings after manual setup in Microsoft Entra ID.

```APIDOC
## Manual Setup: Enable in Claude Admin Settings

### Description
After completing the manual setup and admin consent in Microsoft Entra ID, an organization Owner needs to enable the Microsoft 365 connector within Claude's admin settings.

### Method
N/A (UI Interaction)

### Endpoint
N/A (UI Interaction)

### Parameters
N/A

### Request Example
N/A

### Response
N/A

**Steps:**
1. Sign in to Claude.
2. Navigate to Admin Settings > Connectors.
3. Click the “Browse connectors” button at the bottom of the page.
4. Find "Microsoft 365" and click "Add to your team."

After this, "Microsoft 365" will appear in the list of Connectors at Settings > Connectors.
```

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

### Automatic Setup: Enable in Individual Claude Settings

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

Steps for a Microsoft Entra Global Administrator to connect to Microsoft 365 in their individual Claude user settings after organization-level setup.

```APIDOC
## Enable in Individual Claude Settings

### Description
After the organization-level setup, the Microsoft Entra Global Administrator needs to connect to Microsoft 365 in their individual Claude user settings.

### Method
N/A (UI Interaction)

### Endpoint
N/A (UI Interaction)

### Parameters
N/A

### Request Example
N/A

### Response
N/A

**Steps:**
1. Navigate to Settings > Connectors.
2. Find "Microsoft 365" in the list and click "Connect."
3. Authenticate with your Microsoft 365 credentials.
4. Review and accept the requested permissions, checking the box to grant access on behalf of the whole organization.
   * This step must be completed before any team members can connect to Microsoft 365 individually.
5. (Optional) To restrict users, navigate to the M365 MCP Server for Claude enterprise application in the Entra admin center (https://entra.microsoft.com), go to Properties, set “Assignment required?” to Yes, and assign users/groups. Repeat for the M365 MCP Client for Claude enterprise application.
6. (Optional) To selectively restrict permission scopes, refer to "Permission categories" and "Selectively revoking permissions" sections (not detailed here).
```

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

### Documentation Updates with Claude

Source: https://support.claude.com/en/articles/12618689-claude-code-on-the-web

This section details how to use Claude for generating or updating technical documentation, such as README files, API documentation, code comments, or user guides. The example prompt focuses on updating a CHANGELOG.md file by reviewing commits since a specific release tag, categorizing changes, and including commit hashes.

```prompt
Update CHANGELOG.md with all changes since the v2.3.0 release:  
  - Review commits on main branch since that tag.   
  - Categorize changes into "Added, "Changed, "Fixed", and "Removed" sections.   
  - Include the commit hash for each entry.
```

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

### Manual Setup: Enable in Individual Claude Settings

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

Steps for the Microsoft Entra Admin to connect to Microsoft 365 in their individual Claude user settings after organization-level manual setup.

```APIDOC
## Manual Setup: Enable in Individual Claude Settings

### Description
After the organization-level manual setup is complete, the Microsoft Entra Admin needs to connect to Microsoft 365 in their individual Claude user settings.

### Method
N/A (UI Interaction)

### Endpoint
N/A (UI Interaction)

### Parameters
N/A

### Request Example
N/A

### Response
N/A

**Steps:**
1. Navigate to Settings > Connectors.
2. Find "Microsoft 365" in the list and click "Connect."
3. Authenticate with your Microsoft 365 credentials.
4. Review and accept the requested permissions, checking the box to grant access on behalf of the whole organization.
   * This step must be completed before any team members can connect to Microsoft 365 individually.
```

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

### Manual Setup: Grant Admin Pre-consent

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

Steps to grant admin pre-consent for the M365 MCP Client and Server for Claude applications by constructing and visiting specific URLs.

```APIDOC
## Manual Setup: Grant Admin Pre-consent

### Description
Grant admin pre-consent for the Microsoft 365 connector applications by constructing and visiting specific admin consent URLs. This allows the applications to access your organization's data.

### Method
N/A (Browser Navigation)

### Endpoint
N/A (Browser Navigation)

### Parameters
#### Path Parameters
- **{your-tenant-id}** (string) - Required - Your organization's Microsoft Entra tenant ID.

### Request Example
N/A

### Response
N/A

**Steps:**
1. **Grant pre-consent for M365 MCP Client for Claude:**
   - Visit the following URL in your browser, replacing `{your-tenant-id}` with your organization's tenant ID:
     `https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=08ad6f98-a4f8-4635-bb8d-f1a3044760f0`

2. **Grant pre-consent for M365 MCP Server for Claude:**
   - Visit the following URL in your browser, replacing `{your-tenant-id}` with your organization's tenant ID:
     `https://login.microsoftonline.com/{your-tenant-id}/adminconsent?client_id=07c030f6-5743-41b7-ba00-0a6e85f37c17`

   - You will be prompted to consent to the delegated user permissions required by the integration on behalf of your organization.
```

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

### Start Claude Code session

Source: https://support.claude.com/en/articles/11845131-using-claude-code-with-your-team-or-enterprise-plan

Initiates a Claude Code session in your terminal. This command is used to start interacting with Claude models for coding tasks after installation and authentication.

```bash
claude
```

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

### MCP Tool Annotation Example (JSON)

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

This example demonstrates the required JSON structure for tool annotations in MCP servers. It includes the 'readOnlyHint' property, which is mandatory for all tools to avoid immediate rejection during submission.

```json
{
  "name": "read_data",
  "readOnlyHint": true
}
```

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

### Automatic Setup: Enable in Claude Admin Settings

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

Steps for an organization Owner and Microsoft Entra Global Administrator to enable the Microsoft 365 connector within Claude's admin settings.

```APIDOC
## Enable in Claude Admin Settings

### Description
As an organization Owner and Microsoft Entra Global Administrator, follow these steps to enable the Microsoft 365 connector in Claude's admin settings.

### Method
N/A (UI Interaction)

### Endpoint
N/A (UI Interaction)

### Parameters
N/A

### Request Example
N/A

### Response
N/A

**Steps:**
1. Sign in to Claude.
2. Navigate to Admin Settings > Connectors.
3. Click the “Browse connectors” button at the bottom of the page.
4. Find "Microsoft 365" and click "Add to your team."

After this, "Microsoft 365" will appear in the list of Connectors at Settings > Connectors.
```

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

### Manual Setup: Add Service Principals

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

Steps to manually add the required service principals for the Microsoft 365 connector in Microsoft Entra ID using Microsoft Graph Explorer.

```APIDOC
## Manual Setup: Add Service Principals

### Description
Manually add the two required service principals to Microsoft Entra ID using Microsoft Graph Explorer. This process establishes service-level identities for the M365 MCP for Claude app registrations.

### Method
POST

### Endpoint
https://graph.microsoft.com/v1.0/servicePrincipals

### Parameters
#### Request Body
- **appId** (string) - Required - The application ID for the service principal.

### Request Example
```json
{
  "appId": "08ad6f98-a4f8-4635-bb8d-f1a3044760f0"
}
```

### Response
#### Success Response (201 Created)
- **id** (string) - The unique identifier for the created service principal.
- **appId** (string) - The application ID of the service principal.

#### Response Example
```json
{
  "id": "<service-principal-object-id>",
  "appId": "08ad6f98-a4f8-4635-bb8d-f1a3044760f0"
}
```

**Steps:**
1. **Add M365 MCP Client for Claude:**
   - **Method:** POST
   - **Endpoint:** `https://graph.microsoft.com/v1.0/servicePrincipals`
   - **Body:** `{"appId":"08ad6f98-a4f8-4635-bb8d-f1a3044760f0"}`

2. **Add M365 MCP Server for Claude:**
   - **Method:** POST
   - **Endpoint:** `https://graph.microsoft.com/v1.0/servicePrincipals`
   - **Body:** `{"appId":"07c030f6-5743-41b7-ba00-0a6e85f37c17"}`
```

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

### Example Tenant Restriction Header

Source: https://support.claude.com/en/articles/13198485-enforce-network-level-access-control-with-tenant-restrictions

Provides an example of the `anthropic-allowed-org-ids` header, demonstrating the correct format with multiple organization UUIDs. This illustrates how to list multiple approved organizations for access.

```text
anthropic-allowed-org-ids: 550e8400-e29b-41d4-a716-446655440000,6ba7b810-9dad-11d1-80b4-00c04fd430c8
```

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

### Install Claude Desktop MSIX (Single User) - PowerShell

Source: https://support.claude.com/en/articles/12622703-deploy-claude-desktop-for-windows

Installs the Claude Desktop MSIX package for the current user. This command requires the path to the MSIX file. Refer to Microsoft's Add-AppxPackage documentation for further details.

```powershell
Add-AppxPackage -Path "Claude.msix"
```

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

### Package Claude Extension using mcpb

Source: https://support.claude.com/en/articles/12922832-local-mcp-server-submission-guide

Commands to clean build, install production dependencies, package the extension, and verify the package using the mcpb tool. Assumes Node.js environment and mcpb installed.

```bash
# Clean build
rm -rf node_modules/.cache
npm install --production

# Package
mcpb pack

# Verify package
mcpb info your-extension.mcpb
```

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

### Install Claude Code using npm

Source: https://support.claude.com/en/articles/11845131-using-claude-code-with-your-team-or-enterprise-plan

This command installs the Claude Code command-line tool globally using npm. Ensure Node.js version 18 or higher is installed before running this command. This is a prerequisite for using Claude Code.

```bash
npm install -g @anthropic-ai/claude-code
```

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

### Install Wiley Scholar Gateway Plugin for Claude Code

Source: https://support.claude.com/en/articles/12614815-using-the-scholar-gateway-connector-in-claude

These commands are used to add and install the Wiley Scholar Gateway plugin within Claude Code. Ensure Claude Code is restarted after installation and verify the connection using the provided command.

```bash
/plugin marketplace add anthropics/life-sciences
/plugin install wiley-scholar-gateway@life-sciences
/mcp
```

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

### Refactoring Code with Clear Scope using Claude

Source: https://support.claude.com/en/articles/12618689-claude-code-on-the-web

This example illustrates using Claude for refactoring code to improve organization or readability, provided clear boundaries for the change can be defined. This includes tasks like extracting code, splitting large files, or organizing module structures. The prompt provides a specific scenario of splitting a large Go class into three focused services and ensuring tests remain valid.

```prompt
The UserService class in /src/services/user.go has 800 lines long.  
Split it into three focused services:   
  - UserAuthService (login/logout/sessions)   
  - UserProfileService (profile CRUD operations)   
  - UserPreferencesService (settings/preferences)  
  
Ensure all tests still pass.
```

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

### Manage Claude Code Permissions with Settings Files

Source: https://support.claude.com/en/articles/12386420-claude-code-faq

Permissions in Claude Code are managed using pattern matching in `.claude/settings.json` or `settings.local.json`. Wildcard syntax and exact command matching are supported. Incremental permission building is recommended.

```json
{
  "permissions": {
    "allow": [
      "Bash(atlassian-api:*)",
      "git clone https://github.com/example/repo.git"
    ]
  }
}
```