We built a Claude MCP server (BuyBot) that can execute purchases across all our business accounts, but it requires approval from a centralized budget authority before spending a single dollar. It’s changed how we handle expenses, inventory replenishment, and vendor management.
The Problem
We manage 19 WordPress sites, each with different budgets. Some are client accounts, some are owned outright, some are experiments. When we need to buy something—cloud credits, plugins, stock images, tools—we were doing it manually, which meant:
– Forgetting which budget to charge it to
– Overspending on accounts with limits
– Having no audit trail of purchases
– Spending time on transaction logistics instead of work
We needed an agent that understood budget rules and could route purchases intelligently.
The BuyBot Architecture
BuyBot is an MCP server that Claude can call. It has access to:
– Account registry: All business accounts and their assigned budgets
– Spending rules: Per-account limits, category constraints, approval thresholds
– Payment methods: Which credit card goes with which business unit
– Vendor integrations: APIs for Stripe, Shopify, AWS, Google Cloud, etc.
When I tell Claude “we need to renew our Shopify plan for the retail client,” it:
1. Looks up the retail client account and its monthly budget
2. Checks remaining budget for this cycle
3. Queries current Shopify pricing
4. Runs the purchase cost against spending rules
5. If under the limit, executes the transaction immediately
6. If over the limit or above an approval threshold, requests human approval
7. Logs everything to a central ledger
The Approval Engine
Not every purchase needs me. Small routine expenses (under $50, category-approved, within budget) execute automatically. Anything bigger hits a Slack notification with full context:
“Purchasing Agent is requesting approval:
– Item: AWS credits
– Amount: $2,000
– Account: Restoration Client A
– Current Budget Remaining: $1,200
– Request exceeds account budget by $800
– Suggested: Approve from shared operations budget”
I approve in Slack, BuyBot checks my permissions, and the purchase executes. Full audit trail.
Multi-Business Budget Pooling
We manage 7 different business units with different profitability levels. Some months Unit A has excess budget, Unit C is tight. BuyBot has a “borrow against future month” option and a “pool shared operations budget” option.
If the restoration client needs $500 in cloud credits and their account is at 90% utilization, BuyBot can automatically route the charge to our shared operations account (with logging) and rebalance next month. It’s smart enough to not create budget crises.
The Vendor Integration Layer
BuyBot doesn’t just handle internal budget logic—it understands vendor APIs. When we need stock images, it:
– Checks which vendor is in our approved list
– Gets current pricing from their API
– Loads image requirements from the request
– Queries their library
– Purchases the right licenses
– Downloads and stores the files
– Updates our inventory system
All in one agent call. No manual vendor portal logins, no copy-pasting order numbers.
The Results
– Spending transparency: I see all purchases in one ledger
– Budget discipline: You can’t spend money that isn’t allocated
– Automation: Routine expenses happen without my involvement
– Audit trail: Every transaction has context, approval, and timestamp
– Intelligent routing: Purchases go to the right account automatically
What This Enables
This is the foundation for fully autonomous expense management. In the next phase, BuyBot will:
– Predict inventory needs and auto-replenish
– Optimize vendor selection based on cost and delivery
– Consolidate purchases across accounts for bulk discounts
– Alert me to unusual spending patterns
The key insight: AI agents don’t need unrestricted access. Give them clear budget rules, approval thresholds, and audit requirements, and they can handle purchasing autonomously while maintaining complete financial control.
Leave a Reply