Connect AI tools (MCP)
Overview
The Model Context Protocol - or MCP - lets compatible AI clients list and call Lungoor Notes tools. This server gives you read-only access to your meetings from Cursor, Claude Desktop, or any client that supports SSE and Bearer token authentication. Every response is scoped to your signed-in user account. There are no tools that allow writing or deleting data.
Prerequisites
To use MCP, make sure you have the Lungoor Notes desktop app installed and signed in. You'll also need the backend MCP service URL: https://backend-lungoor-notes.lungoor.ai/mcp/sse
Generate an API Token
Follow these steps to create a connection token:
- Open the desktop app, go to Settings, and select AI tools.
- Click Generate token.
- Label your token so you know which device uses it.
- Copy the token immediately and save it somewhere secure. It won't be shown again.
Tokens expire after 90 days, but you can revoke them anytime in the app if you lose your device or leak a configuration file.
Client Configuration
To configure your AI client, replace the placeholder token in the configuration files with your active API token.
Cursor Setup
Add the following configuration block under the mcpServers key in your ~/.cursor/mcp.json file:
{
"mcpServers": {
"meetings": {
"type": "sse",
"url": "https://backend-lungoor-notes.lungoor.ai/mcp/sse",
"headers": {
"Authorization": "Bearer YOUR_TOKEN_HERE"
}
}
}
}Claude Desktop Setup
- Generate a token in Lungoor Notes and copy it. This token is shown only once.
- Open Claude Desktop - Settings - Connectors - Add - Add custom connector.
Set the name (default Lungoor, or any name you prefer) and the URL, then click Add.
CUSTOM CONNECTOR Name: Lungoor URL: https://backend-lungoor-notes.lungoor.ai/mcp/sse
Paste the token into the next input, then click Allow Claude to connect.
- Open Chat or Co-work, enable the Lungoor connector from the + menu if needed, then use it to ask about your meetings.
How It Works
Your client establishes a connection by opening a GET request to the SSE endpoint with your Bearer token. It then sends JSON-RPC messages on a POST request with the same token. All tool calls run securely, scoped directly to your unique user ID.
The system enforces a rate limit of 120 requests per minute per token, with a maximum of 3 concurrent SSE connections.
Tool Reference
Here are the available tools you can call through MCP:
Meetings (8 Tools)
| Tool Name | When to Use |
|---|---|
| getMeetings | Use this to get a baseline list of meetings, sorted newest first. This is best when you don't have a person, date, or text filter in mind yet. |
| getRecentMeetings | Use this for a quick look at your latest activity. It is faster than getMeetings when you only need recent sessions. |
| getMeetingsByDateRange | Use this to retrieve meetings within a specific time window. This is ideal when the user provides a clear date range. |
| getMeetingDetail | Use this to retrieve canonical metadata, participant lists, summaries, and meeting references for a single session. |
| getMeetingTranscript | Use this for deep Q&A or extracting evidence. Since transcripts are heavier, avoid this for simple list tasks. |
| getMeetingNotes | Use this when the answer depends on your own typed notes rather than the automated transcript or summary. |
| searchMeetings | Use this as a fallback text search on titles and summaries when the folder or date scope is unknown. |
| getMeetingMarkdown | Use this single-call tool to export the summary, transcript, and notes in markdown format for easy sharing. |
Folders (5 Tools)
| Tool Name | When to Use |
|---|---|
| getFolders | Use this as an entry point to discover folders when searching by project or topic before you list individual meetings. |
| getFolderDetail | Use this to resolve metadata and linked sessions for a single folder using its unique ID. |
| getMeetingsInFolder | Use this as your primary tool to list meetings once you know the folder context. |
| suggestMeetingsForFolder | Use this helper tool to get recommendations for organizing existing meetings into a folder. |
| suggestNewFolders | Use this to discover emerging themes and cluster suggestions from your meeting patterns. |
Insights, Recipes, and People (6 Tools)
| Tool Name | Category | When to Use |
|---|---|---|
| getCrossMeetingInsights | Insights | Use this for high-level analytics, trend analysis, and portfolio-level KPIs across multiple meetings. |
| listMeetingRecipes | Recipes | Use this to list all the automation templates and custom prompt recipes available in your workspace. |
| getMeetingRecipe | Recipes | Use this to fetch the details of a specific recipe using its unique ID. |
| getConnectedPeople | People | Use this as a first step to resolve contacts when someone asks about meetings with a specific person. |
| getOrganizationPeople | People | Use this for directory-wide lookups or to resolve people when contacts aren't found in your immediate history. |
| getPersonInteractions | People | Use this to fetch interactions and meetings associated with a resolved person, then filter by date or text. |
Related
Tips
If you lose a device or expose a configuration file, go to Settings immediately and revoke that API token to secure your account.