textify-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@textify-mcpGet transcript from https://youtu.be/abc123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@textifyme/mcp
Local (stdio) shim for the hosted Textify MCP server — turn anything into text from any MCP
client. It bridges a local command-style MCP config to the hosted streamable-HTTP endpoint at
https://mcp.textify.me/mcp, with your API key pre-wired.
Prefer a remote connector? If your client supports remote MCP servers directly (Claude.ai "Add custom connector"), just add
https://mcp.textify.me/mcp— you don't need this package. This shim exists for clients that only accept a local command.
Tools
Tool | What it does |
| Fetch a YouTube video's published captions by URL or ID. |
| Transcribe an audio/video file (URL or upload) to timestamped text. |
| Extract text from a photo, screenshot, or scan (incl. handwriting). |
| Convert a DOCX / PPTX / XLSX / EPUB to clean Markdown (PDF not supported). |
| Fetch a public URL and return clean Markdown. |
Every account gets 100 free credits/month. All calls debit the same credit ledger as the Textify REST API and website — one balance, one accounting.
Setup
Get an API key at https://textify.me/docs.
Claude Desktop / Claude Code / Cursor
{
"mcpServers": {
"textify": {
"command": "npx",
"args": ["-y", "@textifyme/mcp"],
"env": { "TEXTIFY_API_KEY": "sk_your_key" }
}
}
}TEXTIFY_API_KEY is required — tool calls that cost credits authenticate with it as
Authorization: Bearer <key>. Get a free key (100 credits/month) at https://textify.me/account.
Configuration
Env var | Default | Purpose |
| — | API key; sent as |
|
| Endpoint override. Set to |
Extra CLI args are forwarded to the underlying mcp-remote
bridge (e.g. --debug).
How it works
The shim is a thin wrapper: it resolves the bundled mcp-remote proxy and launches it against the
Textify endpoint with your auth header attached, then pipes MCP over stdio. No Textify credentials
are stored on disk by this package; the key lives only in your client's env.
Local development
# in this package dir
npm install
TEXTIFY_MCP_URL=http://localhost:8788/mcp TEXTIFY_API_KEY=sk_test node bin/textify-mcp.mjs
# (run `pnpm --filter @app/mcp run dev` in the Textify monorepo to serve localhost:8788)License
MIT — see LICENSE.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
OCR, transcription, file extraction, and image generation for AI agents via MCP.
Transform video, audio and images, and generate media from prompts. FFmpeg, captions, models.
Transcripts from YouTube, TikTok, Instagram and podcasts (Spotify, Apple, RSS), as clean JSON.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/textifyme/textify-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server