Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
MCP payments server for Claude Code, Cursor, and Codex
Vaaya MCP gives agents paid access to search, scraping, data, compute, media, and research through one account. Each call declares a spend ceiling, so the server can refuse work before it reaches the provider if the price is too high.

Builders who want their agent to buy external tools and data without vendor keys or surprise spend.
You can let an agent use paid services with a hard budget on every call.
What it does
Pay-per-call tool access
`consult` returns a priced plan, and `use` runs the chosen call only if it fits the stated `max_cost_cents`.
Spend ceiling on every call
If the quoted price is over budget, the call is refused before it reaches the provider.
Success-only billing
Failed or refused calls cost nothing, and the README says billing happens only on success.
Multi-host setup
The server works with Cursor, Claude Code, Claude Desktop, Codex, and any MCP host.
Agent skill and plugin bundles
The repo ships a `vaaya` skill and plugin packages for Claude Code, Codex, Cursor, and Gemini CLI.
Hosted tool proxy
The live tool list is proxied from the backend, including search, scraping, GTM, sandbox, browser, email, and memory tools.
Runnable examples
Examples show pay-for-an-api flows and host-specific setups in `examples/pay-for-an-api`, `examples/cursor`, and `examples/claude`.
Session sandbox tools
`session` and `close` manage per-second-billed code sandbox sessions for running code or benchmarks.
How to get it
- 1Run
npx @vaaya/mcp install
- 2Claude Code
claude mcp add --transport http vaaya https://vaaya.ai/mcp
- 3OpenClaw
openclaw mcp add vaaya --url https://vaaya.ai/mcp --transport streamable-http --auth oauth openclaw mcp login vaaya
- 4Run
npx skills add vaaya-ai/vaaya-mcp
README
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.
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 |
| 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-mcpthen/plugin install vaaya@vaaya— bundles the remote MCP server, thevaayaskill, and the SessionStart reminder hook - Codex:
codex plugin marketplace add vaaya-ai/vaaya-mcpthen installvaayafrom 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_centsis a hard spend ceiling. Long jobs return{ async: true, job_id }— poll withresult(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/listfor 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_centsguard.
Links
- Website & docs: https://vaaya.ai
- Agent-readable docs (llms.txt): https://vaaya.ai/llms.txt · full tool reference: https://vaaya.ai/llms-full.txt
- npm: https://www.npmjs.com/package/@vaaya/mcp · https://www.npmjs.com/package/vaaya-cli
- Support: support@vaaya.ai
Files in the repo
- .agents
- .claude-plugin
- .codex-plugin
- .cursor-plugin
- .github
- assets
- clawhub
- examples
- glama
- hooks
- rules
- skills
- .dockerignore
- .gitignore
- .mcp.json
- CHANGELOG.md
- Dockerfile
- gemini-extension.json
- glama.json
- LICENSE
- llms-install.md
- mcp.json
- README.md
- skills.sh.json
Discussion (0)
Ask about usage, or say what you built with itSign in to join the discussion.
No comments yet. Be the first to say what this is good for.
More connectors
High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code
Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.
Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.
Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.