Vaaya

Claude Code

1. Run this in a terminal, in your project folder:

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

1. Start Claude Code, type /mcp, pick vaaya and choose Authenticate. A browser window opens for the vaaya-ai sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

1. Open Settings → Connectors and click Add custom connector.
2. Name it Vaaya and paste this URL:

https://vaaya.ai/mcp

1. Click Add, then Connect, and sign in when vaaya-ai asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

Add to claude.ai a11y.new_tab

1. Check that the URL reads https://vaaya.ai/mcp and click Add.
2. Click Connect and sign in when vaaya-ai asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
3. Paste https://vaaya.ai/mcp as the server URL and choose OAuth. ChatGPT sends you to vaaya-ai to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Install in VS Code a11y.new_tab

Or from a terminal:

code --add-mcp '{"name":"vaaya","type":"http","url":"https://vaaya.ai/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

{
  "servers": {
    "vaaya": {
      "type": "http",
      "url": "https://vaaya.ai/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):

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

1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add vaaya --url https://vaaya.ai/mcp
codex mcp login vaaya

Or edit ~/.codex/config.toml directly:

[mcp_servers.vaaya]
url = "https://vaaya.ai/mcp"

Gemini CLI

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

Then, inside Gemini CLI, run /mcp auth vaaya to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

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

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://vaaya.ai/mcp.

listing.em.badge

[![Vaaya on mcp.tc](https://mcp.tc/i/vaaya/badge.svg)](https://mcp.tc/i/vaaya)

<a href="https://mcp.tc/i/vaaya"><img src="https://mcp.tc/i/vaaya/badge.svg" alt="Vaaya on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

<script src="https://mcp.tc/w/vaaya.js" async></script>

listing.em.widget_note

iframe

<iframe src="https://mcp.tc/embed/vaaya" title="Vaaya on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/vaaya.json

listing.em.fields