Requests

Requests are the approval primitive Qonto uses for spend that needs a second pair of eyes: someone asks for a card or a transfer, and an approver reviews it. Visibility and what you can do depend on your role. The MCP server lets you list and create requests, and decline them. Approving a request is done by the approver in the Qonto web app — the MCP server hands you a link to the approve page rather than approving on your behalf.

Tool	What it does	Upstream
`list_requests`	Paginated list of expense-management requests (flash card, virtual card, transfer, multi-transfer). Visibility is role-scoped: employees see their own, managers their team’s, admins and owners everything.	List requests
`create_card_request`	Create a card request (`flash` or `virtual`) for the authenticated membership. Needs approval before the card is issued.	Create a flash card request / Create a virtual card request
`create_multi_transfer_request`	Bundle 1 to 400 SEPA transfers into one approval batch. The approver later signs it with SCA in the Qonto web app.	Create a multi-transfer request
`approve_request`	Returns a link to the approve page for a pending request in the Qonto web app. The MCP server does not approve on your behalf; the approver reviews and confirms there, where the underlying action (transfer execution, card issuance) and any SCA take place.	Approve a request
`decline_request`	Decline a pending request. The request moves from `pending` to `declined`; the underlying action does not run.	Decline a request

Approvals happen in the Qonto web app, not through the assistant. When you ask to approve a request, approve_request returns a link to the approve page; you review and confirm there, completing any Strong Customer Authentication in the Qonto mobile app when prompted.

Try it

List my pending card requests. Give me the link to approve the transfer request from the design team. Decline the duplicate transfer request from yesterday.

Payment links Plans and pricing

⌘I

Install

Tools