# StackSpend MCP server

> Review cloud and AI spend, forecasts, anomalies, provider health and tasks from StackSpend.

- Listing: https://mcp.tc/i/stackspend
- Connect: use the server's own URL `https://api.stackspend.app/api/v1/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Finance & Payments](https://mcp.tc/c/finance-payments)
- Vendor: StackSpend
- Homepage: <https://stackspend.app/>

## About

Connects to StackSpend, a cost management product for cloud, database, developer-tool and AI spend. The OAuth scopes cover spend summaries, rollups, line items, provider status, anomalies, tasks, usage and webhooks, so an assistant can read forecasts and investigate cost changes.

The hosted endpoint runs over streamable HTTP and uses OAuth sign-in. A StackSpend Business subscription is required. A local npm setup is also documented by the vendor.

## What it can do

- Read cloud and AI spend summaries
- View spend forecasts
- Check provider connection health
- Browse rollups and line items
- Review cost anomalies
- Read and manage tasks

## Example prompts

- "Summarize our cloud and AI spend this month."
- "Which providers have cost anomalies this week?"
- "Show the month-end forecast against budget."
- "List line items behind the AWS spend increase."

## Install

### Claude Code

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

```bash
claude mcp add --transport http stackspend https://api.stackspend.app/api/v1/mcp
```

2. Start Claude Code, type `/mcp`, pick **stackspend** and choose **Authenticate**. A browser window opens for the StackSpend sign-in.

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

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **StackSpend** and paste this URL:

```url
https://api.stackspend.app/api/v1/mcp
```

3. Click **Add**, then **Connect**, and sign in when StackSpend 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](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=StackSpend&connectorUrl=https%3A%2F%2Fapi.stackspend.app%2Fapi%2Fv1%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://api.stackspend.app/api/v1/mcp` and click **Add**.

3. Click **Connect** and sign in when StackSpend 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, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://api.stackspend.app/api/v1/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to StackSpend to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=stackspend&config=eyJ1cmwiOiJodHRwczovL2FwaS5zdGFja3NwZW5kLmFwcC9hcGkvdjEvbWNwIn0%3D>) (opens Cursor)

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

`mcp.json`:

```json
{
  "mcpServers": {
    "stackspend": {
      "url": "https://api.stackspend.app/api/v1/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=stackspend&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.stackspend.app%2Fapi%2Fv1%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"stackspend","type":"http","url":"https://api.stackspend.app/api/v1/mcp"}'
```

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

`.vscode/mcp.json`:

```json
{
  "servers": {
    "stackspend": {
      "type": "http",
      "url": "https://api.stackspend.app/api/v1/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):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "stackspend": {
      "serverUrl": "https://api.stackspend.app/api/v1/mcp"
    }
  }
}
```

2. 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

```bash
codex mcp add stackspend --url https://api.stackspend.app/api/v1/mcp
codex mcp login stackspend
```

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

`config.toml`:

```toml
[mcp_servers.stackspend]
url = "https://api.stackspend.app/api/v1/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http stackspend https://api.stackspend.app/api/v1/mcp
```

Then, inside Gemini CLI, run `/mcp auth stackspend` 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.

```json
{
  "mcpServers": {
    "stackspend": {
      "type": "http",
      "url": "https://api.stackspend.app/api/v1/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://api.stackspend.app/api/v1/mcp`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/stackspend (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
