mcp-transkriptor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSKRIPTOR_API_KEY | Yes | Your Transkriptor API key from https://developer.transkriptor.com | |
| TRANSKRIPTOR_ALLOWED_DIR | No | Sandbox directory for transcribe_local_file. Defaults to process working directory. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| transcribe_urlA | Transcribe a publicly accessible URL, such as YouTube, Google Drive, Dropbox, or OneDrive. Returns an order_id used to check results later. |
| transcribe_local_fileA | Upload and transcribe a local audio/video file. The file must be inside TRANSKRIPTOR_ALLOWED_DIR. Returns an order_id used to check results later. |
| transcribe_meetingB | Send Transkriptor bot to a Google Meet, Microsoft Teams, or Zoom meeting. Returns an order_id. |
| get_file_contentC | Get completed transcription content by order_id. |
| get_file_detailB | Get metadata/details for a transcription file by order_id. |
| get_meeting_detailC | Get meeting details by meeting order_id. |
| list_filesA | List files in the Transkriptor account. Without folder_id, returns root/unfiled files only. Pass a folder_id (from list_folders) to list files inside that folder. |
| list_foldersA | List folders in the Transkriptor account. Each item has folder_id and folder_name. |
| get_user_detailsA | Get Transkriptor account/user details, such as remaining minutes. |
| get_summaryB | Get AI-generated summary for a transcription. Not every transcription has a summary. |
| export_transcriptionC | Export a transcription as txt, srt, pdf, or docx. |
| rename_fileC | Rename an existing transcription file. |
| delete_fileC | Delete all files associated with an order_id. Use carefully. |
| set_custom_vocabularyA | Replace custom vocabulary with the provided words/phrases. Maximum 1000 words/phrases. Maximum 6 words per phrase. |
| get_custom_vocabularyA | Get current custom vocabulary. |
| delete_custom_vocabularyB | Delete current custom vocabulary. |
| create_webhookB | Register a webhook URL for completed transcriptions. Your webhook URL must be reachable by Transkriptor. |
| list_webhooksA | List all webhooks, or view a specific webhook by webhookType. |
| delete_webhookB | Delete a webhook by webhookType. |
| text_to_speechA | Generate speech from text. Pro voices may support emotion; Lite voices do not. |
| list_knowledgebasesB | List AI Chat knowledgebases. |
| create_knowledgebaseC | Create an AI Chat knowledgebase. |
| add_file_to_knowledgebaseC | Add a Transkriptor transcription file to an AI Chat knowledgebase. |
| create_chat_sessionC | Create a chat session inside a knowledgebase. |
| chat_with_knowledgebaseC | Send a message to an AI Chat knowledgebase session. |
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 25 tools
Every tool targets a distinct operation on different entities (transcription, file, vocabulary, webhook, knowledgebase), with no overlapping functionality. The descriptions clearly differentiate their purposes.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_knowledgebase, list_files, transcribe_url), with no mixing of conventions or vague verbs.
25 tools is on the higher side but still reasonable given the comprehensive feature set (transcription, file management, export, vocabulary, webhooks, knowledgebase, TTS). Each tool serves a clear purpose without bloat.
The tool surface covers core transcription lifecycle, file operations, vocabulary management, webhooks, and knowledgebase chat. Minor gaps like missing cancellation or status polling tools, but overall well-rounded.