Ramp

@ramp show me all my transactions from the last 30 days and break down spending by category

Here's an illustrative summary of your Ramp transactions over the last 30 days: • Software & SaaS: $4,230 (12 transactions) • Travel & Lodging: $2,890 (5 transactions) • Meals & Entertainment: $1,450 (18 transactions) • Office Supplies: $340 (4 transactions) Total spend: $8,910 across 39 transactions. Your largest single transaction was $1,200 for AWS services on the 15th. Three transactions are still pending merchant categorization. Would you like me to drill into any specific category or flag unusual spending patterns?

This example demonstrates the MCP's read-heavy transaction retrieval paired with AI synthesis. The user needs OAuth2 access with transaction read scope. Note that category breakdowns depend on how your organization has configured merchant categorization rules in Ramp—uncategorized transactions may require manual review.

@ramp create a new department called 'Product Marketing' under the Marketing parent department with cost center code PMK-2024

Department created successfully: • Name: Product Marketing • Department ID: dept_abc123xyz • Parent: Marketing (dept_mkt001) • Cost Center: PMK-2024 • Status: Active This department is now available for expense allocation and reporting. Team members can be assigned to this department, and you can set department-specific spending policies or card limits. The department will appear in your accounting exports with the PMK-2024 cost center code for reconciliation.

This write example shows organizational structure management, a key Ramp capability for multi-team expense tracking. Requires OAuth2 with department write permissions. Be aware that creating departments affects your accounting hierarchy immediately—coordinate with finance before restructuring to avoid breaking existing expense allocation rules or reporting workflows.

@ramp pull details on all virtual cards I have access to and flag any that are approaching their monthly spending limit

Here's an illustrative overview of your virtual cards: **Card 1: AWS Infrastructure** (card_virt_001) • Limit: $5,000/month | Spent: $4,720 (94% utilized) ⚠️ • Expires: 12/2025 | Status: Active **Card 2: Marketing Tools** (card_virt_002) • Limit: $2,000/month | Spent: $890 (45% utilized) • Expires: 06/2026 | Status: Active **Card 3: Conference Travel** (card_virt_003) • Limit: $3,000/month | Spent: $150 (5% utilized) • Expires: 03/2025 | Status: Active Your AWS card is at 94% of its monthly limit—consider requesting an increase if you have planned infrastructure expenses this month.

This synthesis example combines card retrieval with spending analysis, useful for proactive budget management. The MCP returns card metadata and current spend; the AI layers on utilization warnings. Requires card read scope. Monthly limits reset based on your organization's billing cycle, and limit increases typically require manager approval through Ramp's workflow system.

When Ramp MCP speeds up expense reconciliation at small scale

A 15-person startup closing books each month spends 3-4 hours reconciling Ramp transactions in QuickBooks. The Ramp MCP wins here because the finance lead can pull all transactions, filter by department or custom field, and cross-check card assignments without toggling between Ramp's UI and their accounting system. The 22 tools cover the full reconciliation loop: fetch transactions, verify department tags, check card limits, and validate custom accounting fields. This works cleanly up to about 500 transactions per month. Beyond that threshold—or if you need multi-entity consolidation—you're better off using Ramp's native QuickBooks sync. The buying call: if your monthly close involves manual Ramp lookups and you're under 30 people, this MCP cuts reconciliation time in half.

How Ramp MCP supports ad-hoc vendor card requests

A 6-person agency handles one-off vendor payments (AWS credits, design tools, freelancer deposits) by issuing virtual cards on demand. The operations manager uses the Ramp MCP to create a virtual card, set a spending limit, assign it to the correct department, and pull the transaction history once the charge posts—all without leaving Slack or their project tracker. The MCP's card creation and retrieval tools make this faster than logging into Ramp's dashboard for each request. The trade-off: if you're issuing more than 10 cards a week, you'll want Ramp's approval workflows and policy engine instead of ad-hoc MCP calls. This scenario works best for teams under 20 people with low card-issuance volume. The call: use this MCP when vendor payments are infrequent and you want to keep approvals inside your existing chat or task tool.

When Ramp MCP helps ops track spend without a finance hire

A 25-person SaaS company without a dedicated finance person relies on the ops lead to track department spend each week. The Ramp MCP lets the ops lead pull all transactions by department, check which cards are active, and verify that custom accounting fields (like project codes) are tagged correctly. The MCP's department and custom field tools make this a 10-minute weekly check-in instead of a 45-minute Ramp UI session. The boundary: if you need budget alerts, spend forecasts, or policy enforcement, the MCP won't replace Ramp's native reporting or a proper finance tool like Mosaic. This works for teams under 40 people where spend tracking is manual and the ops lead owns the process. The call: if you're pre-finance-hire and need lightweight spend visibility, the Ramp MCP keeps you out of the dashboard.