Skip to content
Back to search

vantage-mcp-server

MCP Server to fetch costs and usage data from your Vantage account.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/vantage-sh/vantage-mcp-server with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/vantage-sh/vantage-mcp-server'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/vantage-sh--vantage-mcp-server/badge.svg)](/listings/vantage-sh--vantage-mcp-server)

HTML

<a href="/listings/vantage-sh--vantage-mcp-server"><img src="/api/listings/vantage-sh--vantage-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

General

The hosted MCP server uses [Streamable HTTP](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#streamable-http) with OAuth 2.1. After connecting a client, a browser window prompts you to sign in to Vantage — the same account you use at [console.vantage.sh](https://console.vantage.sh/).

**Server URL:** `https://mcp.vantage.sh/mcp`

**Legacy SSE connections:** The `/sse` endpoint is deprecated and remains available during the 60-day migration window, ending on **November 30, 2026**, when the legacy SSE endpoint will be retired. If your client uses `https://mcp.vantage.sh/sse`, update its server URL to `https://mcp.vantage.sh/mcp`, select Streamable HTTP if it asks for a transport, then reconnect and sign in if prompted. Some clients display a deprecation warning when connecting; others do not.

Clients that support remote MCP natively can connect directly to that URL. For clients that only support stdio, use the `mcp-remote` bridge (see [Visual Studio Code](#visual-studio-code) below).

**API token auth:** If your client or script cannot complete OAuth, pass a [Vantage API token](https://docs.vantage.sh/vantage_account#create-an-api-token) as a Bearer token instead:

Authorization: Bearer <your_vantage_api_token>

Claude Code

claude mcp add --transport http vantage https://mcp.vantage.sh/mcp

Then run `/mcp` in a Claude Code session to complete the OAuth flow.

Codex

codex mcp add vantage --url https://mcp.vantage.sh/mcp

Run `codex mcp login vantage` if Codex prompts you to authenticate.

Cursor

The recommended install is the official Vantage plugin — in the Cursor chat panel, run:

/add-plugin vantage

To configure manually (for example, to commit `.cursor/mcp.json` to a repo):

{
  "mcpServers": {
    "VantageMCP": {
      "url": "https://mcp.vantage.sh/mcp"
    }
  }
}

Open **Cursor Settings → Tools & MCP → New MCP Server** to edit `mcp.json`, or create `.cursor/mcp.json` in your project root.

Claude

**Claude.ai (Team / Enterprise):** **Settings → Connectors → Add custom connector** — enter `https://mcp.vantage.sh/mcp`.

**Claude Desktop:** **Settings → Connectors** — add a custom connector with the same URL.

Goose

1. **Extensions → Add custom extension** 2. **Type:** Streamable HTTP 3. **Endpoint:** `https://mcp.vantage.sh/mcp`

Complete the OAuth flow when Goose connects.

Visual Studio Code

{
  "mcpServers": {
    "vantage": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vantage.sh/mcp"]
    }
  }
}

Or use the command palette: **MCP: Add Server → Command (stdio)** and enter:

npx -y mcp-remote https://mcp.vantage.sh/mcp

Windsurf

Under **Cascade → MCP servers → Add custom server**, add:

{
  "mcpServers": {
    "vantage": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vantage.sh/mcp"]
    }
  }
}

Zed

In Zed settings, add:

{
  "context_servers": {
    "vantage": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vantage.sh/mcp"],
      "env": {}
    }
  }
}

Other clients

For any stdio-only MCP client, use:

- **Command:** `npx` - **Arguments:** `-y mcp-remote https://mcp.vantage.sh/mcp`

See the [MCP clients list](https://modelcontextprotocol.io/clients) and the [Vantage MCP documentation](https://docs.vantage.sh/vantage_mcp) for additional clients (including ChatGPT via the Vantage app).

Authorize

After configuring your client, you may need to restart it. A browser window opens for Vantage OAuth — sign in and click **Allow Access**. You can revoke access anytime under **Vantage Settings → API Access Tokens → MCP Server Token**.

Try a prompt like: _"In Vantage, which workspaces do I have access to?"_

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 318 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <div align="center">
  2. # Vantage MCP Server
  3. <h4>Use natural language to explore your organization's cloud costs via MCP clients, like Claude, Cursor, and others. Ask questions about your organization's previous and current cloud cost spend, cost tagging, provider integrations, and more.</h4>
  4. <img src="static/img/mcp.png" alt="MCP Logo" width="600" height="auto">
  5. </div>
  6. ## About
  7. The Vantage MCP Server exposes tools for listing, querying, and creating Vantage resources. Tools are defined in [/src/tools](/src/tools); see the [Vantage MCP documentation](https://docs.vantage.sh/vantage_mcp) for the full tool list, prompting examples, and product details.
  8. This repository supports two deployment modes:
  9. | Mode | Best for |
  10. | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
  11. | **Hosted (Remote) MCP** — Vantage-managed at `https://mcp.vantage.sh/mcp` | Most users and teams. OAuth sign-in, no local server to run. |
  12. | **Self-Hosted (Local) MCP** — stdio via `npx -y vantage-mcp-server` or this repo | API-token auth, air-gapped environments, or contributing to this codebase. |
  13. **Start with the hosted MCP** unless you have a specific reason to self-host.
  14. ## Setup Instructions
  15. ### General
  16. The hosted MCP server uses [Streamable HTTP](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#streamable-http) with OAuth 2.1. After connecting a client, a browser window prompts you to sign in to Vantage — the same account you use at [console.vantage.sh](https://console.vantage.sh/).
  17. **Server URL:** `https://mcp.vantage.sh/mcp`
  18. **Legacy SSE connections:** The `/sse` endpoint is deprecated and remains available during the 60-day migration
  19. window, ending on **November 30, 2026**, when the legacy SSE endpoint will be retired. If your client uses
  20. `https://mcp.vantage.sh/sse`, update its server URL to `https://mcp.vantage.sh/mcp`, select Streamable HTTP if it asks
  21. for a transport, then reconnect and sign in if prompted. Some clients display a deprecation warning when connecting;
  22. others do not.
  23. Clients that support remote MCP natively can connect directly to that URL. For clients that only support stdio, use the `mcp-remote` bridge (see [Visual Studio Code](#visual-studio-code) below).
  24. **API token auth:** Clients and scripts can authenticate to the hosted endpoint without OAuth by sending a
  25. [Vantage API token](https://docs.vantage.sh/vantage_account#create-an-api-token), including a service token:
  26. ```http
  27. Authorization: Bearer <your_vantage_api_token>
  28. ```
  29. Core validates the token and its permissions on each tool call. Reads require `read` scope; mutations require
  30. the corresponding write permissions. An invalid or revoked token can initialize MCP, but its tool calls return
  31. Core's authorization error.
  32. ### Claude Code
  33. ```bash
  34. claude mcp add --transport http vantage https://mcp.vantage.sh/mcp
  35. ```
  36. Then run `/mcp` in a Claude Code session to complete the OAuth flow.
  37. ### Codex
  38. ```bash
  39. codex mcp add vantage --url https://mcp.vantage.sh/mcp
  40. ```
  41. Run `codex mcp login vantage` if Codex prompts you to authenticate.
  42. ### Cursor
  43. The recommended install is the official Vantage plugin — in the Cursor chat panel, run:
  44. ```
  45. /add-plugin vantage
  46. ```
  47. To configure manually (for example, to commit `.cursor/mcp.json` to a repo):
  48. ```json
  49. {
  50. "mcpServers": {
  51. "VantageMCP": {
  52. "url": "https://mcp.vantage.sh/mcp"
  53. }
  54. }
  55. }
  56. ```
  57. Open **Cursor Settings → Tools & MCP → New MCP Server** to edit `mcp.json`, or create `.cursor/mcp.json` in your project root.
  58. ### Claude
  59. **Claude.ai (Team / Enterprise):** **Settings → Connectors → Add custom connector** — enter `https://mcp.vantage.sh/mcp`.
  60. **Claude Desktop:** **Settings → Connectors** — add a custom connector with the same URL.
  61. ### Goose
  62. 1. **Extensions → Add custom extension**
  63. 2. **Type:** Streamable HTTP
  64. 3. **Endpoint:** `https://mcp.vantage.sh/mcp`
  65. Complete the OAuth flow when Goose connects.
  66. ### Visual Studio Code
  67. ```json
  68. {
  69. "mcpServers": {
  70. "vantage": {
  71. "command": "npx",
  72. "args": ["-y", "mcp-remote", "https://mcp.vantage.sh/mcp"]
  73. }
  74. }
  75. }
  76. ```
  77. Or use the command palette: **MCP: Add Server → Command (stdio)** and enter:
  78. ```bash
  79. npx -y mcp-remote https://mcp.vantage.sh/mcp
  80. ```
  81. ### Windsurf
  82. Under **Cascade → MCP servers → Add custom server**, add:
  83. ```json
  84. {
  85. "mcpServers": {
  86. "vantage": {
  87. "command": "npx",
  88. "args": ["-y", "mcp-remote", "https://mcp.vantage.sh/mcp"]
  89. }
  90. }
  91. }
  92. ```
  93. ### Zed
  94. In Zed settings, add:
  95. ```json
  96. {
  97. "context_servers": {
  98. "vantage": {
  99. "source": "custom",
  100. "command": "npx",
  101. "args": ["-y", "mcp-remote", "https://mcp.vantage.sh/mcp"],
  102. "env": {}
  103. }
  104. }
  105. }
  106. ```
  107. ### Other clients
  108. For any stdio-only MCP client, use:
  109. - **Command:** `npx`
  110. - **Arguments:** `-y mcp-remote https://mcp.vantage.sh/mcp`
  111. See the [MCP clients list](https://modelcontextprotocol.io/clients) and the [Vantage MCP documentation](https://docs.vantage.sh/vantage_mcp) for additional clients (including ChatGPT via the Vantage app).
  112. ### Authorize
  113. After configuring your client, you may need to restart it. A browser window opens for Vantage OAuth — sign in and click **Allow Access**. You can revoke access anytime under **Vantage Settings → API Access Tokens → MCP Server Token**.
  114. Try a prompt like: _"In Vantage, which workspaces do I have access to?"_
  115. ---
  116. ## Self-Hosted (Local) MCP
  117. Use self-hosted mode when you need API-key auth without OAuth, or when developing against this repository.
  118. ### npm package (recommended for self-host)
  119. Install nothing — configure your MCP client to run the published package:
  120. ```json
  121. {
  122. "mcpServers": {
  123. "Vantage": {
  124. "command": "npx",
  125. "args": ["-y", "vantage-mcp-server"],
  126. "env": {
  127. "VANTAGE_TOKEN": "<your_vantage_api_token>"
  128. }
  129. }
  130. }
  131. }
  132. ```
  133. Create a token in the [Vantage console](https://docs.vantage.sh/vantage_account#create-an-api-token). Requires [Node.js 20+](https://nodejs.org/en/download).
  134. ### From this repository (contributors)
  135. For working on the MCP server itself:
  136. ```bash
  137. git clone https://github.com/vantage-sh/vantage-mcp-server
  138. cd vantage-mcp-server
  139. npm install
  140. ```
  141. Configure your client to run the local entrypoint (replace `<path_to_repository>` and `<personal_vantage_api_token>`):
  142. ```json
  143. {
  144. "mcpServers": {
  145. "Vantage": {
  146. "command": "npx",
  147. "args": ["tsx", "<path_to_repository>/src/local.ts"],
  148. "env": { "VANTAGE_TOKEN": "<personal_vantage_api_token>" }
  149. }
  150. }
  151. }
  152. ```
  153. Or use the repo's installed binary directly:
  154. ```json
  155. {
  156. "mcpServers": {
  157. "Vantage": {
  158. "command": "<path_to_repository>/node_modules/.bin/tsx",
  159. "args": ["<path_to_repository>/src/local.ts"],
  160. "env": { "VANTAGE_TOKEN": "<personal_vantage_api_token>" }
  161. }
  162. }
  163. }
  164. ```
  165. Test from the terminal: `npm run local` (requires `VANTAGE_TOKEN` in the environment).
  166. ---
  167. ## Local Development
  168. To develop the hosted worker locally:
  169. ```bash
  170. cp .dev.vars.example .dev.vars.development
  171. # Edit .dev.vars.development — set VANTAGE_MCP_TOKEN to your API token
  172. npm run dev
  173. ```
  174. Wrangler serves the worker at `http://localhost:8787` (default). Setting `VANTAGE_MCP_TOKEN` bypasses OAuth for local testing.
  175. ---
  176. ## Running Evals
  177. Each tool is tested with one direct prompt and one inferred prompt. Both runs load the target tool plus four distractors, then the same cases can be replayed across models. Outcomes are committed as JSON so we do not re-run the whole suite; GitHub Pages rebuilds the report from those files. The approach and full workflow are in [evals.md](evals.md).
  178. **New tools** must ship with cases under `evals/cases/<resource>/<tool>.eval.ts`. Authoring conventions: [`.agents/skills/writing-evals/SKILL.md`](.agents/skills/writing-evals/SKILL.md).
  179. ### View outcomes locally
  180. ```bash
  181. npm run eval:site
  182. open evals/site/index.html
  183. ```
  184. No model API keys required. The published report is at <https://vantage-sh.github.io/vantage-mcp-server/>.
  185. ### Run a new eval
  186. Set `ANTHROPIC_API_KEY` and/or `OPENAI_API_KEY` in `.env`, then:
  187. ```bash
  188. npm run eval -- --tool <your-tool> --model gpt-5.6-sol-high
  189. ```
  190. `--model` is required (`npm run eval -- --list-models` prints the catalog). That writes `evals/results/<model>/<resource>/<tool>.json` and leaves every other result file untouched. Commit the new JSON.
  191. ### Overwrite an eval
  192. Re-run the same `--tool` and `--model`. The JSON for that pair is replaced. Do this after changing a tool's description, schema, or prompts — you do not need to re-run every model unless you want those baselines refreshed too.
  193. ---
  194. ## Available Scripts
  195. - `npm run dev` — Start the Wrangler development server
  196. - `npm run local` — Run the stdio MCP server locally
  197. - `npm run inspect` — Launch the MCP inspector
  198. - `npm run test` — Run Vitest
  199. - `npm run format` / `npm run lint:fix` — Biome format and lint
  200. - `npm run type-check` — TypeScript check
  201. - `npm run cf-typegen` — Generate Cloudflare Worker types
  202. - `npm run generate-tools-index` — Regenerate `src/tools/index.ts` after tool changes
  203. - `npm run generate-resources-index` — Regenerate `src/resources/index.ts` after resource changes
  204. - `npm run eval` — Run tool-selection evals (`npm run eval -- --tool <name> --model gpt-5.6-sol-high`)
  205. - `npm run eval:site` — Merge stored JSON and write `evals/site/index.html`
  206. - `npm run eval:view` — Open promptfoo's local results viewer
  207. ---
  208. ## Contribution Guidelines
  209. 1. Fork this repository and create a branch: `git checkout -b feature/my-feature`.
  210. 2. Make your changes.
  211. 3. Verify locally:
  212. ```bash
  213. npm run format
  214. npm run lint:fix
  215. npm run type-check
  216. npm test -- --run
  217. ```
  218. 4. Submit a [pull request](https://github.com/vantage-sh/vantage-mcp-server/pulls).
  219. See [AGENTS.md](/AGENTS.md) for conventions when adding tools, evals, or resources.
  220. ---
  221. ## License
  222. See [LICENSE.md](LICENSE.md) for commercial and non-commercial licensing details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.