---
title: "Step 3: Pull a Report with Blancco Connections"
canonical: "https://support.blancco.com/space/KB/1020559381/Step%203%3A%20Pull%20a%20Report%20with%20Blancco%20Connections"
format: markdown
---
> Macro (toc)

**Purpose**: Blancco Connections uses MCP to securely query Blancco Management Portal reporting data for audits, reconciliation, reporting review, and operational analysis.

### Getting started

You can connect BMP MCP through Claude Code **or** Microsoft Copilot. Here is a step-by-step guide:

#### Getting Started & Connecting with BMP MCP - Claude Code

BMP MCP is a Centralized integration component.

##### **Requirements:**

1. A valid BMP Account
2. Add-on license: MCP license
3. AI Assistant: Claude Cowork / Claude Code

##### **Create API key for MCP Server:**

1. Login to Blancco Management Portal with an admin account
2. Navigate to “Help” → “My API Keys”
3. Click “Generate API key”
4. Use following example to create new MCP server API key:

![image](media://46cb6ed8-dd8b-478b-8d8f-8e99ca861c88)

5. Click “Generate” to create a new key
6. Click “Copy API key” and paste it to a text editor

![image](media://993e151d-dc89-4513-a611-cb05855ee074)

#### **Instructions for Claude users:**

If you don’t yet have Claude Code setup, follow the quick start guide in: [https://code.claude.com/docs/en/quickstart](https://code.claude.com/docs/en/quickstart) 

1. Form a command to connect to BMP MCP Server: claude mcp add --transport http bcc-prod-mcp [https://luna-eu-west-1.portal.blancco.cloud/mcp](https://luna-eu-west-1.portal.blancco.cloud/mcp) --header “X-BLANCCO-API-KEY:<YOURAPIKEY>"
2. Open Terminal and copy and paste to your command to the terminal   
(Note! The command must be run before you launch Claude, from terminal / command prompt)

![image](media://1d83ea12-16e8-4219-a065-b6e9505f90c4)

3. Next login to Claude using a command: claude
4. Type /mcp to Manage MCP Servers

![image](media://0862694e-7f04-44ea-9015-ea1bd9ce4bc3)

5. Open bcc-prod-mcp

![image](media://3ec79a79-6253-40ae-bf17-831e9c46b59b)

6. Select “1. Authenticate”.   
note! if you get an error in connection, click “disable” and then connect again

![image](media://d31f3fd8-243c-4663-a5d3-ab6b9accc656)

7. Claude is now successfully connected to Claude:

![image](media://d3d4dafa-e07a-4f5b-a411-0689cb6aa701)

8. Use “esc” to navigate back to a Terminal CLI Interface
9. Try out the MCP with few prompt templates:  
”Give me a weekly throughput of devices within last 3 months. Which week we've had the most errors and what those issues have been? Create me a HTML visualization of the results.”

#### Getting Started & Connecting with BMP MCP - Microsoft Copilot

BMP MCP is a Centralized integration component

##### **Requirements:**

1. A valid BMP Account
2. Add-on license: MCP license
3. AI Assistant: Claude Cowork / Claude Code

##### **Create API key for MCP Server:**

1. Login to Blancco Management Portal with an admin account
2. Navigate to “Help” → “My API Keys”
3. Click “Generate API key”
4. Use following example to create new MCP server API key:

![image](media://865bf668-849d-4fbf-b73e-9c6e5f505145)

5. Click “Generate” to create a new key
6. Click “Copy API key” and paste it to a text editor

![image](media://25785269-104d-475e-ba7d-7120f12f1c1f)

#### **Instructions for Microsoft Copilot Users:**

Requirements:

1. Copilot Professional license

**Login to Copilot Studio:**

1. [https://www.microsoft.com/en-us/microsoft-365-copilot/microsoft-copilot-studio](https://www.microsoft.com/en-us/microsoft-365-copilot/microsoft-copilot-studio)
2. Create new Agent

![image](media://643b3fd8-0407-4190-b1c2-2b707d163f77)

3. Select “+” from tools

![image](media://229cc994-a27d-46df-a210-191fa85fba75)

4. Click “Add” to and select Model Context Protocol (MCP)

![image](media://709e3497-1301-4202-ab88-89fe6d9a5e62)

5. Insert BMP MCP details

![image](media://f4ef3a40-d57e-462a-8740-8dead354ed9a)

6. bcc-prod-mcp is now connected

![image](media://4694713a-2558-4b85-a64b-6db72e34ab36)

### Suggested prompts to try

#### Audit and evidence retrieval

**Scenario: Missing evidence check**  
“Search for erasure reports for these serial numbers and tell me which assets have completed reports and which are missing evidence.”

#### Failure analysis

**Scenario: Failed erasure review**  
“Find all failed erasures from last month, group them by failure reason, and highlight any patterns by device model or site.”

#### Reporting summary

**Scenario: Quarterly activity summary**  
“Summarize our erasure activity for the last quarter, including total reports, pass rate, common failure reasons, and standards used.”

**Success looks like: **The report comes back accurate and complete, and reconciling it takes noticeably less manual digging than usual.