Integrations
Aila MCP

Aila Model Context Protocol (MCP)

Connect Claude, Claude Code, Cursor, and other MCP-compatible clients to Aila using the Model Context Protocol. The Aila MCP lets your agent read call data, analyze real conversations, and help configure your account when you approve setup changes.

Overview

The Aila MCP server enables Claude to:

  • List your calls - Browse and search through your call library
  • Read call transcripts - Access full conversation transcripts in multiple formats
  • Retrieve call metadata - Get call details, participants, duration, and more
  • Analyze real call patterns - Find call types, common fields, follow-up commitments, and coaching themes
  • Review current setup - Inspect datasets, routing rules, task triggers, scorecards, connected sources, and CRM fields
  • Configure Aila with approval - Create or update setup items after showing you the exact proposed changes

This integration is perfect for:

  • Analyzing call patterns and trends
  • Creating custom reports from call data
  • Automating follow-up tasks based on call content
  • Setting up datasets, call routing, task triggers, and scorecards from real calls
  • Building AI workflows that reference specific calls
  • Extracting insights across multiple conversations

Recommended Setup Workflow

After you have connected the MCP and Aila has processed a useful sample of calls, ask your agent to follow the built-in Aila setup process:

Use the Aila MCP to configure my account from real calls.

First call getAilaConfigurationSkill and follow that process. Start by checking my current setup, then analyze my recent non-voicemail calls, identify recommended datasets, call routing rules, task triggers, scorecards, and CRM mappings.

Do not create or update anything until you show me the exact proposed changes and I explicitly approve them.

The getAilaConfigurationSkill tool returns the current Aila setup runbook directly from the MCP server, so you do not need to paste a long prompt into every new chat.

Installation

Claude Desktop (Recommended)

Claude Desktop provides the easiest setup experience with OAuth authentication -- no API keys required.

Step 1: Open Connectors Settings

  1. Open the Claude Desktop application
  2. Navigate to Settings
  3. Select Connectors (or Cowork)
Connectors Settings
Connectors Settings

Step 2: Add Custom Connector

  1. Scroll to the bottom and click "Add custom connector"
  2. A dialog will appear
Add Custom Connector
Add Custom Connector

Step 3: Configure Aila

Enter the following details:

  • Name: Aila
  • Server URL: https://app.aila.fyi/api/mcp
  • Leave the Advanced Settings (OAuth Client ID / Secret) blank

Click "Add" to save.

Step 4: Authorize Connection

  1. Find Aila in your connectors list
  2. Click "Connect"
Connectors Overview
Connectors Overview
  1. You'll be redirected to the Aila authorization page
  2. Sign in with your Aila credentials
OAuth Authorization
OAuth Authorization
  1. Click "Authorize" to grant access to your Aila call data and setup tools

Step 5: Start Using

Return to Claude Desktop and start querying your calls:

Show me my last 10 calls from Aila

To configure Aila from real call patterns, use:

Use the Aila MCP to configure my account from real calls. First call getAilaConfigurationSkill and follow that process.

Using the Aila MCP

Once connected, you can interact with your Aila data naturally in Claude or another MCP-compatible agent.

Example Prompts

List Recent Calls:

Show me my last 10 calls from Aila

Analyze Specific Call:

Read the transcript from my call with John Smith on February 5th

Extract Insights:

Summarize the key action items from my sales calls this week

Compare Calls:

Compare the objections raised in my last 3 demos

Generate Reports:

Create a report of all calls where the prospect mentioned budget concerns

Follow-up Automation:

For each call from yesterday, draft a personalized follow-up email

Account Configuration From Calls:

Use the Aila MCP to configure my account from real calls. First call getAilaConfigurationSkill and follow that process.

Available MCP Tools

The hosted Aila MCP endpoint exposes call analysis tools and account setup tools. Some standalone npm-package clients may expose only the core call tools.

Core Call Tools

list_calls

List recent calls from your Aila workspace. Returns call IDs, contact names, dates, and durations.

Parameters:

  • page (optional): Page number for pagination (default: 1)
  • limit (optional): Results per page (default: 20, max: 50)
  • search (optional): Search by contact name

Returns:

Found 42 calls (showing page 1 of 3):

- **John Smith** (2/10/2026, 15min) — ID: `call_abc123` [completed]
- **Sarah Johnson** (2/9/2026, 8min) — ID: `call_def456` [completed]
- **Acme Corp** (2/8/2026, 22min) — ID: `call_ghi789` [completed]
...

Example Usage:

List my last 10 calls
Show me calls with "Acme" in the contact name

get_call_transcript

Retrieve the full transcript for a specific call. Use list_calls first to find the call ID.

Parameters:

  • call_id (required): The unique identifier for the call (from list_calls)
  • format (optional): Transcript format (default: identified)
    • identified: Transcript with speaker names (e.g., "John Smith: Hi there...")
    • diarized: Transcript with speaker labels (e.g., "Speaker 1: Hi there...")
    • raw: Plain text transcript without speaker identification

Returns: Full transcript with speaker labels based on the selected format. The tool automatically falls back through formats if the requested format isn't available: identified → diarized → raw.

Example Usage:

Get the transcript for call_abc123
Show me the transcript for my call with John Smith (use identified format)
Read the transcript from call_def456 in raw format

Additional Call Analysis Tools

The hosted MCP endpoint can also expose tools such as:

  • search_calls - Search by contact, caller, date range, call type, tags, duration, transcript keywords, follow-up status, extracted fields, or deal status
  • get_call_details - Retrieve a full call record, extracted fields, summary, follow-ups, and optionally the transcript
  • lookup_contact and search_contacts - Review contact-level call history and engagement patterns
  • get_team_performance - Summarize team call volume and performance metrics

Account Setup Tools

For setup work, start with:

First call getAilaConfigurationSkill and follow that process.

The setup process uses tools such as:

  • getSetupStatus and getIngestionDiagnostics - Check connected sources, call flow, datasets, routing, task triggers, scorecards, and ingestion health
  • analyzeCallTranscripts - Analyze recent calls to discover call types, dataset fields, and task trigger patterns
  • getDatasetDetails, getRoutingRuleDetails, getTaskTriggers, and getScorecardDetails - Read existing configuration before proposing changes
  • getGhlCustomFields - Inspect connected GoHighLevel fields before recommending CRM mappings
  • createDataset, updateDataset, createRoutingRule, updateRoutingRule, createTaskTrigger, updateTaskTrigger, createScorecard, updateScorecard, and createDatasetFromGhlFields - Apply approved setup changes

Before using any create or update tool, the agent should show you the exact proposed changes and wait for explicit approval.

Use Cases

Sales Enablement

Coaching Analysis:

Analyze my team's discovery calls and identify common areas for improvement

Best Practice Extraction:

Review our top-performing calls and create a talk track template

Objection Handling:

Show me how our best reps handle pricing objections

Customer Success

Health Score Analysis:

Review calls with customers who churned and identify warning signs

Feature Requests:

Extract all feature requests mentioned in customer calls this month

Sentiment Tracking:

Analyze the sentiment of our quarterly business reviews

Research & Insights

Theme Identification:

What are the most common pain points mentioned across all calls?

Competitive Intelligence:

List all mentions of competitors and their products

Market Research:

Summarize what customers are saying about our pricing model

Workflow Automation

CRM Updates:

For calls missing next steps in the CRM, extract action items from transcripts

Meeting Prep:

Before my call with Acme Corp, summarize our previous conversations

Documentation:

Create customer success playbooks based on successful onboarding calls

Account Setup

Call Type Configuration:

Analyze my last 50 completed calls and recommend the call types and routing rules Aila should use.

Dataset Design:

Review my recent discovery calls and propose the structured fields Aila should extract from this call type.

Task Trigger Setup:

Find recurring commitments our reps make on sales calls and recommend task triggers. Only include agent-side commitments, not promises made by prospects.

CRM Field Mapping:

Look at my GoHighLevel custom fields and recent calls, then recommend which Aila dataset fields should map back to the CRM.

Privacy & Security

Data Access

  • Call data access: The MCP can read calls, transcripts, summaries, extracted fields, and related call metadata that your Aila account is allowed to access
  • Setup tools: Authorized setup users can approve changes to datasets, routing rules, task triggers, scorecards, and CRM mappings
  • No call deletion: The MCP tools do not delete calls or transcripts
  • Workspace scoped: The MCP only accesses data from the Aila workspace connected during authentication

Authentication Methods

OAuth (Recommended):

  • Secure authorization flow
  • No API keys to manage
  • Easy to revoke access
  • Token expiry for added security
  • Recommended for Claude Desktop, Claude Code, Cursor, and any client that supports remote HTTP MCP servers

API Key:

  • Useful for CLI tools and automation
  • Keep secure and never commit to version control
  • Can be revoked anytime in Settings > API Keys
  • Best for the standalone npm package when your MCP client cannot connect to the hosted endpoint

Best Practices

  1. Only Connect Trusted Clients: Only add the Aila MCP to applications you trust
  2. Review Permissions: Understand what data and setup tools the MCP can access
  3. Regular Audits: Periodically review connected applications
  4. Disconnect When Not Needed: Remove the connector if you're not actively using it
  5. Approve Changes Explicitly: For configuration work, review the proposed datasets, routing rules, task triggers, scorecards, or CRM mappings before allowing the agent to apply them

Troubleshooting

Connection Issues

"Unable to connect to Aila"

  • Verify the URL is exactly: https://app.aila.fyi/api/mcp
  • Check your internet connection
  • Try disconnecting and reconnecting
  • Ensure your Aila account is active

OAuth Authorization Fails:

  • Check that you're using valid Aila credentials
  • Verify your account has call data access
  • Try clearing browser cache and re-authorizing
  • Contact support if the issue persists

No Calls Returned

"I don't see any calls" or "No calls found"

  • Confirm your Aila workspace has recorded calls
  • The list_calls tool only shows completed calls (not in-progress)
  • If using search parameter, try removing it to see all calls
  • Verify workspace permissions
  • Check pagination - you might be on a page beyond your total results

Transcript Not Available

"Cannot retrieve transcript"

  • Ensure the call has finished processing
  • Check that the call has a transcript (not all calls do)
  • Verify the call_id is correct
  • Some very old calls may have archived transcripts

API Key Issues (CLI Tools)

"Unauthorized" or "Invalid API Key"

  • Verify your API key is correct
  • Check that the key hasn't been deleted or expired
  • Ensure the AILA_API_KEY environment variable is set
  • Try creating a new API key in Settings > API Keys

Advanced Configuration

Batch Processing

For analyzing many calls, use pagination efficiently:

Approach 1: Iterate through pages

List my calls page by page:
- Get page 1 (20 calls)
- Analyze key themes
- Get page 2
- Continue until all calls are analyzed

Approach 2: Targeted analysis

For each of my last 20 calls:
- Extract prospect company names
- Identify their primary pain point
- Note their budget range
- Create a summary table

Best Practice: Process calls in batches of 10-20 to avoid overwhelming Claude's context window with too many transcripts at once.

Integration with Other Tools

Combine the Aila MCP with other Claude connectors:

Aila + Gmail:

Find calls where we promised to send pricing,
then draft follow-up emails with our latest pricing

Aila + Notion:

Create a Notion database of key calls with links to recordings

Aila + Linear:

Extract product feedback from customer calls and create Linear tickets

FAQ

Q: What's the difference between OAuth and API key authentication? A: OAuth (via the web interface) is recommended for most users - it's more secure and easier to manage. API key authentication is useful for CLI tools and automation scripts.

Q: Can I use the MCP to modify or delete calls? A: The MCP does not delete calls or transcripts. It can read call data and, for authorized setup users, apply approved changes to Aila configuration such as datasets, routing rules, task triggers, scorecards, and CRM mappings.

Q: Should I copy a long setup prompt into Claude? A: No. Connect the Aila MCP and ask Claude to call getAilaConfigurationSkill. That tool returns the current account-configuration process directly from Aila.

Q: How do I revoke access to the MCP? A: For OAuth: Go to Settings > Connections in your Aila dashboard and disconnect the MCP integration. For API keys: Delete the API key from Settings > API Keys.

Q: What happens if I exceed the rate limit? A: The MCP will return an error. Wait a few seconds and try again. Contact support if you need higher rate limits.

Q: Can multiple people in my organization use the MCP? A: Yes, each user should connect the MCP to their own Claude account. They'll only have access to calls they have permissions to view in Aila.

Q: Does the MCP work with all call types? A: Yes, the MCP works with calls from all sources (Google Meet, Zoom, Teams, OpenPhone, manual uploads, etc.) as long as they have transcripts.

Q: Which client should I use? A: Claude Desktop is recommended for most users due to its easy OAuth setup. Use CLI tools with API keys if you need automation or don't use a desktop client.

Known Limitations

Current limitations of the Aila MCP:

  • Call Limit: Maximum 50 calls per query (use pagination for more)
  • Pagination: Results are paginated - use the page parameter to access additional calls
  • Transcript Formats: Some calls may not have all three transcript formats available
    • The tool automatically falls back to available formats: identified → diarized → raw
  • Call States: Only completed calls are returned by list_calls
  • Real-time Access: New calls may take 1-2 minutes to appear via MCP after processing completes
  • Standalone Package Scope: The npm package path may expose only core call-data tools. Use the hosted endpoint for guided account configuration tools.
  • Explicit Approval Required: Configuration tools should be used only after you approve the proposed changes in your MCP client

Getting Help

If you encounter issues with the Aila MCP:

  1. Check this documentation for troubleshooting steps
  2. Verify your Aila account settings
  3. Review the Changelog for recent updates
  4. Contact Aila support:
    • Email: support@aila.fyi
    • Include: Account email, description of issue, screenshots, error messages

Next Steps

Now that you've connected the Aila MCP:

  • Ask your agent to call getAilaConfigurationSkill if you want help configuring Aila from real calls
  • Explore Call Library to understand your call data structure
  • Review Custom Datasets for structured data extraction
  • Check out Call Quality for QA checklist automation
  • Learn about Coaching workflows you can augment with Claude

Related Documentation

OverviewGoHighLevel