Ask your assistant for the data instead of calling it

Registers the server for the project you are in. The key travels in a header, so it never lands in the repository.

1. Open a terminal in the project you want the data in.
2. Run the command below with your own key.
3. Start Claude Code and ask it something about your hotels.

claude mcp add --transport http veetal https://mcp.veetal.app/mcp \
  --header "veetal-api-key: YOUR_API_KEY"

Add --scope user to make the server available in every project instead of just this one. Run /mcp to check that veetal comes back connected.

Cursor reads its MCP servers from a JSON file. Edit the global one to get it everywhere, or drop the same block into .cursor/mcp.json inside a project.

1. Open Preferences → Cursor Settings → Customize → MCP and click New MCP server.
2. Cursor opens the file for you: the global ~/.cursor/mcp.json. If you only want it in one project, create .cursor/mcp.json in its root and edit that instead.
3. Paste the block below and swap in your key. If you already have other servers, add veetal inside mcpServers.
4. Reload Cursor: the server shows up in the MCP list and the Veetal tools in the chat's tool list.

{
  "mcpServers": {
    "veetal": {
      "url": "https://mcp.veetal.app/mcp",
      "headers": {
        "veetal-api-key": "YOUR_API_KEY"
      }
    }
  }
}

This file holds your key in plain text — keep it out of version control. Cursor also expands environment variables inside headers, so you can export the key in your shell profile and reference it with the env: syntax instead of writing it here.

Claude Desktop adds remote servers from its own settings. The form only offers a short list of header names, so here the key travels as a bearer token.

1. Open Settings → Connectors and click Add, top right.
2. Name the connector — Veetal Connect API, say — paste the server URL above and click Continue.
3. Under Authentication pick No authentication, even if Sign in now shows up as Detected: the server authenticates with an API key, not OAuth.
4. Under Request headers pick authorization from the dropdown, paste the value below with your key, and leave Required ticked.
5. Click Add, then enable the connector in a new chat.

Bearer YOUR_API_KEY

The server takes the key either as the veetal-api-key header or as Authorization: Bearer. Claude Desktop's dropdown only offers the second. The value is stored encrypted and never shown again.