kedimeet-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
KediMeet holds the user's recorded work calls: transcripts by speaker and summaries (decisions, tasks, open questions). When a question is about what was discussed, decided or agreed, who assigned or promised what, deadlines, the status of tasks and projects, or colleagues and their positions — look here first (search), then answer. In the answer, name the meeting and its date, and for quotes give the time in the recording.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the user's work calls: transcripts (who said what) and summaries (decisions, tasks, open questions). Use it first when a question is about what was discussed, decided or agreed, who assigned or promised what, deadlines, the status of tasks and projects, or colleagues. People ask things like "What did we decide about pricing?", "What did Maya promise to send me?", "When did we last talk about the API migration?", "Did anyone push back on the Thursday release?" Matches words with different endings. Ranked by how many query words matched, then newest first. Then read what you found with get_meeting and get_transcript. Read-only. |
| list_meetingsA | Meetings in a period, newest first: title, date, participants and the main point of the summary. For questions like "What calls did I have this week?", "Catch me up on yesterday's meetings", "When did I last talk to Daniel?" Read-only. |
| get_meetingA | The full summary of a meeting: the short version, decisions, tasks (marked done or not), open questions, participants and how much each of them spoke, the call link, and the notes the user wrote for the meeting. For "What are my action items from the Northwind call?", "Write a follow-up email after today's sync", "Which tasks from Monday are still open?" Read-only. |
| get_transcriptA | The transcript turn by turn: "[time] Name: text". For exact wording and context: "What exactly did Priya say about the deadline?", "Quote the client's objection". Read a long meeting (an hour is about 60,000 characters) in pieces around the place search pointed to. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct retrieval mode: keyword search across content, chronological listing of meetings, full summary of one meeting, and verbatim transcript of one meeting. The search description explicitly routes the agent ('Use it first... Then read what you found with get_meeting and get_transcript'), and get_meeting vs get_transcript are cleanly separated by summary vs exact wording.
Three of four tools follow a clear verb_noun pattern (list_meetings, get_meeting, get_transcript). The bare 'search' lacks an object noun, a minor deviation but consistent with the otherwise verb-first convention and unlikely to confuse.
Four tools is a well-scoped surface for a read-only meeting-knowledge server: find, browse, summarize, and quote. Each tool covers a genuinely different access path with no filler.
The retrieval lifecycle is well covered, but the surface is entirely read-only: no way to create notes, mark tasks done, or draft follow-ups despite tasks and action items being first-class content in the summaries. Agents asking 'mark that task complete' hit a dead end.