Skip to main content
Glama
txscribe-ai

txscribe MCP Server

Official
by txscribe-ai

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TXSCRIBE_API_KEYYesYour txscribe API key (starts with txs_live_…)
TXSCRIBE_API_BASENoPoints the server at another deploymenthttps://txscribe.ai/api/v1

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_transcriptionsA

The account's transcriptions, newest first. Pass the previous page's nextCursor to read on.

transcribe_linkA

Create a transcription from a link to a video or recording (YouTube, Google Drive, Dropbox and others; the recording is transcribed, never downloaded). Starts at once and uses the account's minutes. Returns the transcription with its id; poll get_transcription until status is done, then read get_transcript.

search_transcriptionsA

Which of the account's recordings said something, and when. Looks for the words as one phrase in what was said (not in titles), in the newest 500 recordings (ones still processing or failed among them are skipped; truncated is true when there may be older ones, which are not read): give a distinctive word or short phrase, not a question. Each result has up to five matches with the second each starts at; read around one with get_transcript's from and to rather than reading the whole transcript.

get_transcriptionB

Status and metadata of one transcription: fetching, uploading, preparing, transcribing, done or error.

get_transcriptA

The finished transcript. json gives segments with word timings and speakers (what the app shows); txt, srt and vtt give the file the app's Export menu makes. A long recording is a lot of text: pass from and to (seconds) for only the paragraphs around a moment, such as a match from search_transcriptions, or summaryOnly for the summary instead. Not ready yet answers with the not_ready error; check get_transcription first.

get_summaryA

The summary of a finished transcription and its status. Ask for one with request_summary if there is none yet.

request_summaryA

Ask for a summary of a finished transcription, or a new one. Returns at once with status generating; read it with get_summary.

delete_transcriptionA

Delete a transcription, its media and everything made from it. Cannot be undone.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 8 tools

Disambiguation4/5

Each tool maps to a distinct operation, but the trio get_transcription (status/metadata), get_transcript (content) and get_summary (summary) shares similar names and resource focus, so an agent must read descriptions carefully to pick correctly. The descriptions do explicitly disambiguate (e.g., 'Not ready yet... check get_transcription first'), keeping overlap manageable.

Naming Consistency5/5

All eight tools follow a consistent snake_case verb_noun pattern: list_transcriptions, get_transcript, get_summary, request_summary, delete_transcription, transcribe_link, search_transcriptions, get_transcription. Verbs are used predictably (get_ for reads, request_ for creating async work, delete_ for removal).

Tool Count5/5

Eight tools is well-scoped for a transcription service, with each tool earning its place across listing, creation, status polling, content retrieval, search, summarization, and deletion. No redundant or filler tools.

Completeness4/5

The lifecycle is largely covered: create via link, poll status, retrieve transcript in multiple formats, summarize, search, and delete. Minor gaps exist—there is no tool for directly uploading a local media file (despite an 'uploading' status) and no rename/update metadata operation.

Maintenance

ActivityMaintained
ResponsivenessNo issues