Transcript MCP spike
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Listen port (default 3000) | 3000 |
| MCP_TRANSPORT | No | Set to 'http' to use Streamable HTTP transport (same as passing --http) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_transcriptsA | List transcript metadata. Optionally filter by participant or tag. |
| get_transcriptA | Get one complete transcript by its ID. |
| search_transcriptsA | Search titles, participants, tags, speakers, and spoken transcript text. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all-transcripts | The complete mock transcript dataset as JSON |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing metadata, retrieving a single transcript by ID, and searching across transcript content. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (list_transcripts, get_transcript, search_transcripts), with minor singular/plural variation that does not undermine the pattern.
Three tools is a well-scoped set for a transcript retrieval service, covering the essential read operations without unnecessary bloat.
The read side is well covered (list, get, search), but write operations like create, update, or delete are absent. For a 'spike' server, this is a minor gap.