← vaaya.ai

INDIVIDUAL MCP TOOL

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.

vaaya.ainone authenticationAvailability not checked

Input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent endpoint

vaaya.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vaaya]
url = "https://vaaya.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vaaya": {
      "type": "http",
      "url": "https://vaaya.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vaaya
Remote MCP URL: https://vaaya.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "vaaya": {
      "type": "http",
      "url": "https://vaaya.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vaaya",
  "transport": "streamable-http",
  "url": "https://vaaya.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • vaaya_test_connection — Round-trip ping that confirms the agent → Vaaya connection and whether the user is linked.
  • vaaya_onboard — Public onboarding hint for an agent whose user isn't linked to Vaaya yet.
  • vaaya_account — Show which Vaaya account this connection is linked to and its money state.
  • consult — Vaaya's consultant.
  • use — Execute a single call that `consult` handed you, and bill on success.
  • result — Fetch the status + output of an async job started by `use` (e.
  • session — Run a command or code in an open E2B sandbox session (started by `use` with action `create_session`, which returns a `session_id`).
  • close — Close an E2B sandbox session and stop its billing.