OmniExtract MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify token for the hosted Apify MCP server. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| omni_extract_urlB | Universal, cookie-free content & transcript extractor for AI Agents. Extracts full long-form X (Twitter) Articles/Tweets, watermark-free Douyin/TikTok videos & photo galleries, YouTube/Bilibili video subtitles/transcripts with timestamps, GitHub READMEs/code, and anti-bot web pages into clean Markdown. |
| omni_extract_batchC | Concurrently extract up to 10 URLs (X Articles, Douyin, TikTok, YouTube, GitHub, Web) in parallel. |
| omni_check_quotaA | Check remaining API key credits or daily anonymous free quota. |
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 3 tools
Each tool targets a distinct operation: single-URL extraction, batched extraction, and quota checking. There is no realistic way to confuse batch extraction with a single extraction or with a credit check, and the descriptions reinforce the boundary.
All three names follow a strict server-prefixed verb_noun pattern: omni_extract_url, omni_extract_batch, omni_check_quota. The shared 'omni_' namespace plus consistent verb forms makes the set fully predictable.
Three tools is a tight, well-scoped surface for a stateless extraction service, and each one earns its place. Nothing redundant, nothing gratuitous.
The core workflow is fully covered: extract one, extract many, and monitor credits. Minor gaps exist, such as no way to select output format/depth, inspect supported-platform info, or check the status of a long-running batch, but agents can work around these.