Connect your AI tools to Claap using the MCP server
Learning Objective
By the end of this tutorial, you'll know how to connect a third-party AI assistant or automation tool to your Claap workspace using the MCP server, authenticate your access, and query your Claap meetings, contacts, companies, and deals directly from your AI tool.
Why This Matters
Switching between Claap and your AI assistant to manually copy meeting data breaks your workflow and slows down analysis. Claap's MCP (Model Context Protocol) server gives your AI tools direct access to your workspace data — recordings, contacts, companies, and deals — so you can ask natural language questions and get answers grounded in your actual Claap data without leaving your AI tool.
Prerequisites
Before starting, you should already have:
A Claap account with access to at least one workspace
A third-party application that supports the MCP protocol (such as Claude.ai or an n8n workflow)
Appropriate permissions in your Claap workspace to access recordings, contacts, and company data
If authenticating with an API key: your Claap API key (see Using Claap's API)
Core Lesson — Step-by-Step Workflow
Phase 1: Configure your third-party application to connect to Claap
Step 1: Add the Claap MCP server URL to your application
Open your third-party application's MCP or integration settings and enter the Claap MCP server URL:
This endpoint is the single connection point between your AI tool and your Claap workspace data. Every query your AI tool sends to Claap passes through this URL.
Phase 2: Authenticate your Claap MCP connection
Choose one of the two authentication methods below. OAuth is the default; API key authentication is available if your tool or workflow requires it.
Step 2a: Authenticate with OAuth (default)
Before authenticating, make sure you are signed in to your Claap account at https://app.claap.io.
When your third-party application connects to https://api.claap.io/mcp, Claap prompts you to complete an OAuth flow. Complete the OAuth prompt to grant your application access to your Claap workspace.
OAuth authentication verifies your identity and confirms that you have permission to access recordings, contacts, companies, and deals within your Claap workspace.
Step 2b: Authenticate with an API key (alternative)
If your application supports bearer token authentication, you can bypass the OAuth flow by adding an Authorization header to your MCP requests:
Authorization: Bearer cla_xxxxx
Replace cla_xxxxx with your actual Claap API key. To obtain an API key, follow the instructions in Using Claap's API.
Phase 3: Wait for Claap MCP tools to install in your application
Step 3: Confirm the Claap MCP tools are available
After authentication, wait a few seconds to a few minutes for your application to detect and install the available Claap MCP tools automatically.
When the tools are ready, your application lists them with a success indicator:
Verify: Your application should display the Claap MCP tools in its tool list before you proceed to Step 4.
Phase 4: Query your Claap data from your AI tool
Step 4: Ask questions about your Claap workspace data
With the Claap MCP tools installed, type a natural language question about your Claap data into your AI tool. Your application automatically selects the relevant Claap MCP tool based on what you ask.
For example:
"Summarize my last three sales calls with Acme Corp" → triggers the Search Meeting Recordings tool
"Who are the contacts at Contoso?" → triggers the Search Contacts tool
"What's the status of the deal with Initech?" → triggers the Search Deals tool
Your AI tool handles tool selection automatically — you ask in plain language, and Claap's MCP server retrieves the relevant data.
Available Claap MCP tools
After successful authentication, the following tools are available in your application:
Tool | What it does |
List Workspaces | Displays all Claap workspaces you have access to |
Search Companies | Searches your workspace's company database |
Search Contacts | Searches contacts, including workspace members and external participants extracted from meetings |
Search Deals | Searches your workspace's deal database |
Search Meeting Recordings | Searches recordings by topic (semantic), keyword, or metadata filters (date, participants, duration). Returns transcript chunks grouped by recording. |
Recording access note: A recording is retrievable through the Claap MCP tools only if the recording itself — or its folder — is accessible to workspace members and visible in global search.
Practical Application
Example: Summarizing competitor mentions across recent sales calls
Situation: A sales manager has dozens of recorded discovery calls in their Claap workspace from the past month.
Goal: Find every call where a specific competitor was mentioned, without watching each recording manually.
How they built it:
Connected Claude.ai to
https://api.claap.io/mcpand completed OAuth authenticationWaited for the Claap MCP tools to appear in Claude's tool list
Asked Claude: "Find all recordings from the last 30 days where [Competitor Name] was mentioned"
The Search Meeting Recordings tool ran a semantic search across all accessible recordings and returned transcript chunks grouped by recording, showing the context of each mention
Result: The manager reviewed competitor mentions across all recent calls in minutes, without leaving Claude.ai.
For step-by-step instructions specific to Claude.ai, see Using Claap's MCP server with Claude.ai. For n8n workflows, see Using Claap's MCP server in your n8n workflow.
Troubleshooting & Pitfalls
Issue: Authentication fails or access is denied when connecting to https://api.claap.io/mcp Why: Your Claap account may lack the required permissions, or you are not signed in to Claap before starting the OAuth flow. Fix:
Confirm you are signed in at https://app.claap.io before initiating the OAuth flow.
Contact your Claap workspace administrator to verify your permissions.
If using API key authentication, confirm the key is formatted correctly:
Authorization: Bearer cla_xxxxx.
Issue: The Claap MCP tools do not appear in your application after authentication. Why: Detection can take up to a few minutes, or the MCP server URL may have been entered incorrectly. Fix:
Wait 2–3 minutes and refresh your application.
Confirm the MCP server URL is entered exactly as:
https://api.claap.io/mcp(no trailing slash, no typos).Verify that your third-party application supports the MCP protocol.
Issue: Search returns no results for recordings you know exist in Claap. Why: The recording or its folder may not be visible to workspace members in global search, or the search terms are too specific. Fix:
Confirm you are querying the correct Claap workspace using the List Workspaces tool.
Try broader search terms or partial phrases.
Check in Claap that the recording and its folder are accessible to workspace members and appear in global search.
Cross-Links / Learn More
Next level: Using Claap's MCP server with Claude.ai — step-by-step setup for Claude.ai specifically
Next level: Using Claap's MCP server in your n8n workflow — step-by-step setup for n8n automation
Prerequisites: Using Claap's API — how to generate and manage your Claap API key