How do I install Vaaya?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Vaaya need an API key?

No required environment variable is listed on this record.

When was Vaaya last checked?

Last checked 2026-10-20. Paid APIs and tokenized shares for agents. Prepaid funding, including authorized Instinct checkout.

Vaaya MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://vaaya.ai/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http ai.vaaya-mcp https://vaaya.ai/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "ai.vaaya-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://vaaya.ai/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.6.8
Last checked

14 tools

Tools

tools/listVoice mode preview

Tool	What it does
stocks	Buy tokenized stocks on Base using only the user’s prepaid Vaaya balance, never the welcome credit or the GitHub credit line. Commands: list (supported token tickers), portfolio (owned stocks and buying power), quote {symbol, amount_cents}, buy {symbol, amount_cents, idempotency_key}, order {order_i
jobs	Jobs: a marketplace where humans hire humans, and each side's agent handles the steps. Call with { action, ...params }. Actions: list, get, mine, draft, update_draft, cancel, accept, submit_proof, record_verdict, request_release, dispute. A poster's agent drafts a job (budget_usd, definition_of_done
vaaya_test_connection	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 t
vaaya_onboard	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 link
vaaya_account	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
vaaya_logout	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 VERBA
docs	Vaaya's deep reference, FREE and instant. Pass `topic` to get the full playbook for a capability area — exact services, actions, params, prices, model lists, and gotchas — the same reference files the vaaya skill ships. Topics: 'setup' (connecting an agent, a chat app, or an unattended process), 'to
consult	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 remem
use	Execute a single external call, 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
result	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_
buy	Find and buy products, tickets, bookings and subscriptions for the user at supported stores. Start with `search` { query } to find the item and merchant page using Vaaya OneSearch (5¢ per search); the user can describe what they need without supplying a link. Before checkout, use `setup` to check pa
session	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
close	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).
llm	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, Gem

Vaaya MCP — payments for any agent

MCP server for AI agent payments. An agent in Cursor, Claude Code, Claude Desktop, Codex, or any MCP host can call paid APIs (search, scraping, contact data, public records, compute, media, research) from one balance, with a spend ceiling it states on every call, and no vendor keys anywhere in its environment. Billed only on success (x402 USDC on Base, Stripe MPP, or Tempo); a refused or failed call costs nothing.

npx @vaaya/mcp install            # Cursor, Claude Code, Claude Desktop, Codex
claude mcp add --transport http vaaya https://vaaya.ai/mcp

First paid call: consult returns a priced plan; use({ service, action, params, max_cost_cents }) runs one line of it. If the quoted price is above max_cost_cents, the call is refused before it reaches the provider and the reason comes back:

{ "error": "over_max", "message": "price is 5¢ but max_cost_cents was 1", "price_cents": 5 }

Runnable examples: examples/pay-for-an-api (one call allowed, one refused), examples/cursor, examples/claude. Guides: give an agent a budget, Cursor setup, Claude setup, what is an AI agent wallet.

Buy tokenized shares — including with Instinct

Agents can buy supported tokenized stocks on Base with Vaaya prepaid funds. These are tokenized stocks, not direct brokerage shares. Discover the current supported tickers with stocks({ command: "list" }) (for example Apple AAPLc and NVIDIA NVDAc), then check stocks({ command: "portfolio" }) for buyingPowerCents. Welcome grants and credit lines cannot buy shares.

For a user-authorized $10 Apple purchase:

{ "command": "buy", "symbol": "AAPLc", "amount_cents": 1000, "idempotency_key": "<unique purchase key>" }

Call the dedicated stocks MCP tool with this input; it is separate from consult/use. The amount is the maximum total prepaid spend including fees. Save the returned id, then poll stocks({ command: "order", order_id: "<id>" }). Only confirmed means purchased. Stop on failed or needs_review; reuse the same purchase key on uncertain retries, never place a new order to check status.

Insufficient prepaid balance? With the user's authorization for a $10, $30, or $100 pack, POST https://vaaya.ai/api/v1/topup with JSON { "pack_cents": 1000 } (or 3000 / 10000) using the same account's bearer token. An Instinct agent with access to the user's saved card can pay the returned Stripe Checkout url in its own browser when authorized for that pack amount. For a handoff, provide the URL and authorized amount to the user's Instinct agent; otherwise give the URL to the user. Keep card details and bearer tokens out of the handoff. Vaaya cannot charge a card stored in Instinct directly. A share purchase alone does not authorize an extra card charge.

Poll GET /api/v1/wallet (wallet.prepaid_cents), then recheck stock buying power before resuming the original purchase key. Do not pay again while a payment's outcome is uncertain. Stock availability and account permissions apply.

Full MCP and REST purchase guide · Complete tool reference

What your agent can do through Vaaya

Capability	What you get
🎨 Media generation	Images & video with top models — Nano Banana Pro 2, GPT Image 2, Seedream v4.5, Kling v3, Seedance 2.0 — plus TTS voices & music
🎬 Product demo videos	Record a raw, silent screen capture of your live product; Vaaya auto-authors narration + zoom/cut plan and renders a finished narrated demo
🖼️ Website imagery	Derive a site's brand and generate an on-brand image set straight into your repo
🔎 Web search	Exa & Parallel: query search, URL contents, async deep research tasks
🕷️ Web scraping	Firecrawl scrape / crawl / map / search / extract, persisted to files
📚 Deep research	Multi-hop, source-verified, cited research reports
📊 Market & competitive research	Company reports (people, hiring, ads, reviews, SEO/LLM visibility), product & feature catalogs with review sentiment, UX research with interactive product maps, "best X for my data" bake-offs, persistent competitive knowledge repos
🎯 GTM & sales	Find ICP-matched leads with verified contacts, enrich contacts, track buying signals (funding/hiring/launch/press), 24×7 LinkedIn discovery, segment-based outbound email — every draft held for human approval
⏰ Monitoring workers	Scheduled watches (30 min–weekly) over competitor pricing, deals, reviews, job postings, news — only new/changed findings surface
🖥️ Compute sandboxes	Per-second-billed code execution (Modal) for benchmarks, untrusted code, GPU inference, data jobs
🌐 Browser automation	Browserbase sessions to click, type, log in, fill forms
📧 Email	AgentMail inboxes your agent owns — send and receive replies
🧠 Memory	Persistent cross-session memory via mem0, Zep, or Letta

Install

One command (recommended)

npx @vaaya/mcp install

(npx vaaya-cli install runs the same installer.)

Sets up the Vaaya MCP server for every agent it detects on your machine — Claude Code, Claude Desktop, Cursor, Codex — plus the agent skill. Idempotent: re-run any time to update. Then restart your agent; the first Vaaya call opens a short browser approval (sign-up happens right there).

Remote (Streamable HTTP + OAuth)

{ "mcpServers": { "vaaya": { "url": "https://vaaya.ai/mcp" } } }

Claude Code:

claude mcp add --transport http vaaya https://vaaya.ai/mcp

OpenClaw:

openclaw mcp add vaaya --url https://vaaya.ai/mcp --transport streamable-http --auth oauth
openclaw mcp login vaaya

Hermes (~/.hermes/config.yaml):

mcp_servers:
  vaaya:
    url: "https://vaaya.ai/mcp"
    auth: oauth

On first use your client runs the OAuth flow in the browser; approve and you're connected. Revoke anytime at vaaya.ai/connected-apps.

npm stdio shim (for stdio-only clients: opencode, …)

{ "mcpServers": { "vaaya": { "command": "npx", "args": ["-y", "@vaaya/mcp"] } } }

The shim (@vaaya/mcp) opens the OAuth flow on first call, stores a refresh token locally (0o600), and proxies the live tool list from the backend — new server-side tools appear without a shim upgrade. It also ships an agent skill so your client routes every capability gap through consult automatically.

Agent skill (works across 70+ agents)

npx skills add vaaya-ai/vaaya-mcp

Installs the vaaya skill for Claude Code, Codex, Cursor, Gemini CLI, Copilot, and any other client that supports the open Agent Skills standard. The skill bootstraps the Vaaya MCP server if it's missing and keeps the install updated.

As a plugin

Claude Code: /plugin marketplace add vaaya-ai/vaaya-mcp then /plugin install vaaya@vaaya — bundles the remote MCP server, the vaaya skill, and the SessionStart reminder hook
Codex: codex plugin marketplace add vaaya-ai/vaaya-mcp then install vaaya from the Plugins panel
Gemini CLI: gemini extensions install https://github.com/vaaya-ai/vaaya-mcp

How it works

consult(intent) — describe any goal in plain English ("generate a hero video", "find 50 heads of RevOps with verified emails", "watch my competitor's pricing page"). It converses, clarifies, and returns the exact call(s) to run.
use(service, action, params, max_cost_cents) — execute the call. Billed on success; max_cost_cents is a hard spend ceiling. Long jobs return { async: true, job_id } — poll with result(job_id).
session / close — per-second-billed code sandbox sessions.

Plus a full GTM suite (gtm_leads_find, gtm_lead_enrich, gtm_signal_create, gtm_segments, gtm_message, gtm_replies, …) and scheduled monitoring workers (worker_create, worker_findings, …) — the tool list is proxied live from the backend.

Example prompts

"Generate a hero video for our landing page in 16:9."
"Record my product and turn it into a narrated demo video."
"Find 50 heads of RevOps at Series-B SaaS companies with verified emails."
"Watch my competitor's pricing page and tell me when it changes."
"Do deep research on the agentic payments market with cited sources."
"Scrape these 200 product pages into structured JSON."
"Run this benchmark in a GPU sandbox."

CLI

The vaaya-cli CLI manages everything from the terminal:

npx vaaya-cli install        # set up the MCP server for every detected agent
npx vaaya-cli status         # connection state + live tool count
npx vaaya-cli consult "..."  # ask Vaaya how it would do something (returns the plan)
npx vaaya-cli reauthorize    # re-run the browser auth flow
npx vaaya-cli logout         # disconnect & delete local credentials

Security & billing

Your agent never sees vendor API keys or upstream URLs — Vaaya proxies every call server-side.
OAuth 2.1 (PKCE, dynamic client registration); anonymous tools/list for discovery; revocable grants.
Pay-per-call on x402 (USDC on Base), Stripe MPP/SPT, or Tempo. Failed calls are never charged. Every call carries a max_cost_cents guard.

Vaaya

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Vaaya?

Does Vaaya need an API key?

What transport does Vaaya use?

When was Vaaya last checked?

Documentation

Vaaya MCP — payments for any agent

Buy tokenized shares — including with Instinct

What your agent can do through Vaaya

Install

One command (recommended)

Remote (Streamable HTTP + OAuth)

npm stdio shim (for stdio-only clients: opencode, …)

Agent skill (works across 70+ agents)

As a plugin

How it works

Example prompts

CLI

Security & billing

Links