Back

Ramp

Manage your cards, bills, and spend.

MCP server URL

https://ramp.gumstack.com/mcp

Works with

Tools 214

  • Get Current User

    Get the current user's information (email, name, etc.)

  • Ramp Token Info

    Get Token Info Get token info: auth level, granted OAuth scopes, and any MCP tools that are unavailable to the current token along with the missing scopes needed to unlock them. Use this to debug why an expected tool is not listed.

  • Ramp Activate Card

    Activate a card by its last four digits. 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 the physical card has arrived.

  • Ramp Add Traveler Loyalty Program

    Add one loyalty program to the user's traveler profile. If success is true, stop calling tools and tell the user it is saved.

  • Ramp Answer Policy Question

    Get an answer to a question about the expense policy or funds (amount, restrictions, etc). 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 Approve Or Reject Reimbursement

    Approve or reject an employee reimbursement request for an out-of-pocket expense. 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", "yes, reimburse them", "no, don't reimburse this". This tool is specifically for employee reimbursements and is NOT for approving/rejecting card transactions or unified requests (spend allocations, purchase orders).

  • Ramp Approve Or Reject Request

    Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval. 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 approve it", "decline this request". This tool is specifically for unified requests (spend allocations, purchase orders, procurement approvals) and is NOT for approving expenses like corporate card transactions or reimbursements. The user must have proper approval authority for the request.

  • Ramp Approve Or Reject Transaction

    Approve or reject a transaction awaiting your review. 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 written justification (e.g., “reject this because the receipt is missing”), pass that verbatim via `user_reason`—do not invent your own rationale.

  • Ramp Cancel Reimbursement Payment

    Cancel the payment on a reimbursement that has been approved but not yet paid out.

  • Ramp Create Reimbursement From Receipt

    Create a reimbursement from an actual uploaded receipt. The receipt is identified by its real UUID from the conversation context or receipt-matching handoff. Do not use this tool for mileage reimbursements. Do not call this tool unless a real receipt UUID is available. Never pass placeholders such as null, "null", "mileage", or 00000000-0000-0000-0000-000000000000. When you have extracted receipt details from the image, provide amount, currency_code, transaction_date, and merchant directly. This creates the draft faster and more reliably than OCR. At minimum, provide the amount. Omit fields you could not extract. After successfully creating the reimbursement: 1. Check missing_items to see what is required 2. For items that CAN be filled via the agent (memo, accounting categories, funds, trip, attendees): - Request the missing item from the user - Include the relevant suggestions (suggested_memos or suggested_codings) - For funds, consult suggested_funds alongside the user's expense history and any preference the user has stated. suggested_funds is ordered by policy preference (most preferred first). Submitting without a fund appears as a regular entry (fund_name="None", fund_uuid="00000000-0000-0000-0000-000000000000") when policy permits it — treat it like any other choice and refer to it as "None" to the user. 3. For items that CANNOT be filled via the agent (mileage_locations, or if all agent-fillable items are complete): - ALWAYS provide the reimbursement_link URL as a clickable link in your response - Format it as markdown: [link text](reimbursement_link) - Example: "You can complete your reimbursement here: [Complete reimbursement](https://app.ramp.com:3000/s/reimbursements/xxx)" Items are requested in this order: receipt, memo, accounting categories, funds.

  • Ramp Create Trip

    Create a new trip for the acting user.

  • Ramp Departments

    List all departments in the company. Returns the departments available in the user's business, which can be used as inputs to workflows that require department references.