scribefy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRIBEFY_API_KEY | Yes | Your Scribefy API key for authentication. | |
| SCRIBEFY_API_BASE | No | Base URL for the Scribefy API. | https://api.scribefy.app |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_transcriptA | Pulls the transcript of a YouTube video and returns it as Markdown with timestamps. Use this whenever the user provides a YouTube URL and wants to summarise, quote, search, or otherwise process the video's spoken content. Costs credits on first fetch (1 credit ≤15min, 2 credits 15–45min, 4 credits 45min–2h, 8 credits 2h+). Cached extractions are free — videos other Scribefy users have already extracted are cached for 30 days. Returns the title, channel, duration, language, and the transcript itself split into segments with clickable timestamps. |
| search_videosA | Search YouTube for videos matching a query string. Returns up to |
| get_video_metadataA | Look up title, channel, duration, view count, upload date, and available caption tracks for a video. Does NOT pull the transcript — use extract_transcript for that. Free — no credits charged. Useful to inspect a video before deciding whether to extract, or to discover which caption languages are available. |
| get_related_videosA | Return the videos YouTube recommends after a given video — the 'Up next' / 'Related' feed. Returns up to |
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 has a clearly distinct purpose: extracting transcripts, getting related videos, retrieving metadata, and searching. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., extract_transcript, get_related_videos). The verbs vary but the pattern is uniform.
With 4 tools, the server is well-scoped for its purpose of YouTube video processing. The count is neither too thin nor too heavy.
The tool set covers the full workflow: search, metadata inspection, transcript extraction, and discovery of related content. No obvious gaps for the intended use case.