MCP (Model Context Protocol) Server

MCP (Model Context Protocol) Server

The Salescaling MCP server allows AI agents like Claude, Cursor, and other MCP-compatible clients to access your meeting data, transcripts, and summaries in a structured and secure manner.

What is MCP?

The Model Context Protocol (MCP) is a standard protocol that allows Large Language Models (LLMs) to interact with external systems in a structured way. The Salescaling MCP server implements this protocol to expose your meeting data through tools that AI agents can use.

Features

  • ✅ Spec-Compliant: Full implementation of the official MCP protocol
  • ✅ 14 Available Tools: Meetings (video calls and in-person), phone calls, search, listing, transcription, summary with action items, details, statistics, deep links to the web app, and more
  • ✅ Advanced Search: Full Text Search for content-based searches across meetings and calls
  • ✅ Payload Control: Configurable limits to prevent context overflow
  • ✅ Secure Authentication: Salescaling API key or OAuth Clients (Authorization Code + PKCE)
  • ✅ Multi-tenant: Automatic isolation by organization
  • ✅ High Performance: Optimized for large volumes of activity with concurrency control

MCP Endpoints

The MCP server exposes two main endpoints:

GET /api/v1/mcp - List Tools

Returns the list of available tools with their input schemas.

Example:

bash
curl -X GET https://api.salescaling.com/api/v1/mcp \
  -H "X-API-Key: sk_xxx"

POST /api/v1/mcp - Call Tool

Executes a specific tool with the provided arguments.

Example:

bash
curl -X POST https://api.salescaling.com/api/v1/mcp \
  -H "X-API-Key: sk_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "search_meetings",
    "arguments": {
      "query": "performance",
      "limit": 10
    }
  }'

MCP Connection via OAuth Clients

In addition to the API key, you can connect MCP clients that support OAuth 2.0 (Authorization Code flow with PKCE). The server supports Dynamic Client Registration (DCR), so the client automatically registers its redirect URIs and does not require a manually created client_id or client_secret.

Requirements

  • The MCP client must be able to complete the OAuth flow in the browser and send Authorization: Bearer <access_token> to the MCP server.

Configure the MCP Client

Add only the MCP server URL. Claude or another compatible client will perform the DCR registration and open the consent screen. For Claude (Anthropic), the redirect URI registered by the client is:

https://claude.ai/api/mcp/auth_callback

At a minimum, read access to meetings is requested; the consent screen displays all permissions allowed by your role in the selected tenant, with checkboxes to choose which ones to grant before authorizing.

Authorization Server Metadata

Salescaling exposes OpenID-compatible discovery metadata at the MCP endpoint itself:

  • GET https://api.salescaling.com/.well-known/oauth-protected-resource/api/v1/mcp
  • GET https://api.salescaling.com/.well-known/oauth-authorization-server

There you will find the issuer, authorization_endpoint, token_endpoint, revocation_endpoint, and supported scopes (replace the host if using a different environment).

Example: MCP for Claude with OAuth

Configure the MCP client with the MCP server URL (adjust domains if using a different environment):

json
{
  "mcpServers": {
    "salescaling": {
      "url": "https://api.salescaling.com/api/v1/mcp"
    }
  }
}

Summary of typical URLs

UsageURL
MCP Serverhttps://api.salescaling.com/api/v1/mcp
Authorization (user login)https://app.salescaling.com/oauth/authorize
Token (code exchange / refresh)https://api.salescaling.com/v1/oauth/token
Dynamic Registration (DCR)https://api.salescaling.com/v1/oauth/register

Requests to the MCP will use the access token in the Authorization: Bearer … header instead of X-API-Key.

Meetings vs. Phone Calls

Salescaling stores video calls, in-person meetings, and phone calls under the same meeting entity. To keep the MCP API clear:

  • Tools with meetings in their name (search_meetings, search_meetings_semantic, list_meetings, find_meetings_by_participant) only include video calls and in-person meetings by default (search_meetings_semantic can include calls with includePhoneCalls: true).
  • The tools list_calls, search_calls, and find_calls_by_participant are dedicated to phone calls and support filters such as direction (INBOUND / OUTBOUND) and phone numbers.
  • get_meeting_transcript, get_meeting_summary, get_meeting_details, and get_meeting_action_items work with any meeting or call ID (the same identifier).

Available Tools

Searches video calls and in-person meetings by text in titles and/or transcripts (Full Text Search). Does not include phone calls; use search_calls for that. Transcript search respects the same FGA access as the agent (access_control).

Parameters:

ParameterTypeRequiredDescription
querystringYesSearch term
scopestringNotitle, sentences, or all (default: all)
fromDatestringNoStart date (YYYY-MM-DD)
toDatestringNoEnd date (YYYY-MM-DD)
limitnumberNoMaximum 50 (default: 20)

Note: Only video call or in-person activity types.

Example:

json
{
  "name": "search_meetings",
  "arguments": {
    "query": "performance review",
    "scope": "all",
    "fromDate": "2024-12-01",
    "limit": 10
  }
}

1b. search_meetings_semantic - Topic Search (embeddings)

Same pipeline as the platform agent: embeddings in summary and transcript, compound subqueries, mandatory FGA. Use for natural language questions ("where did we talk about the line cost?"). Excludes phone calls by default.

ParameterTypeRequiredDescription
querystringYesTopic or natural language question
limitnumberNoMaximum 20 (default: 8)
fromDate / toDatestringNoRange by meeting start date
includePhoneCallsbooleanNoInclude phone calls (default: false)

1c. search_memory_statements - Extracted Facts (person facts)

Semantic search on CRM statements (person_fact) with evidenceQuote. Does not require contactId. FGA on the source activity.

ParameterTypeRequiredDescription
querystringYesTopic (pricing, objections, etc.)
limitnumberNoMaximum 20 (default: 8)
canonicalNamespacestringNoOptional filter (pricing, budget, …)

2. list_meetings - List Meetings

Lists video calls and in-person meetings with structured filters (excludes phone calls).

Parameters:

ParameterTypeRequiredDescription
keywordstringNoSearch in names / title
fromDatestringNoStart date
toDatestringNoEnd date
limitnumberNoMaximum 50 (default: 20)
skipnumberNoPagination (default: 0)
sortOrderstringNoasc or desc — sort by start date (default: desc)
participantsstring[]NoParticipant emails
organizersstring[]NoOrganizer emails

Example:

json
{
  "name": "list_meetings",
  "arguments": {
    "fromDate": "2024-12-01",
    "toDate": "2024-12-31",
    "participants": ["client@company.com"],
    "limit": 20
  }
}

3. get_meeting_transcript - Get Transcript

Gets the detailed transcript with speaker attribution (meeting or call).

Parameters:

ParameterTypeRequiredDescription
transcriptIdstringYesMeeting or call ID
languagestringNoLanguage code (e.g., "es", "en")
maxSentencesnumberNoSentence limit (payload control)

Payload Control:

  • Auto-truncates at 10,000 sentences if maxSentences is not specified
  • Indicates in the response if the content was truncated

Example:

json
{
  "name": "get_meeting_transcript",
  "arguments": {
    "transcriptId": "meeting-uuid-here",
    "language": "es",
    "maxSentences": 100
  }
}

4. get_meeting_summary - Get Summary

Gets the AI-generated summary: text (summaryText), action items (actionItems / next_steps), and depending on the type, topics/highlights (meetings) or call insights (calls).

Parameters:

ParameterTypeRequiredDescription
transcriptIdstringYesMeeting or call ID
languagestringNoLanguage code

Example:

json
{
  "name": "get_meeting_summary",
  "arguments": {
    "transcriptId": "meeting-uuid-here",
    "language": "es"
  }
}

5. get_meeting_details - Full Details

Gets full details of a meeting (metadata + transcript + summary).

Parameters:

ParameterTypeRequiredDescription
idstringYesMeeting ID
includeTranscriptbooleanNoInclude transcript (default: true)
includeSummarybooleanNoInclude summary (default: true)
maxSentencesnumberNoSentence limit in transcript

Example:

json
{
  "name": "get_meeting_details",
  "arguments": {
    "id": "meeting-uuid-here",
    "includeTranscript": true,
    "includeSummary": true,
    "maxSentences": 500
  }
}

6. find_meetings_by_participant - Find Meetings by Participant

Finds meetings where a specific person participated. Searches by name (partial match) or email (exact match).

Parameters:

ParameterTypeRequiredDescription
participantstringYesParticipant name or email
fromDatestringNoStart date (YYYY-MM-DD)
toDatestringNoEnd date (YYYY-MM-DD)
limitnumberNoMaximum 50 (default: 20)
skipnumberNoPagination (default: 0)
sortOrderstringNoasc or desc by start date (default: desc)
titleFilterstringNoOptional filter on meeting title (partial match)

Features:

  • Only video calls and in-person meetings (no phone calls).
  • Email search: Exact match (case-insensitive)
    • Example: jon@company.com will find only that exact email
  • Name search: Partial match
    • Example: Jon will find "Jon Smith", "Jonathan", "Jon Doe", etc.
  • Returns full participant and organizer information
  • Sort order configurable with sortOrder

Examples:

Search by email:

json
{
  "name": "find_meetings_by_participant",
  "arguments": {
    "participant": "jon@company.com",
    "fromDate": "2024-12-01",
    "limit": 20
  }
}

Search by name:

json
{
  "name": "find_meetings_by_participant",
  "arguments": {
    "participant": "Jon",
    "fromDate": "2024-01-01",
    "toDate": "2024-12-31",
    "limit": 50
  }
}

7. list_calls - List Phone Calls

Lists only phone calls (phonecall), with filters by date, title, participants, direction, and numbers.

ParameterTypeRequiredDescription
titleFilterstringNoPartial match in name/title
fromDate / toDatestringNoDate range (YYYY-MM-DD)
limitnumberNoMaximum 50 (default: 20)
skipnumberNoPagination
sortOrderstringNoasc or desc (default: desc)
directionstringNoINBOUND or OUTBOUND
participantsstring[]NoParticipant emails
fromNumber / toNumberstringNoPartial filter by caller or destination number

8. search_calls - Search Calls

Search in titles and/or transcripts only for phone calls. Parameters similar to search_meetings, plus optional direction, fromNumber, toNumber.

9. find_calls_by_participant - Calls by Participant

Same as find_meetings_by_participant but only for phone calls, with the same extra filters as list_calls (titleFilter, sortOrder, direction, numbers).

10. get_meeting_action_items - Summary Action Items

Returns the structured next steps from the AI summary for a meeting or call ID.

ParameterTypeRequired
meetingIdstringYes
languagestringNo

11. get_meetings_statistics - Aggregated Statistics

Totals, average durations by activity type, and top participants (limited sample). Configurable scope:

ParameterTypeDescription
fromDate / toDatestringOptional range
typestringmeetings (video+in-person), calls (phone only), or all (default)

Returns an absolute URL to open a resource in the web app (same tenant as the request). Paths aligned with the platform (/meetings, /calls, activities, CRM, etc.).

ParameterTypeRequiredDescription
resourceTypestringYesmeeting, call, activity, contact, company, calendar_event, clip, playlist, library_topic, voice_agent, call_campaign
idstringYesResource ID (UUID or other ID used by the API / URL)
baseUrlstringNohttps origin of the app (e.g., https://app.salescaling.com). Only origins on the server's allowlist are accepted (production and the same host as PLATFORM_URL / NEXT_PUBLIC_URL / FRONTEND_URL in that environment); the value's path is ignored. If omitted: uses those variables or the production default
preferCallDetailbooleanNoOnly with resourceType: "meeting". If true (default) and the meeting is a phone call, the link points to /calls/{callId} instead of /meetings/{id}

Notes:

  • For resourceType: "call", id must be the call row ID (the one used by the /calls/[id] page).
  • For meetings that are phone calls, if you already have the meeting ID and preferCallDetail: true, the server resolves the callId when it exists (respects FGA access like the rest of the tools).
  • The response includes JSON with url, path, resourceType, id, and optionally note (e.g., when linking a phone meeting via /calls/...).

Configuration in MCP Clients

For OAuth (including Claude with redirect https://claude.ai/api/mcp/auth_callback), follow the MCP Connection via OAuth Clients section.

Claude Desktop (API Key)

  1. Locate your configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add the MCP server configuration:

json
{
  "mcpServers": {
    "salescaling": {
      "url": "https://api.salescaling.com/api/v1/mcp",
      "headers": {
        "X-API-Key": "sk_your_api_key_here"
      }
    }
  }
}
  1. Restart Claude Desktop

  2. Verify that the server is connected:

    • Look for the tools icon in the interface
    • You should see "salescaling" as an available server
    • All 14 tools should be listed

Cursor IDE

  1. Open Cursor settings (Cmd/Ctrl + ,)

  2. Search for "MCP Servers" in the settings

  3. Add the Salescaling server:

json
{
  "mcp.servers": {
    "salescaling": {
      "url": "https://api.salescaling.com/api/v1/mcp",
      "headers": {
        "X-API-Key": "sk_your_api_key_here"
      }
    }
  }
}
  1. Restart Cursor

  2. Use the server from the Cursor chat:

    • Mention "@salescaling" in the chat
    • Or ask directly: "Search for meetings about performance"

Other MCP Clients

For any MCP-compatible client:

  1. Server URL: https://api.salescaling.com/api/v1/mcp
  2. Authentication: X-API-Key header with your API key
  3. Protocol: Standard HTTP/HTTPS
  4. Format: JSON

Usage Examples

Example 1: Search Meetings with Claude

text
User: "Search for meetings about pricing from the last month"

Claude → POST /api/v1/mcp
{
  "name": "search_meetings",
  "arguments": {
    "query": "pricing",
    "scope": "all",
    "fromDate": "2024-12-01",
    "limit": 20
  }
}

Claude: "I found 5 meetings about pricing:
1. Pricing meeting with Acme Corp - Dec 15, 2024
2. Pricing strategy review - Dec 10, 2024
..."

Example 2: Get Full Transcript

text
User: "Give me the full transcript of the meeting with ID abc-123"

Claude → POST /api/v1/mcp
{
  "name": "get_meeting_transcript",
  "arguments": {
    "transcriptId": "abc-123",
    "language": "en"
  }
}

Claude: "Here is the meeting transcript:
[00:00 - 00:15] John Doe: Good morning everyone..."

Example 3: Analysis of Multiple Meetings

text
User: "Analyze the sales meetings from December and give me insights"

Claude:
1. List meetings → list_meetings (December)
2. For each meeting → get_meeting_summary
3. Analyze patterns and generate insights

Claude: "I have analyzed 15 meetings from December:
- Most discussed topics: pricing (8), implementation (6)
- Common objections: implementation time (5)
- Identified opportunities: 3 enterprise accounts..."

Response Format

All tools return responses in standard MCP format:

json
{
  "content": [
    {
      "type": "text",
      "text": "Readable description of the result"
    },
    {
      "type": "resource",
      "resource": {
        "uri": "salescaling://meeting/xxx",
        "mimeType": "application/json",
        "text": "{...structured JSON data...}"
      }
    }
  ]
}

Security and Privacy

Authentication

  • Requests require an API key (X-API-Key) or an OAuth access token (Authorization: Bearer) issued for an authorized OAuth Client
  • API keys are managed under Settings > API Keys; OAuth MCP clients are registered automatically via DCR
  • Each credential is linked to your organization (tenant)

Data Isolation

  • The MCP server respects multi-tenant isolation
  • You can only access meetings from your organization
  • Your role and organization permissions are applied automatically

Best Practices

  1. Never share your API key: Treat it like a password
  2. Use environment variables: Do not hardcode the key in files
  3. Rotate keys periodically: Create new keys and delete old ones
  4. Set expiration dates: For temporary or test keys
  5. Monitor usage: Review access logs regularly

Limits and Quotas

Rate Limiting

The MCP server shares the same limits as the public API:

  • Short term: 35 requests per second
  • Medium term: 200 requests every 10 seconds
  • Long term: 1000 requests per minute

Payload Limits

  • Transcripts: Auto-truncates at 10,000 sentences
  • Searches: Maximum 50 results per request
  • Listings: Maximum 50 meetings per request

Use the maxSentences parameter to control transcript size.

Troubleshooting

Error: "Unauthorized - missing or invalid API key"

Cause: Invalid or missing API key

Solution:

  1. Verify that the X-API-Key header is present
  2. Confirm that the key is valid under Settings > API Keys
  3. Verify that the key has not expired

Error: "Unknown tool: xxx"

Cause: Incorrect tool name

Solution:

  1. Verify the tool name (case-sensitive)
  2. Use GET /api/v1/mcp to see available tools
  3. Valid names (among others): search_meetings, search_meetings_semantic, search_memory_statements, list_meetings, get_meeting_transcript, get_meeting_summary, get_meeting_details, find_meetings_by_participant, list_calls, search_calls, find_calls_by_participant, get_meeting_action_items, get_meetings_statistics, build_platform_link

Error: "Meeting not found"

Cause: Meeting ID does not exist or you do not have access

Solution:

  1. Verify that the ID is correct
  2. Confirm that the meeting belongs to your organization
  3. Use list_meetings to get valid IDs

The server does not appear in Claude Desktop

Solution:

  1. Verify that the configuration file is in the correct location
  2. Check that the JSON is valid (no syntax errors)
  3. Restart Claude Desktop completely
  4. Check Claude Desktop logs for errors

Very long responses or timeouts

Solution:

  1. Use maxSentences to limit transcripts
  2. Reduce the limit in searches and listings
  3. Use includeTranscript: false if you only need the summary
  4. Filter by date to reduce the dataset

Support

Need help with the MCP server?

Additional Resources


Last updated: April 2026