TTS MCP Server
Text-to-speech MCP server using Microsoft Edge TTS, supporting multiple voices and async processing.
README
VoiceOver MCP Server
Server exposing three MCP tools over Streamable HTTP + legacy SSE, plus a matching REST API:
voice_over— text-to-speech.visual_creator— turns a checklist of code/command entries into VS Code-style code screenshots and terminal-style command screenshots (PNG/SVG), for coding vlogs.video_renderer— stitches a project's syncedvoice_overnarration +visual_creatorscreenshots into a single MP4, via ffmpeg.
Generated files (MP3s, images, MP4s) are written to a temp directory (safe for ephemeral disks on Render/Railway/Fly/etc.) and served back over HTTP so any LLM client or frontend can fetch them.
Project layout
The codebase is organized one directory per tool, so each tool's core
logic, MCP schema, MCP handler, and tests live together — adding a fourth
tool means adding one new directory under tools/, not touching four
scattered files.
common/ # shared across all tools
├── config.py # all env-var configuration in one place
├── files.py # filename generation, temp-path resolution, cleanup
├── logging.py # in-memory request log
├── formatting.py # file-size + timestamp helpers
└── project_store.py # manifest/order sync layer (shared by all 3 tools)
tools/ # one self-contained directory per MCP tool
├── voice_over/
│ ├── core.py # generate_audio_core, TTSGenerationError (edge-tts wrapper)
│ ├── schema.py # MCP Tool() inputSchema definition
│ ├── handler.py # MCP call_tool logic for this tool
│ └── tests/
│ └── test_tts_core.py
│
├── visual_creator/
│ ├── core.py # generate_visuals_core, VisualCreatorError
│ ├── schema.py
│ ├── handler.py
│ ├── rasterize.py # SVG -> PNG rasterizer
│ ├── vlogshot/ # vendored screenshot-rendering package (see below)
│ └── tests/
│ ├── test_visual_core.py
│ └── test_rasterize.py
│
└── video_renderer/
├── core.py # render_project_video, VideoRenderError (ffmpeg pipeline)
├── schema.py
├── handler.py
└── tests/
└── test_render_core.py
mcp_layer/ # MCP protocol/transport only — no tool-specific logic
├── server.py # Server("voiceover-mcp-server") instance
├── registry.py # aggregates each tool's schema.py + handler.py
├── errors.py # shared {"success": false, "error": ...} helper
├── sse_asgi.py # legacy SSE transport
├── streamable_http_asgi.py # Streamable HTTP transport
└── tests/
├── test_mcp_handlers.py
└── test_mcp_transport.py
api/ # REST layer only — imports from tools/*/core.py directly
├── app.py # FastAPI app factory: middleware, lifespan, routers
├── models.py # TTSRequest / TTSResponse Pydantic models
├── routes/ # one file per resource
│ ├── root.py # GET / , GET /health
│ ├── tts.py # POST /api/v1/tts
│ ├── voices.py # GET /api/v1/voices
│ ├── audio.py # GET /api/v1/audio/{filename}
│ ├── visuals.py # GET /api/v1/visual/{filename}
│ ├── projects.py # GET /api/v1/project(s), .../video
│ └── logs.py # GET /api/v1/logs
└── tests/
├── test_routes_misc.py
├── test_routes_tts.py
└── test_routes_projects.py
tests/ # cross-cutting tests only (shared fixtures, project_store)
├── test_files.py
├── test_formatting.py
└── test_project_store.py
conftest.py # project-root pytest fixtures (e.g. `client`), shared by every test dir above
run.py # entry point
tools/visual_creator/vlogshot/ is a vendored copy of the standalone
vlog_screenshot_tool CLI project — same rendering code (checklist parsing,
zip extraction, SVG rendering, themes, fonts), reused here as a library
instead of being invoked as a subprocess.
See each tool's own README for details specific to that tool:
tools/voice_over/README.md ·
tools/visual_creator/README.md ·
tools/video_renderer/README.md
Run it
pip install -r requirements.txt
cp .env.example .env # edit as needed
python run.py
Server starts on http://0.0.0.0:8080 by default. Docs at /docs.
MCP tools
Connect an MCP client to /mcp (Streamable HTTP) or /mcp/sse (legacy
SSE). All three tools below are exposed on the same server; each is
documented in full in its own tools/{name}/README.md.
voice_over
- Input:
text(required),voice,rate,pitch,volume,output_filename, and optionallyproject_id+order+labelto group this clip with a matchingvisual_creatorscreenshot for later sync. - Output:
{ "success": true, "content": "<original text>", "filename": "<name>.mp3", "timestamp": "..." }
The tool does not return audio bytes or a filesystem path — only the
filename. Fetch the actual file with GET /api/v1/audio/{filename}.
visual_creator
- Input:
checklist(required) — array of entries, each one of:- a zip-lookup code entry:
{file, start_line, end_line, label} - an inline code entry (no zip needed):
{path, start_line, code, label} - a command entry (no zip needed):
{type: "command", command, output, label}
- a zip-lookup code entry:
zip_base64— base64-encoded project zip; required only ifchecklisthas at least one zip-lookup code entrytheme(dark/light/high-contrast, defaultdark)style(vscode/minimal, defaultvscode)font_size(default22),width(default1920),height(default1080)output_format(png/svg/both, defaultpng)- optionally
project_id(matched tovoice_overcalls by each checklist entry's ownorder)
- Output:
{ "success": true, "results": [{order, label, status, detail}, ...], "files": ["<name>.png", ...], "download_url_template": "/api/v1/visual/{filename}", "timestamp": "..." }
One bad entry never fails the whole call — results[i].status is OK,
CLIPPED, or SKIPPED (reason) per entry. Fetch each generated file with
GET /api/v1/visual/{filename}.
video_renderer
- Input:
project_id(required — must have matchingvoice_over+visual_creatorcalls already made against it),transition(cutdefault /crossfade),crossfade_seconds(default0.5). - Output:
{ "success": true, "filename": "final_output.mp4", "total_duration_seconds": ..., "orders": [...], "warnings": [...], "download_url": "/api/v1/project/{project_id}/video", "timestamp": "..." }
Reads the project's manifest (written by voice_over/visual_creator),
holds each order's screenshot(s) on screen for that order's narration
duration, and concatenates every order into one MP4. Orders missing either
audio or visual are skipped with a warning, not a hard failure. Fetch the
result with GET /api/v1/project/{project_id}/video.
REST API (mirrors the MCP tools 1:1)
| Method | Path | Purpose |
|---|---|---|
| GET | / |
Service info |
| GET | /health |
Health + temp dir status |
| GET/POST/DELETE | /mcp |
MCP Streamable HTTP transport |
| GET | /mcp/sse |
MCP legacy SSE transport |
| POST | /api/v1/tts |
Generate speech, returns filename + download URL |
| GET | /api/v1/voices |
List/filter available edge-tts voices |
| GET | /api/v1/audio/{filename} |
Download/stream a generated clip |
| GET | /api/v1/visual/{filename} |
Download a generated screenshot |
| GET | /api/v1/projects |
List known project_ids |
| GET | /api/v1/project/{project_id} |
Get a project's manifest |
| GET | /api/v1/project/{project_id}/{order}/{filename} |
Download one order's audio/visual file |
| GET | /api/v1/project/{project_id}/video |
Download the rendered MP4 (video_renderer output) |
| GET | /api/v1/logs |
Recent request log (monitoring) |
Storage model
- All audio, visuals, and rendered videos are written to a single ephemeral
temp directory (
TEMP_DIR, defaults to the OS temp dir +voiceover_mcp); visuals go in avisuals/subfolder, project-synced files (includingvideo_renderer's output) go under aprojects/subfolder. - Filenames are sanitized and resolved with
Path(...).nameonly — no path traversal viaoutput_filename, checklist entries, or any download route. - Each
visual_creatorcall gets a short random filename prefix, so repeat calls (even with identical labels) never overwrite each other's output. AUDIO_TTL_SECONDS/VISUAL_TTL_SECONDS/ project TTL (seecommon/config.py) control a startup cleanup sweep that deletes stale files.- Because storage is ephemeral, files will not survive a server restart on most PaaS platforms — by design. Download endpoints return a clear 404 if a file has expired or the instance was recycled.
Testing
python -m pytest -v
pyproject.toml's testpaths covers tests/, tools/, mcp_layer/, and
api/, so this one command discovers every test across the whole tree —
each tool's own tests, the MCP dispatch tests, the REST route tests, and
the shared/cross-cutting tests all run together. Currently 102 tests.
Covers: filename/path safety, TTS core logic (edge-tts mocked, no real
network calls), visual_creator core rendering logic (inline code,
command, and zip-lookup entries; bad-input errors), video_renderer's
manifest-to-segments logic and ffmpeg pipeline (mocked subprocess calls
plus real end-to-end renders when ffmpeg is available), all three MCP tool
handlers, and all REST routes.
Environment variables
See .env.example. Key ones:
PORT,HOST— server bindingTEMP_DIR— override the shared audio/visuals/projects temp directoryAUDIO_TTL_SECONDS,VISUAL_TTL_SECONDS— cleanup age thresholdsDEFAULT_VOICE,DEFAULT_RATE,DEFAULT_PITCH,DEFAULT_VOLUME— TTS defaultsFFMPEG_BINARY— override the ffmpeg binaryvideo_renderershells out to (defaults to the static binary bundled byimageio-ffmpeg, since this deploys on Render's Dockerfile-less native Python runtime)DEFAULT_TRANSITION,CROSSFADE_SECONDS,RENDER_TIMEOUT_SECONDS—video_rendererdefaults
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。