Access and permissions

The MCP server respects each user's existing Ramp permissions, with an extra layer of admin-managed access control on top.

Controlling who can use MCP

Admins control which employees can use Ramp MCP from the dashboard:

1. Navigate to Company → Integrations → Ramp MCP.
2. Select Manage Access.
3. Set restrictions based on roles, departments, or specific users.

Permission tiers

• Employee tools are available to all users but respect individual permissions — a user only sees the funds, cards, and transactions tied to their account.
• Admin and business-owner tools can expose company-wide data such as spend exports, vendors, accounting categories, departments, entities, and treasury balances.
• Agent Card tools require Agent Cards enrollment, an active fund, and the scopes and permissions needed to generate agentic card credentials.

The MCP tools reference lists tool schemas generated from production. It does not override Ramp permissions. A listed tool can still be unavailable to a user who lacks the underlying access.

Session lifetime

• Read-only sessions expire one week after last use.
• Read-write sessions expire 24 hours after last use.

As long as the agent makes at least one call within the refresh window, the session keeps rolling and doesn't expire.

Limits and quirks

• Query result cap: MCP returns up to 100 rows per query. Ask the agent for a narrower time range, vendor, cardholder, department, or other filter when a query is too broad.
• File uploads: MCP connections do not currently pass receipt images or PDFs from chat attachments into Ramp MCP tools.
• Tool refresh: Clients cache tool schemas. Reconnect Ramp after new tools ship or after changing a user's access.
• ETL data tables: If a data-table operation hits a limit, ask the agent to drop unused tables or narrow the request. Persistent errors usually clear after in-flight operations finish.

See Troubleshooting for connection and auth issues.