Vaaya MCP Server

Most search and retrieval work still happens through a UI a human drives. Vaaya MCP server moves it into the conversation instead. Vaaya CLI — give your agent paid superpowers. One command installs the Vaaya MCP server into Claude Code, Claude Desktop, Cursor, and Codex: media & video generation, product demo videos, web search & scraping, deep/market research, GTM &.

The short version

Vaaya is the agent payment system: one MCP server that lets any agent call paid APIs pay-per-call, with no API keys. Instead of wiring up a dozen vendor keys, your agent asks Vaaya's conversational consult tool for anything it can't do, gets back the exact call to run, and executes it with use — billed on success only (x402 USDC on Base, Stripe MPP, or Tempo; the payment is the auth). Failed calls are never charged.

The tools it exposes

The server publishes 5 tools. What each one is for:

• Codex — codex plugin marketplace add vaaya-ai/vaaya-mcp then install vaaya from the Plugins panel
• Pay-per — call on x402 (USDC on Base), Stripe MPP/SPT, or Tempo. Failed calls
• Agent — readable docs (llms.txt): https://vaaya.ai/llms.txt · full tool reference: https://vaaya.ai/llms-full.txt
• Support — support@vaaya.ai
• Capability — What you get

Getting it running

The server ships on npm as @vaaya/mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Vaaya's toolset — Codex, Pay-per, Agent and 2 more — is a fair guide to whether it matches your workflow. It is maintained by marupelkar; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.