Direct answer: Finta's Aurora catalog includes Ramp's remote MCP server at https://mcp.ramp.com/mcp. Ramp documents tools for supported spend, transaction, card, funds, vendor, budget, request, reimbursement, approval, and help workflows, with every action constrained by the connected user's Ramp role and permissions.
This guide is for teams using Finta as relationship intelligence around a capital, investor, customer, or company-building workflow. Ramp remains the source system for its records. Aurora can use only the context and actions exposed to the connected account.
How the Ramp connection works
| Connection detail | Current Finta guidance |
|---|---|
| Classification | Catalog MCP |
| Configured endpoint | https://mcp.ramp.com/mcp |
| Authentication and transport | Provider OAuth through Aurora; Streamable HTTP |
| Source of truth | Ramp remains authoritative for provider records, permissions, and action results. |
| Human control | Review external communication, record changes, financial actions, publishing, deletion, and other consequential work before execution. |
What you can use it for
- Read supported transaction, spend, vendor, budget, card, and funds context.
- Review requests, reimbursements, approvals, and policy information exposed to the connected user.
- Prepare a spend or approval analysis with source links and stated filters.
- Take a supported approval action only when the user is an authorized approver and explicitly confirms it.
- Use Ramp's audit trail to attribute actions taken through the connection.
These uses summarize the current provider documentation and Finta catalog purpose. The exact tool inventory varies by provider version, plan, workspace, user permissions, region, and authorization scopes.
Relationship intelligence workflows for Ramp
Prepare burn and vendor context for a board meeting
Outcome: Have finance approve the source-linked summary.
- Define the date range, entities, currencies, and spend categories.
- Retrieve relevant transactions, vendors, budgets, and account context.
- Flag exclusions, pending items, policy exceptions, and data gaps.
- Have finance approve the source-linked summary.
Human decision: Ramp data can support analysis but is not a replacement for reconciled accounting statements or finance approval.
Review a diligence-vendor spend request
Outcome: Record the resulting status without implying the vendor work is complete.
- Find the exact request, vendor, budget, policy, and approver chain.
- Summarize the business purpose and outstanding information.
- Ask the authorized approver to decide in Ramp.
- Record the resulting status without implying the vendor work is complete.
Human decision: Aurora must not approve, reject, issue funds, or change a limit without an authorized human decision.
How to connect Ramp to Aurora
- Ask a Ramp administrator to confirm the user can connect Ramp MCP.
- In Aurora, open Apps and select Ramp.
- Authorize https://mcp.ramp.com/mcp with the intended Ramp identity.
- Review role-based access and the requested scopes before completing OAuth.
- Begin with a read-only transaction, vendor, or budget lookup.
Open the official Finta apps directory to confirm the catalog entry before authorizing a provider account.
Permissions and approval boundary
Ramp preserves the connected user's role and permissions. Use read-only access first. Require explicit finance-owner confirmation for approvals, rejections, reimbursements, spend limits, cards, payments, funds, or other financial actions. Keep sensitive employee and transaction data restricted.
Limitations to understand
- Tool access depends on Ramp role, plan, organization policy, and the current server inventory.
- Some approval types or financial operations are not supported through Ramp MCP.
- A Ramp record may be pending, uncategorized, or unreconciled and should not be treated as final accounting.
- The catalog listing is not proof that every Ramp write action has been tested through Aurora.
Verification checklist
- Confirm the endpoint, OAuth identity, Ramp role, organization, and admin connection policy.
- Capture the exact Aurora-discovered tools and effective permissions.
- Run a safe read-only vendor, budget, or transaction lookup and retain the receipt.
- Test one controlled approval only with the authorized approver in a safe context, then verify Ramp's audit trail.
- Record unsupported approval types, plan gates, data caveats, and verification date.
Verification status: On 2026-08-22, Finta confirmed that this connector appears in the enabled production Aurora catalog and reviewed the configured endpoint, authentication type, and first-party sources listed below. This is not a claim that every provider tool or an authenticated end-to-end action has been tested for every account.
Official provider sources
- Ramp official MCP documentation (support.ramp.com)
- Ramp official MCP documentation 2 (agents.ramp.com)
- Ramp official MCP documentation 3 (agents.ramp.com)