Deep-dive into the Keep It Krispy MCP server for Claude integration.
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.
Connect Claude to your meeting data in under a minute. Choose your client below.
Claude Desktop stores its configuration in a JSON file on your machine:
| Platform | Config File Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
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"
}
}
}
}
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.
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"
Confirm the server was added:
claude mcp list
You should see krisp in the list of configured MCP servers.
claude "what was my last meeting about?"
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.
List recent meetings with metadata including title, date, duration, and speakers. Filter by date range or speaker name.
| Param | Type | Description |
|---|---|---|
start_date | string | Filter from date (YYYY-MM-DD) |
end_date | string | Filter to date (YYYY-MM-DD) |
speaker | string | Filter by speaker name |
limit | number | Max results (default: 20) |
Semantic search across all your meetings. Finds content by meaning, not just keywords — powered by vector embeddings.
| Param | Type | Description |
|---|---|---|
query | string | Natural language search query (required) |
speaker | string | Filter by speaker name |
from | string | Start date (YYYY-MM-DD) |
to | string | End date (YYYY-MM-DD) |
limit | number | Max results (default: 10) |
Fetch transcript content by meeting IDs. Returns summary, notes, action items, and optionally full text.
| Param | Type | Description |
|---|---|---|
meeting_ids | string[] | Meeting IDs to retrieve (required) |
summary_only | boolean | Skip full transcript text |
Correct or identify speakers in a meeting. Map generic labels like “Speaker 2” to real names.
| Param | Type | Description |
|---|---|---|
meeting_id | string | Meeting to update (required) |
speaker_mappings | object | Map of old name → {name, linkedin?} |
List speakers from your knowledge graph with metadata like names, LinkedIn URLs, and company affiliations.
| Param | Type | Description |
|---|---|---|
limit | number | Max results (default: 50) |
company | string | Filter by company name |
List companies extracted from your meetings.
| Param | Type | Description |
|---|---|---|
limit | number | Max results (default: 50) |
Get comprehensive context about a speaker including their enriched profile, LinkedIn match, and meeting history.
| Param | Type | Description |
|---|---|---|
speaker_name | string | Name of the speaker (required) |
List imported LinkedIn connections that can be matched to meeting speakers.
| Param | Type | Description |
|---|---|---|
limit | number | Max results (default: 50) |
search | string | Search by name (partial match) |
Find a LinkedIn 1st-degree connection that matches a speaker name.
| Param | Type | Description |
|---|---|---|
speaker_name | string | Speaker name to match (required) |
company_hint | string | Company name to improve accuracy |
List action items extracted from meetings. Filter by status, assignee, or due date.
| Param | Type | Description |
|---|---|---|
status | string | pending, in_progress, completed, cancelled |
assignee | string | Filter by assignee name |
due_before | string | Due before date (YYYY-MM-DD) |
due_after | string | Due after date (YYYY-MM-DD) |
limit | number | Max results (default: 20) |
Update an action item’s status, assignee, or due date.
| Param | Type | Description |
|---|---|---|
entity_id | string | Action item entity ID (required) |
status | string | New status |
assignee | string | New assignee name |
due_date | string | New due date (YYYY-MM-DD) |
List decisions made during your meetings — explicit agreements, approvals, or choices.
| Param | Type | Description |
|---|---|---|
from_date | string | Start date (YYYY-MM-DD) |
to_date | string | End date (YYYY-MM-DD) |
participant | string | Filter by participant name |
limit | number | Max results (default: 20) |
Get a meeting preparation briefing for a contact. Aggregates your history: last meeting, topics, open items, and decisions.
| Param | Type | Description |
|---|---|---|
contact | string | Name of the person (required) |
Test MCP server connectivity and verify the API is reachable. Returns health status and latency.
| Param | Type | Description |
|---|---|---|
| No parameters | ||
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.
Sign in to the Keep It Krispy dashboard and navigate to Settings. Your API Key is displayed on the page.
Common issues and how to resolve them.
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.
Double-check that your X-API-Key header value matches the API key from your dashboard. You can verify it on the Settings page.
Verify the MCP server URL is correct. Try curl https://eneiq5vwovjqz7ahuwvu3ziwqi0bpttn.lambda-url.us-east-1.on.aws/health — you should get {"status":"healthy"}.
Open an issue on GitHub with details about your setup and the error you are seeing. Include your MCP client version and OS.