diio’s MCP connects Claude directly to your diio workspace, allowing you to query sales metrics, analyze conversations, search deals and contacts in your CRM, and review scheduled meetings — all without leaving Claude. It is currently in early access (beta).
Before you start
Activation happens in two steps:
An admin sets up the connector once for the entire organization
Each user connects it individually from their own account
Optionally, you can install the diio skill for use in Claude Cowork
Part 1: connector setup (admin)
This step must be completed by a user with admin permissions. It enables the connector for the entire team.
1. Go to connectors
In Claude, navigate to:
Organization Settings → Connectors
Click Add (top right) and select Add custom connector.
2. Enter connector details
Fill in the following values:
Name: diio
Click Add to save.
Once configured, the diio connector will appear as CUSTOM, and all team members will be able to connect it.
Part 2: user activation
Each user who wants to use diio’s MCP must complete the following steps.
1. Connect the diio connector
Go to:
Settings → Connectors → Custom connectors
Find diio and click Connect.
2. Authenticate with your diio account
A diio login window will open. Sign in using Google or Microsoft, depending on your organization.
Review the requested permissions and click Authorize.
3. Confirm the connection
Once you return to the connectors screen, the status should show Connected.
The MCP is now active for your account.
MCP permissions
diio’s MCP operates in read-only mode.
This means:
It can query data
It cannot create or modify anything
It has access to:
deals
conversations
company data
Each user can only access the data they already have permission to view in diio.
Part 3: install the diio skill (Claude Cowork)
This step is optional but recommended for teams using Claude Cowork.
Automatic installation
1. Download the skill file
Download the .skill file here: diio.skill
2. Install
Double-click the file. This will install the skill in:
.claude/skills/diio-assistant/
3. Use it in Cowork
Open a new conversation in Claude Cowork and type:
/diio
The assistant will respond with available capabilities and be ready to use.
Part 4: manual skill installation
In some environments, manual installation is required.
1. Create the folder
In your team’s configuration directory, create:
.claude/skills/diio-assistant/
2. Add the SKILL.md file
Place the SKILL.md file inside that folder.
The final structure should be:
.claude/skills/diio-assistant/SKILL.md
3. Use it in Cowork
Open a new conversation and type:
/diio-assistant
What you can do with diio’s MCP
Once connected, you can ask Claude things like:
Metrics: “Which reps had the most calls this week?”
CRM search: “Find the deal for Company XYZ”
Conversation analysis: “What are the most common objections this month?”
Meetings: “What meetings do I have today connected to diio?”
Important
diio’s MCP is currently in beta. This means:
It may produce errors
It is continuously evolving
It may not be available at all times
Also:
It is an advanced configuration
It operates in read-only mode
It respects each user’s permission levels in diio
Frequently Asked Questions
Access to conversations via MCP
Once an admin sets up the connector once for the entire organization, each user must log in to diio to install the MCP. Once configured, the MCP will only allow your LLM (e.g., Claude or similar models) to access the conversations that the user already has permission to view within diio.
This means that if a user cannot see certain conversations in diio (for example, from another team or location), the MCP will not be able to access them either.
Does diio log or store interactions that go through the MCP?
The flow works as follows:
The user submits a query to their LLM (e.g., Claude).
The LLM determines which MCP functions (queries) are needed to respond.
The LLM executes a query to the MCP.
This query is sent to diio.
diio does not have visibility into the original content of the user’s query to the LLM. It only logs which MCP function was executed to process the request.