MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Reka is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Understand your videos with Reka AI — search, ask questions, and extract insights.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-reka-ai-reka-mcp https://mcp.reka.ai/mcp
# 2 — ask your agent for something these tools do
# upload_video, list_videos, get_video and 14 more
Reka costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, read from the address; if the publisher says otherwise, swap that one word.
claude mcp add --scope user --transport http mcp-reka-ai-reka-mcp https://mcp.reka.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Upload a video from a URL. Returns a video_id. Local file paths are not accepted; upload files outside the MCP server and pass a reachable video_url. The upload runs asynchronously — poll get_video until status is 'uploaded', then call index_video to enable search and analysis.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_url | string | yes | — |
| name | no | — | |
| description | no | — | |
| group_id | no | — | |
| rationale | no | — |
List all videos in your account, or filter to a specific group by passing group_id. Shows upload status and which features have been indexed for each video. Each video's 'url' is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call list_videos or get_video again for a fresh URL when needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_id | no | — | |
| rationale | no | — |
Get detailed information about a video including upload status, metadata (duration, resolution, fps), and per-feature indexing status. Use this to check if upload or indexing is complete. The 'url' field is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call get_video again for a fresh URL when needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| rationale | no | — |
Update a video's display name, title, description, or move it to a different group. At least one field must be provided. To remove a video from its group, pass group_id as null.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| name | no | — | |
| title | no | — | |
| description | no | — | |
| group_id | no | — | |
| move_group | boolean | no | — |
| rationale | no | — |
Permanently delete a video and all its indexed data (transcript, captions, embeddings, etc.). This cannot be undone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| rationale | no | — |
Create a new video group. Groups organize videos into collections. Returns the new group's ID and name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| rationale | no | — |
List all video groups. Use list_videos with a group_id to see videos in a specific group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rationale | no | — |
Delete a video group. Videos in the group are not deleted — they are simply removed from the group.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_id | string | yes | — |
| rationale | no | — |
Index a video for search, QA, or full analysis. Processes the video through a pipeline of AI features. Typically takes 3-7 minutes; longer for long videos or the 'full' pipeline. Times out after 10 minutes by default. Pipelines: - search_only: transcription + captions + embeddings (enables search_videos) - qa_only: transcription + captions (enables ask_video) - full: transcription + captions + em
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| pipeline | string | no | — |
| scene_detection | boolean | no | — |
| rationale | no | — |
Find WHEN and WHERE something happens across your videos. Returns timestamped results ranked by relevance — use these timestamps as start/end in ask_video for focused analysis. This is the recommended first step for most questions. Instead of asking ask_video about the entire video, search first to narrow down the relevant moments. Each result's 'video_url' is a short-lived HTTPS presigned URL (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| video_ids | no | — | |
| group_id | no | — | |
| max_results | integer | no | — |
| rationale | no | — |
Ask a question about one or more videos with visual analysis. Most effective on focused time ranges — use start/end to specify the segment to analyze. BEFORE calling this tool, read the reka://docs/guide resource for recommended workflows. In most cases, you should first: - search_videos to find WHEN something happens, then pass those timestamps here as start/end - segment_video to detect and loc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| video_id | no | — | |
| start | no | — | |
| end | no | — | |
| videos | no | — | |
| conversation_id | no | — | |
| rationale | no | — |
Detect objects in a video segment using text prompts. Describe what to look for and get per-frame detections with bounding boxes and confidence scores. Prompt tips: - Use broad, visual categories: 'animal', 'vehicle', 'person', 'text on screen' - Specific labels ('rabbit', 'Toyota') are less reliable — the detector matches visual patterns, not semantic concepts - Best for confirming whether a cat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| prompts | array | yes | — |
| start | number | yes | — |
| end | no | — | |
| threshold | number | no | — |
| rationale | no | — |
Get the spoken words in a video. Use this instead of ask_video when you need to read what was said — it returns the actual text, not a summary. Use start/end to narrow results for long videos. Requires the transcript feature to be indexed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| format | string | no | — |
| start | no | — | |
| end | no | — | |
| max_results | integer | no | — |
| max_chars | integer | no | — |
| rationale | no | — |
Get AI-generated visual descriptions of what happens on screen. Use this to understand the visual content without watching — each caption describes a short segment with timestamps. Use start/end to narrow results. Requires the captions feature (qa_only or full pipeline).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| start | no | — | |
| end | no | — | |
| max_results | integer | no | — |
| rationale | no | — |
Get detected scene boundaries with start/end timestamps. Use this to understand the video's structure, then pass scene timestamps as start/end to: - ask_video for per-scene contextual analysis - segment_video to detect specific objects per scene (scenes typically fit in segment_video's 15s max range) Requires transcript indexed with scene detection (on by default; skipped only if index_video was
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| max_results | integer | no | — |
| rationale | no | — |
List available video analysis features with their dependencies and descriptions. Use this to understand what features exist and what pipelines to use with index_video.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rationale | no | — |
Start here. Get a compact overview of a video: metadata, which features are indexed, a transcript preview, and scene count. Use this to decide which tools to call next — then use segment_video to detect specific objects in time ranges of interest.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| video_id | string | yes | — |
| rationale | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Reka or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.10.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Reka can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.