# @stackspend/mcp-server

Source: https://glimind.com/server/npm%2F-stackspend%2Fmcp-server
Registry id: `npm/-stackspend/mcp-server`
Status: unknown

## Install

```json
{
  "mcpServers": {
    "stackspend-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@stackspend/mcp-server"
      ]
    }
  }
}
```

Claude Code:

```sh
claude mcp add stackspend-mcp-server -- npx -y @stackspend/mcp-server
```

## Tools (14)

- `add_anomaly_comment`: Comment on an anomaly, attributed to the key's owner
- `create_task`: Create an optimisation task (syncs to a connected tracker)
- `get_anomalies`: Anomaly alerts with short id, status, overrun and likely related change
- `get_anomaly_detail`: One anomaly in full, including the ranked change log of PRs and deploys
- `get_daily_rollups`: Daily totals grouped by provider, service, category, project, user, account or model
- `get_forecast`: Month-end projection against budget, with confidence band and days until a breach
- `get_line_items`: Raw cost line items, cursor-paginated, with matching filters
- `get_providers`: Connection health per provider: last sync, last error, needs reconnect
- `get_savings`: Overspend caught by resolving anomalies (this month and lifetime)
- `get_spend_summary`: Yesterday, 7-day, 30-day and month-to-date spend with trend and status, overall and per provider
- `list_tasks`: FinOps tasks with severity, owner, estimated savings and linked Jira/Linear issue
- `set_anomaly_severity`: Set severity: low, medium, high or critical
- `update_anomaly_status`: Acknowledge, resolve, dismiss or mark false positive (resolve and dismiss need a note)
- `update_task`: Move a task to acknowledged, resolved, implemented, dismissed or false positive

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
