# Ramp MCP MCP

Vendor: Ramp MCP  
Category: other  
Auth: OAUTH2  
Composio slug: `ramp_mcp`

Ramp MCP lets authorized users analyze spend and manage cards, bills, reimbursements, approvals, transactions, and other permitted Ramp resources.

## Verdict

Ramp MCP connects your team's corporate card and spend management platform to Switchy. @mention it to activate cards, check policy rules, approve bills and reimbursements, manage shared funds, or pull transaction data without leaving your Project. Finance admins use it to handle approvals in chat; employees use it to check spend limits or submit expenses. Requires OAuth with read/write scopes across cards, transactions, and approvals — setup takes 3-5 minutes if you're a Ramp admin.

## 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 draft** — Delete an abandoned procurement draft owned by the acting user
- **Ramp delete reimbursement** — 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 program** — 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

1. Create or open a Switchy Project.
2. Open Integrations and connect Ramp MCP.
3. Authorise through oauth2.
4. Teammates can now @-mention Ramp MCP tools in chat.

---
Last verified: 2026-10-17T02:00:10.360Z  
Canonical URL: https://switchy.build/directory/mcps/ramp-mcp