Ramp MCP
Ramp MCP lets authorized users analyze spend and manage cards, bills, reimbursements, approvals, transactions, and other permitted Ramp resources.
Verdict
Common use cases
- Approve reimbursements from Slack or chat
- Check if a purchase violates policy
- Activate new employee cards instantly
- Pull last week's spend by category
- Add team members to shared budgets
Integration
- Vendor
- Ramp MCP
- Category
- other
- Auth
- OAUTH2
- Tools
- 50
- Composio slug
ramp_mcp
Tools
- Ramp activate card
Activates an unactivated card for the user. If the card is a physical card awaiting delivery confirmation, call this tool first without confirm_delivery to detect the state, then call again with confirm_delivery=True after the user confirms
- Ramp add traveler loyalty program
Compatibility route for callers that have not migrated to SetTravelerLoyaltyProgram
- Ramp add user to shared fund
Provide user_email for a human or agent_id for a standalone agent; role defaults to MEMBER.
- Ramp agent account numbers
Returns active agent-managed account numbers and all payment details available for receiving funds.
- Ramp answer policy question
Use this tool when the user asks about expense policy rules, spending limits, fund restrictions, or whether certain purchases are allowed under company policy.
- Ramp api keys
Results are sorted by estimated cost in descending order, then by API key ID in ascending order. A request can match at most 10,000 API keys. Use the providers or statuses filter to narrow larger result sets. Estimated cost is calculated f
- Ramp approve or reject bill
The authenticated user must be the next required approver on the bill's approval chain. Rejection is additionally allowed for bill-pay admins as an override, even when they are not the next approver. Find bills awaiting the authenticated us
- Ramp approve or reject reimbursement
Use this tool when the user wants to approve or reject a reimbursement. Reimbursements are employee-submitted requests for reimbursement of out-of-pocket expenses. Common usage patterns: "approve this reimbursement", "reject the expense", "
- Ramp approve or reject request
Use this tool when a user wants to approve or reject a specific request they have identified or referenced. Common usage patterns: "approve this request", "reject this request", "accept the request", "deny this", "authorize this", "yes appr
- Ramp approve or reject transaction
Use this tool when the user wants to approve a transaction, send it back for revisions, or require the cardholder to repay the full amount. The acting user must have the proper approval authority for the transaction. If the user provides a
- Ramp archive spend allocation
Archive a fund to prevent spend and hide it from users
- Ramp award sourcing event
closing its current RFX. Prerequisites: grading must be complete on the current RFX, the event must not already be awarded or pending award approval, and the payee must be an active invited vendor on the RFX. When the business configures a
- Ramp cancel reimbursement payment
Cancel the payment on a reimbursement that has been approved but not yet paid out
- Ramp close sourcing event
Closing cascades to every non-terminal child RFX: each is transitioned to CLOSED, which blocks further vendor submissions and grading and voids any outstanding e-sign envelopes. Closed events are hidden from default list views and become re
- Ramp complete transaction revision
Use this after the cardholder has addressed the requested changes and explicitly asks to mark the transaction revision complete. The completion refreshes the corresponding task and starts Task Platform's sanction-lifting workflow.
- Ramp create department
Department names are unique within the business (case-insensitive). If a department with the requested name already exists, it is returned instead of creating a duplicate.
- Ramp create draft bill
Returns the draft UUID, initial version, and Ramp URL. This does not start approval, schedule, release, or initiate payment. Omitted fields remain empty, so the new draft may not yet be ready for submission.
- Ramp create draft spend request from sourcing event
spend request pre-filled with the winning vendor's context. The draft is prefilled from the sourcing conversation, event details, and (when ``rfx_id`` is passed) the awarded vendor's RFX responses. The user reviews and submits the draft in
- Ramp create fund request
Always use this tool (never invent URLs) and include the returned url in your next message. Prefer spend-program request tools first when available; use this for one-off/default funds or when no program fits. Infer fields from context; do n
- Ramp create pending payee
Call SearchVendors first with include_draft=true. Reuse a suitable existing vendor, including a pending vendor, instead of creating a duplicate. Never create a duplicate to work around an existing vendor whose status is INACTIVE — an admin
- Ramp create reimbursement from receipt
Pass amount/currency_code/transaction_date/merchant to skip OCR.
- Ramp create rfx
event in the same call. Nothing is sent to vendors until the RFX is published. Use GetRFXDetail to review the created questionnaire and InviteVendorsToRFX to add vendors before publishing.
- Ramp create trip
Do not call this solely as a prerequisite for booking a flight or hotel; SubmitFlightBooking and SubmitHotelBooking automatically select or create a trip when trip_id is omitted. If the user explicitly asks to create a named trip in additio
- Ramp delete procurement draftdestructive
Delete an abandoned procurement draft owned by the acting user
- Ramp delete reimbursementdestructive
Deletion is permanent and only allowed for reimbursements the acting user is permitted to delete (their own drafts, or others' if they have write access). Reimbursements that have progressed too far in the payment lifecycle cannot be delete
- Ramp delete spend programdestructive
Use this tool when an admin wants to permanently delete a spend program. If the program has linked funds (spend allocations), the caller must specify what to do with them via spend_intent_delete_action: - "terminate": Close all linked fund
- Ramp departments
Returns the departments available in the user's business, which can be used as inputs to workflows that require department references. Each department includes organizational metadata: its owners (managers), active member count, and managin
- Ramp drawdown requests
Creates a wire drawdown request from an external bank account. The request may require approval, and funds arrive only if the external bank fulfills it. Requires an `X-Idempotency-Key` header.
- Ramp duplicate reimbursement
Duplicate an existing reimbursement as a new draft
- Ramp edit reimbursement
Omitted fields stay unchanged; null/[] clear when editable.
- Ramp edit transaction
Returns the updated transaction, remaining missing items, and a transaction_link for fields the API cannot edit.
- Ramp edit user role on shared fund
Change a shared-fund user's role between member and co-owner using user_email
- Ramp enable shared fund access
Use this when a user wants to turn an existing personal fund into a shared fund, or when adding a member requires sharing to be enabled first.
- Ramp enroll business in agent cards
Enroll the current business in agent cards for agentic commerce
- Ramp estimate mileage reimbursement
Estimate the reimbursement amount for a given mileage distance based on the user's company rates
- Ramp estimate per diem amount
Estimate the per diem reimbursement amount for a trip given start/end dates and optional meal deductions
- Ramp events
Get audit log events
- Ramp execute analyst query
First use the analyst catalog and read the domain docs for every table in the query; those docs define supported tables, columns, joins, and metric semantics.
- Ramp fund x402 wallet
Before calling, use ListBusinessAccounts to obtain the source account UUID; never guess it. Confirm the exact source account and positive USD amount with the user before creating this irreversible transfer. MCP and CLI callers must provide
- Ramp get account balance history
Use when the user asks about balance history for a specific account, savings account trend, checking account balance over time, or the balance trend for a specific Ramp Checking Account. This tool only supports Ramp Checking Accounts, not I
- Ramp get agent card creds
Handles card enrollment and purchase instructions automatically.
- Ramp get agent card funds
Returns eligible funds with available balance.
- Ramp get ai token spend aggregates
Aggregate AI token usage or estimated cost over a time window, grouped by caller-selected dimensions (provider, model, configuration, department, user, or API-key tag group)
- Ramp get ai token spend connections
Use GetAiTokenSpendCurrentSpend for actual vendor spend and GetAiTokenSpendAggregates for estimated token usage and cost.
- Ramp get ai token spend current spend
Requires transaction, reimbursement, or bill read access.
- Ramp get ai token spend filter options
List the dimensions and values available for AI-spend aggregate queries: providers, models, model families/facets, departments, and API-key tag groups
- Ramp get analyst catalog
Review the catalog before writing a query, then read domain docs for every table used.
- Ramp get analyst metric metadata
Discover supported analyst metrics and starter SQL for aggregate business analysis
- Ramp get analyst spend facts domain docs
Read domain documentation for analyst.spend_facts before using it in an analyst query
- Ramp get analyst table domain docs
Read domain documentation for an analyst table before using it in an analyst query
Setup
Setup guide
- 11. In Switchy, open your workspace settings and click 'Add Integration' under MCP Servers. 2. Select Ramp MCP from the list and click 'Connect'. 3. You'll be redirected to Ramp's OAuth consent screen — sign in with your Ramp admin account. 4. Grant the requested scopes: read access to cards, transactions, users, and policies; write access to approvals, reimbursements, and card activation. 5. After authorization, Switchy redirects you back and confirms the connection. 6. Open any Project, type '@Ramp' in a message, and ask 'What cards are pending activation?' to verify the integration works. 7. If the response lists cards or confirms none are pending, you're ready to use all 50 tools.
What teammates see: by default, memories from Ramp MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Activate Pending Cards
@Ramp show me all cards that need activation, then activate the one assigned to the newest employee.
Policy Check
@Ramp can I expense a $200 dinner with a client under our travel and entertainment policy?
Approve Reimbursements
@Ramp show me all reimbursements I need to approve, then approve the one from Sarah if it's under $500.
Add User to Fund
@Ramp add jordan@company.com to the Marketing Fund as a member so they can book ads.
Review Recent Spend
@Ramp list all transactions from the last 7 days over $1000 and group them by merchant category.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@ramp what's our company policy on software subscriptions under $100 per month?
Based on your company's expense policy in Ramp, software subscriptions under $100/month fall under the 'Software & SaaS' category with automatic approval for employees in Engineering and Product departments. Subscriptions require manager approval for other departments. All subscriptions must include a business justification in the memo field. Annual prepayments exceeding $1,000 require Finance team review regardless of monthly cost.
This example shows the policy-question tool interpreting your organization's configured ruleset. The actual policy details will vary by company. Ramp requires admin-level OAuth scope to read policy configurations, and responses reflect rules as they're defined in your Ramp account at query time.
@ramp approve reimbursement #R-2847 for Sarah's client dinner last Tuesday
Reimbursement #R-2847 has been approved. Details: $127.43 submitted by Sarah Chen for client dinner at Osteria Mozza on January 14, 2025. Receipt verified, expense coded to 'Client Entertainment' (account 6250). Funds will be deposited to Sarah's linked bank account within 3-5 business days. You were listed as the required approver on this request.
This demonstrates the approval workflow tool taking action on your behalf. The authenticated user must be the designated approver in the reimbursement chain, or hold bill-pay admin privileges for override capability. This write operation is irreversible through the MCP—reversals require the Ramp web interface.
@ramp show me all API keys we have active and flag any that look expensive based on recent usage
Found 7 active API keys across your Ramp account. Sorted by estimated monthly cost: (1) Stripe production key – est. $340/mo in transaction fees, last used 2 hours ago. (2) AWS infrastructure key – est. $180/mo, last used 18 minutes ago. (3) SendGrid email key – est. $45/mo, last used yesterday. Four additional keys show minimal usage under $10/mo each. The Stripe key has processed 2,300+ transactions this month, significantly above your 6-month average of 1,800.
This synthesis example pairs Ramp's API key listing tool with the AI's ability to rank and summarize cost patterns. Results are capped at 10,000 keys per request—use provider or status filters if your organization exceeds this threshold. Cost estimates derive from Ramp's transaction data and may lag real-time usage by several hours.
Use-case deep-dives
When Ramp MCP handles pre-trip card activation and loyalty setup
A 12-person sales team books flights and hotels monthly through corporate cards. Before this MCP, ops spent 20 minutes per trip activating physical cards and entering loyalty numbers manually. The Ramp MCP automates both: activate_card detects delivery state and confirms activation in one call, then add_traveler_loyalty_program syncs frequent-flyer accounts without opening the Ramp dashboard. This works when your team issues 10-30 cards per month and loyalty programs are standardized (Delta, Marriott, Hilton). If you're issuing 100+ cards monthly or need custom approval workflows per trip, the 50-tool scope here is overkill—you'd script directly against Ramp's API. For mid-volume travel ops, this MCP cuts card-prep time to under 2 minutes per traveler.
Using answer_policy_question to triage flagged transactions at close
A 6-person finance team closes books on the 5th of each month and reviews 200-400 flagged transactions for policy compliance. The answer_policy_question tool lets an AI agent surface the exact policy rule (spending limit, category restriction, fund eligibility) that applies to each flagged charge, so the team triages violations in Slack instead of toggling between Ramp's UI and a policy PDF. This scenario wins when your policy doc is already in Ramp's system and you're reviewing under 500 transactions per close. Above that volume, the MCP's OAuth2 token refresh becomes a bottleneck—you'd want a dedicated Ramp integration with cached policy data. For small finance teams doing monthly audits, this MCP turns a 4-hour review into a 90-minute Slack thread.
When approve_or_reject_reimbursement replaces email-based expense review
A 9-person product team runs async standups in Notion, where managers review and approve employee reimbursements (conference tickets, coworking passes, home-office gear). The approve_or_reject_reimbursement tool surfaces pending requests in the standup doc and lets managers approve or reject with a single command, no Ramp login required. This works when you process 5-20 reimbursements per week and approvers are already in a shared workspace. If your approval chain has 3+ layers or you need audit trails with custom metadata, the MCP's single-approver model won't cover it—you'd need Ramp's native approval workflows. For flat teams with straightforward reimbursement policies, this MCP keeps approvals in the same tool where work happens.
Frequently asked
What does the Ramp MCP let me do in Switchy?
It connects your Ramp corporate card and expense platform to Switchy's AI workspace. You can activate cards, approve or reject bills and reimbursements, check policy rules, manage user fund access, and pull account details—all without leaving your chat. It's built for finance teams who want to handle Ramp workflows conversationally instead of clicking through the web app.
Do I need admin access in Ramp to connect this MCP?
Yes. The OAuth2 flow requires permissions to read account data, manage cards, and approve transactions. If you're a standard employee without bill-pay or card-admin rights in Ramp, the connection will succeed but most tools will return permission errors. Connect it with a finance-admin account or ask your Ramp owner to grant the necessary roles first.
Can the Ramp MCP create new virtual cards or issue physical cards?
No. It can activate cards that already exist in Ramp (including confirming delivery of physical cards), but it can't issue new ones. Card creation still happens in the Ramp dashboard. Once issued, you can use the MCP to activate, suspend, or check spend limits on those cards through Switchy.
Why use this instead of just logging into Ramp's web app?
Speed and context. If you're already working in Switchy—reviewing a budget thread, chatting with your team—you can approve a bill or answer a policy question inline without tab-switching. The MCP also lets you script repetitive tasks (bulk approvals, policy lookups) in a way Ramp's UI doesn't support. For one-off card orders, the web app is still faster.
Who on my team should connect the Ramp MCP?
Your finance lead or whoever approves bills and manages card spend in Ramp. If multiple people share approval duties, each can connect their own Ramp account to Switchy; the MCP respects Ramp's approval-chain rules, so approvals route correctly. Standard employees can connect it to check their own card status or ask policy questions, but they won't see company-wide transaction data.