Spend Guard MCP Server

What this does

Spend Guard exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

SPEND_GUARD_POLICY
SPEND_GUARD_RAILS
SPEND_GUARD_LEDGER
SPEND_GUARD_DASHBOARD_PORT
SPEND_GUARD_APPROVAL_TIMEOUT
SPEND_GUARD_MOCK_NETWORK
ARC_PRIVATE_KEY
NEAR_ACCOUNT_ID
NEAR_PRIVATE_KEY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Spend Guard?

Run the Claude Code command in the install section to add Spend Guard to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Spend Guard?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Spend Guard as well.

Does Spend Guard need an API key?

Yes. Before it can run, set these environment variables: SPEND_GUARD_POLICY, SPEND_GUARD_RAILS, SPEND_GUARD_LEDGER, SPEND_GUARD_DASHBOARD_PORT, SPEND_GUARD_APPROVAL_TIMEOUT, SPEND_GUARD_MOCK_NETWORK, ARC_PRIVATE_KEY, NEAR_ACCOUNT_ID, NEAR_PRIVATE_KEY. They go in the env block of your MCP config.