Vantage MCP Server
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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.
About
The Vantage MCP Server exposes tools for listing, querying, and creating Vantage resources. Tools are defined in /src/tools; see the Vantage MCP documentation for the full tool list, prompting examples, and product details.
This repository supports two deployment modes:
| Mode | Best for |
| -------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| **Hosted (Remote) MCP** — Vantage-managed at https://mcp.vantage.sh/mcp | Most users and teams. OAuth sign-in, no local server to run. |
| **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. |
**Start with the hosted MCP** unless you have a specific reason to self-host.
Setup Instructions
General
The hosted MCP server uses 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.
**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 below).
**API token auth:** If your client or script cannot complete OAuth, pass a Vantage API token as a Bearer token instead:
Claude Code
Then run /mcp in a Claude Code session to complete the OAuth flow.
Codex
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:
To configure manually (for example, to commit .cursor/mcp.json to a repo):
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
Or use the command palette: **MCP: Add Server → Command (stdio)** and enter:
Windsurf
Under **Cascade → MCP servers → Add custom server**, add:
Zed
In Zed settings, add:
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 and the Vantage MCP documentation for additional clients (including ChatGPT via the Vantage app).