What is MCP?

Model Context Protocol (MCP) is the open standard for connecting AI assistants to external tools and data sources. It lets Claude call structured tools, query databases, and take actions on your behalf — all through a secure, well-defined interface.

The Keep It Krispy MCP server is a Lambda-hosted HTTP server that gives Claude direct access to your meeting data: transcripts, speakers, companies, and the knowledge graph that connects them. No local setup or AWS credentials required — just point your MCP client at the endpoint and authenticate with your API Key.

Configuration

Connect Claude to your meeting data in under a minute. Choose your client below.

1. Open Your Config File

Claude Desktop stores its configuration in a JSON file on your machine:

PlatformConfig File Path
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json

2. Add the MCP Server

Paste the following into your config file, replacing YOUR_API_KEY with your API Key from the dashboard settings:

{
  "mcpServers": {
    "krisp": {
      "url": "https://eneiq5vwovjqz7ahuwvu3ziwqi0bpttn.lambda-url.us-east-1.on.aws/",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

3. Restart Claude Desktop

Quit Claude Desktop completely (Cmd+Q on macOS, Alt+F4 on Windows) and reopen it. The krisp server should appear in your MCP tools list.

Tip: You can find your API Key on the Settings page of the Keep It Krispy dashboard.

1. Add the MCP Server

Run a single command to register the server. Replace YOUR_API_KEY with your API Key from the dashboard settings:

claude mcp add --transport http krisp https://eneiq5vwovjqz7ahuwvu3ziwqi0bpttn.lambda-url.us-east-1.on.aws/ --header "X-API-Key: YOUR_API_KEY"

2. Verify

Confirm the server was added:

claude mcp list

You should see krisp in the list of configured MCP servers.

Done! Start a Claude Code session and ask about your meetings — e.g., claude "what was my last meeting about?"

Available Tools

The MCP server exposes 14 tools that Claude can call on your behalf. They are organized into three groups: transcript operations, knowledge graph queries, and productivity tools.

Transcript Tools

list_transcripts

List recent meetings with metadata including title, date, duration, and speakers. Filter by date range or speaker name.

ParamTypeDescription
start_datestringFilter from date (YYYY-MM-DD)
end_datestringFilter to date (YYYY-MM-DD)
speakerstringFilter by speaker name
limitnumberMax results (default: 20)

search_transcripts

Semantic search across all your meetings. Finds content by meaning, not just keywords — powered by vector embeddings.

ParamTypeDescription
querystringNatural language search query (required)
speakerstringFilter by speaker name
fromstringStart date (YYYY-MM-DD)
tostringEnd date (YYYY-MM-DD)
limitnumberMax results (default: 10)

get_transcripts

Fetch transcript content by meeting IDs. Returns summary, notes, action items, and optionally full text.

ParamTypeDescription
meeting_idsstring[]Meeting IDs to retrieve (required)
summary_onlybooleanSkip full transcript text

update_speakers

Correct or identify speakers in a meeting. Map generic labels like “Speaker 2” to real names.

ParamTypeDescription
meeting_idstringMeeting to update (required)
speaker_mappingsobjectMap of old name → {name, linkedin?}

Knowledge Graph Tools

list_speakers

List speakers from your knowledge graph with metadata like names, LinkedIn URLs, and company affiliations.

ParamTypeDescription
limitnumberMax results (default: 50)
companystringFilter by company name

list_companies

List companies extracted from your meetings.

ParamTypeDescription
limitnumberMax results (default: 50)

get_speaker_context

Get comprehensive context about a speaker including their enriched profile, LinkedIn match, and meeting history.

ParamTypeDescription
speaker_namestringName of the speaker (required)

list_linkedin_connections

List imported LinkedIn connections that can be matched to meeting speakers.

ParamTypeDescription
limitnumberMax results (default: 50)
searchstringSearch by name (partial match)

match_linkedin_connection

Find a LinkedIn 1st-degree connection that matches a speaker name.

ParamTypeDescription
speaker_namestringSpeaker name to match (required)
company_hintstringCompany name to improve accuracy

Productivity Tools

list_action_items

List action items extracted from meetings. Filter by status, assignee, or due date.

ParamTypeDescription
statusstringpending, in_progress, completed, cancelled
assigneestringFilter by assignee name
due_beforestringDue before date (YYYY-MM-DD)
due_afterstringDue after date (YYYY-MM-DD)
limitnumberMax results (default: 20)

update_action_item

Update an action item’s status, assignee, or due date.

ParamTypeDescription
entity_idstringAction item entity ID (required)
statusstringNew status
assigneestringNew assignee name
due_datestringNew due date (YYYY-MM-DD)

list_decisions

List decisions made during your meetings — explicit agreements, approvals, or choices.

ParamTypeDescription
from_datestringStart date (YYYY-MM-DD)
to_datestringEnd date (YYYY-MM-DD)
participantstringFilter by participant name
limitnumberMax results (default: 20)

meeting_prep

Get a meeting preparation briefing for a contact. Aggregates your history: last meeting, topics, open items, and decisions.

ParamTypeDescription
contactstringName of the person (required)

test_connection

Test MCP server connectivity and verify the API is reachable. Returns health status and latency.

ParamTypeDescription
No parameters

Authentication

The MCP server uses your API Key to authenticate requests and enforce multi-tenant data isolation. Every request must include the X-API-Key header, which ensures you only ever see your own meeting data.

Where to Find Your API Key

Sign in to the Keep It Krispy dashboard and navigate to Settings. Your API Key is displayed on the page.

Keep your API Key private. Anyone with your API Key and the MCP endpoint URL could query your meeting data. Treat it like a password.

Troubleshooting

Common issues and how to resolve them.

Claude can't find the server

Restart Claude Desktop completely after making config changes. On macOS use Cmd+Q (not just closing the window). On Windows use Alt+F4 or quit from the system tray.

No transcripts returned

Double-check that your X-API-Key header value matches the API key from your dashboard. You can verify it on the Settings page.

Tools not showing up

Verify the MCP server URL is correct. Try curl https://eneiq5vwovjqz7ahuwvu3ziwqi0bpttn.lambda-url.us-east-1.on.aws/health — you should get {"status":"healthy"}.

Need help?

Open an issue on GitHub with details about your setup and the error you are seeing. Include your MCP client version and OS.