DeAPI MCP Server

29 AI tools: audio/video transcription, image generation, TTS, OCR, embeddings via deAPI. Exposed over MCP by the deapi mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Production-ready Model Context Protocol (MCP) server for the deAPI REST API. This server exposes all deAPI AI capabilities as MCP tools, enabling LLMs to perform audio transcription, image generation, OCR, video generation, text-to-speech, and more.

• Complete API Coverage — 39 deAPI tools exposed via MCP, covering every v2 client endpoint
• Smart Adaptive Polling — Automatically polls async jobs with optimized intervals based on job type
• OAuth 2.0 Authentication — Secure token exchange via OAuth Authorization Code flow with PKCE
• Error Recovery — Automatic retry logic with exponential backoff
• Progress Reporting — Real-time progress updates to MCP clients
• Type Safety — Full Pydantic schema validation

Its toolset

Everything the assistant can do here goes through one of these:

• audio_transcription — Transcribe audio files to text using Whisper models
• audio_transcription_price — Calculate transcription cost
• text_to_audio — Convert text to natural speech (TTS)
• text_to_audio_price — Calculate TTS cost
• text_to_music — Generate music from text description and lyrics
• text_to_music_price — Calculate music generation cost
• audio_url_transcription — Transcribe audio from URLs of completed Twitter Spaces
• audio_url_transcription_price — Calculate Twitter Spaces transcription cost
• video_file_transcription — Transcribe video files to text
• video_file_transcription_price — Calculate video file transcription cost
• video_url_transcription — Transcribe videos from URLs (YouTube, Twitter/X, Twitch, Kick)
• video_url_transcription_price — Calculate video URL transcription cost

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 2 environment variables: DEAPI_API_BASE_URL, YOUR_DEAPI_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

For running the MCP server: - Python 3.10 or higher - uv, pip, or conda for package management For a deAPI account: - Sign up at deapi.ai and get your API token

When to reach for it

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. DeAPI's toolset — audio_transcription, audio_transcription_price, text_to_audio and 11 more — is a fair guide to whether it matches your workflow. It is maintained by deapi-ai; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch DeAPI.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the deapi mcp server does with a few real requests.