MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Vaaya 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.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Pay-per-call agent superpowers: media/video gen, product demos, research, GTM, scraping, compute.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http vaaya-ai-vaaya-mcp https://vaaya.ai/mcp
# 2 — ask your agent for something these tools do
# vaaya_test_connection, vaaya_onboard, vaaya_account and 7 more
Vaaya costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VAAll 1 server
vaaya.ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 vaaya-ai-vaaya-mcp https://vaaya.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
10 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.
Round-trip ping that confirms the agent → Vaaya connection and whether the user is linked. Returns { ok:true, userId, scope, version, server_time, first_call } when linked — SHOW first_call.show_to_user to the user as written, it is the same set of starter examples the website and installer give them. Returns { ok:false, needs_auth:true, verification_uri, signup_uri, instructions } when not link
No parameter schema on file.
Public onboarding hint for an agent whose user isn't linked to Vaaya yet. Returns where the human should go to connect (and sign up if new). Call this when vaaya_test_connection reports needs_auth, or any tool returns unauthorized, then relay the instructions to the user. If the user IS already linked it returns first_call instead — show first_call.show_to_user as written so they know what to
No parameter schema on file.
Show which Vaaya account this connection is linked to and its money state. Returns { email, name, user_id, connected_client, scopes, balance_cents, credit_line, available_cents, credits_url, switch_account }. Call it whenever the user asks "which account is connected", "what's my balance", "how much credit is left", or "how do I switch accounts" — and relay the answer. credit_line is the card-ba
No parameter schema on file.
Disconnect this client from the current Vaaya account: revokes this connection's authorization server-side, so every later call fails with 401 until the user reconnects. Call it when the user asks to log out, sign out, disconnect, or switch Vaaya accounts — then relay the returned switch steps VERBATIM (the browser sign-out step is what actually enables switching accounts).
No parameter schema on file.
Vaaya's consultant. Describe ANY external capability you or the user might want — generate an image/video, search or scrape the web, run code in a sandbox, send/receive email, enrich a contact — and it helps figure out the best way, teaching the user what Vaaya can do. It is CONVERSATIONAL and remembers prior turns. It returns: mode='converse' (a reply to RELAY to the user verbatim — questions, op
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | Plain-English description of what you want, or your answer to a previous clarify question. Be concrete — include the prompt text, URL, budget, or target the task implies. |
Execute a single call that consult handed you, and bill on success. Used for any external capability (image/video/audio generation, web search, scraping, email, document parsing, code sandbox, browser automation, embeddings, etc.). The server validates params against a registered schema and proxies to the upstream — you never pass URLs or API keys. Always get the exact (service, action, params,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | Service identifier, taken verbatim from the call consult returned. |
| action | string | yes | Action within the service (e.g. "search", "generate", "create_session"), taken from the call consult returned. |
| params | object | yes | Parameters from the call consult returned, validated against the service's registered schema. |
| max_cost_cents | number | yes | Hard ceiling in cents on what you will be charged. use refuses if the registry price exceeds this. Pick at least 2× the listed price so retries work. |
| intent | string | no | Optional: the one-line why from the consult call you're running (or the user's goal for it). Used only for internal transaction visibility — it never affects validation, billing, or execution. Pass |
Fetch the status + output of an async job started by use (e.g. a video render). Pass the job_id that use returned with { async: true }. Returns { status, result?, progress?, charged_cents }: running (still working — when the job reports it, progress carries { phase, percent, rendered_frames, total_frames, eta_sec } and hint is a one-line summary like "rendering 42% (380/900 frame
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The job_id returned by an async use call. |
Run a command or code in an open E2B sandbox session (started by use with action create_session, which returns a session_id). Pass session_id plus either command (a shell command) or code (+ optional language: python/javascript/bash). Returns stdout/stderr/exit_code (or the code result). The sandbox stays alive — and billed per second of uptime — until you close it; re-running reus
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session_id returned by create_session. |
| command | string | no | Shell command to run in the sandbox. |
| code | string | no | Code to execute (alternative to command). |
| language | string | no | Language for code: python (default), javascript, or bash. |
Close an E2B sandbox session and stop its billing. Pass the session_id. Captures the final metered uptime cost and releases the hold. ALWAYS call this when finished with a session — an open session keeps billing per second of uptime. Safe to call repeatedly (idempotent).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | The session_id to close. |
Ask a DIFFERENT LLM a question and get its answer, billed per token from the Vaaya wallet (model cost + 3%, usually a fraction of a cent). Use it to get a second opinion from a rival model, cross-check an answer, summarize a huge blob cheaply, or query a specific model the user names (Kimi, GPT, Gemini, Claude, DeepSeek, and 300+ more). model accepts 'auto' (default: short prompts go cheap, long
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | The question or task for the other model. |
| model | string | no | 'auto' (default), 'cheap', 'mid', 'best', or an exact OpenRouter model slug (e.g. 'moonshotai/kimi-k3', 'anthropic/claude-opus-5'). |
| system | string | no | Optional system prompt for the other model. |
| max_tokens | number | no | Optional cap on the response length in tokens (default 4096, max 16384). |
Free
$0 forever
- 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 Vaaya or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Vaaya can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.