Rydoo

Manage your Rydoo expenses

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Rydoo MCP connects ChatGPT to your Rydoo account, so you can manage your expenses through everyday conversation instead of navigating the app. Sign in once with your existing Rydoo login — ChatGPT can then only see and do what you're already permitted to do in Rydoo, using your own roles and permissions. Key features: - Read and analyse spend — search expenses you own or oversee by date, status, category, group, person or trip, pull up a single expense with a link into Rydoo, find card expenses still missing a receipt, and get server-computed totals per trip, person or project. - Process approvals — see what's waiting on you, then approve or reject an expense using your company's reject reasons. Every action is confirmed with you first and recorded under your name. - Answer questions — expense-policy Q&A: what's reimbursable, which limits apply, and similar. - Look up company records — find the right category, branch, group, person or trip to filter expenses by, and check your own roles, modules and currencies. - Review trips — look up trips and bookings you own or oversee, and tie expenses back to them. - Manage cards and wallets — list cards you hold, approve or oversee as finance, review matched and unmatched card transactions, check wallet balances, spend summaries and monthly statements, and request a virtual card with the limit you confirm. Requires the Rydoo Cards module. - Send feedback — report a bug or request a feature straight to Rydoo.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-09-23
Tool count: 20
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Rydoo has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

20 tools agents can invoke

Approve a Rydoo expense that is waiting for your approval. Approver-only. This tool has a real effect in Rydoo and cannot be undone from here, so always confirm the specific expense with the user before calling it. Approving an expense that is already approved is safe and has no additional effect. Get the id from 'list_expenses' with 'role': 'Approver' and 'pendingForMe': true.
approve_expense
Ask Rydoo's Expense Policy Assistant a natural-language question about a company's expense policy (e.g. limits, allowed categories, receipt requirements). Returns a grounded, text answer and a sessionId to continue the conversation. The branch whose policy is answered is resolved automatically from the signed-in user's group assignments.
ask_policy_assistant
Resolve a company branch (legal entity / office) by name (substring match) into its id, or omit 'name' to list all branches. Use this before filtering expenses or spend summaries by branch, or before requesting a virtual card: look the branch up here, then pass the returned id as 'branchId'. When resolving a branch for a role-scoped expense operation, pass the same 'role' you will pass to 'list_expenses' or 'get_expense_summary'. Returns a markdown table plus structured rows, both carrying the id. Results are capped at 'limit' (default 25, max 100). Read-only.
find_branch
Resolve an expense category by name (substring match) into its id, or omit 'name' to list all categories. Use this before filtering expenses or spend summaries by category: look the category up here, then pass the returned id as 'categoryId' to 'list_expenses' or 'get_expense_summary'. Returns a markdown table plus structured rows, both carrying the id. Results are capped at 'limit' (default 25, max 100). Read-only.
find_category
Resolve a cost center (also called a group) by name (substring match) into its id, or omit 'name' to list all cost centers. Use this before filtering expenses or spend summaries by cost center: look it up here, then pass the returned id as 'groupId' to 'list_expenses' or 'get_expense_summary'. Returns a markdown table plus structured rows, both carrying the id. Results are capped at 'limit' (default 25, max 100). Read-only.
find_group
Resolve a person (colleague / expense owner) by name (substring match) into their user id, or omit 'name' to list all people. Use this to narrow expense lists or spend summaries to one named person: look them up here, then pass the returned id as 'ownerId' to 'list_expenses' or 'get_expense_summary'. Returns a markdown table plus structured rows, both carrying the id. Results are capped at 'limit' (default 25, max 100). Read-only.
find_owner
Find Rydoo trips by name (substring match), or omit 'name' to list all trips. 'role' is the SIGNED-IN USER'S OWN acting role — NOT the role of the person you are asking about. Pass the same 'role' you will pass to 'list_expenses': Personal returns only the caller's own trips, while Approver, Controller, Director or Finance returns trips across that role's scope, attributed via the Owner column. Returns a markdown table plus structured rows. By default, render the returned markdown table to the user verbatim unless the user asked for a different format; the structured rows are for programmatic use. When a user asks about a hotel or booking, look up the trip here first, then list its expenses via 'list_expenses' using the trip's id as 'tripId'. Results are capped at 'limit' (default 25, max 100) and may be incomplete for very common names — narrow the name to disambiguate. Read-only.
find_trip
Get the full details of a Rydoo expense by id. Can open an expense in any role the caller holds (Personal, Approver, Controller, Director or Finance); by default it uses the caller's most powerful role, so pass 'role': 'Personal' to open the caller's own copy. When the expense was rejected, the rejection reason is included. Returns a markdown detail block plus structured content. By default, render the returned markdown to the user verbatim — as a markdown list keeping every field present (Amount, Date, Status, Type, Category, Trip, Project, Receipt, No-receipt reason, Invoice number, Comment, Reference and Link) plus any Rule violations and Rejection sections, and the merchant heading when one is shown — unless the user asked for a different format. The structured content includes a 'deepLink' and a ready-to-use markdown 'link'; whenever you present the expense, always keep that link so the user can open it. Read-only; returns only an expense the caller is allowed to access. Resolve the id and its 'type' from 'list_expenses' first; the 'type' must match the listed row's type.
get_expense
Resolve the signed-in user's Rydoo context: their name, company, the roles they hold (ordered from most to least powerful), their most powerful role, which product modules are enabled, and their display and default currencies. The display currency is what the user wants amounts shown in and should be used by default when fetching expenses (for example 'list_expenses' or 'get_expense'). Call this once to learn which roles the user may act as before using role-aware tools (for example 'list_expenses' or 'list_cards'), then pass only a role the user actually holds. Returns a markdown summary plus structured fields. Read-only.
get_user_context
Get a finance wallet's card spend summary for a relative period such as ThisMonth. Returns total, virtual, physical, and pending spend for one wallet. Use 'list_wallets' first to get the wallet id. Read-only; finance-only.
get_wallet_spend_summary
List the allowed currencies and maximum amounts for requesting a self-service virtual card in the current user's branch. Read-only.
list_branch_card_currencies
List Rydoo card transactions visible to the signed-in user, focused by default on transactions not yet matched to an expense. 'role' is the SIGNED-IN USER'S OWN acting role — NOT the role of the person you are asking about; to ask about a colleague, keep the caller's own role and pass that colleague's id as 'ownerId'. Use 'role=Personal' for the caller's own transactions or 'role=Finance' for the company transactions a Finance user is allowed to see; the server rejects a role the caller does not hold. Returns a markdown table plus structured rows; each row includes a 'deepLink' and a ready-to-use markdown 'link', so present the per-row link instead of the raw transaction id. By default, render the markdown table verbatim unless the user asked for a different format. Read-only.
list_card_transactions
List Rydoo cards visible to the signed-in user. 'scope' is the SIGNED-IN USER'S OWN visibility scope — NOT the role of a card holder. Use 'scope=Mine' for the caller's own cards, 'scope=Approver' for cards visible to the caller through the approver workflow, or 'scope=Finance' for the finance-scoped company cards the caller is allowed to view; the server rejects a scope the caller does not hold. Returns a markdown table plus structured rows. By default, render the markdown table verbatim unless the user asked for a different format. Read-only.
list_cards
List Rydoo expenses, filtered in plain language. 'role' is the SIGNED-IN USER'S OWN acting role — NOT the role of the person you are asking about. To ask about a colleague, keep the caller's own role and pass that colleague's id as 'ownerId'. Personal returns only the caller's own expenses, Approver the approver's team, Controller the controllable scope, and Finance/Director the company scope; the server rejects a role the caller does not hold. Returns a markdown table plus structured rows. For a 'what's waiting on me' queue, set 'pendingForMe': true (the server picks the right statuses per role). Resolve category / branch / cost-center (group) / person and trip names to ids with the 'find_category', 'find_branch', 'find_group', 'find_owner' and 'find_trip' tools first, then pass those ids. By default, render the returned markdown table to the user verbatim (do not reformat or summarize it) unless the user asked for a different format; the structured rows are for programmatic use such as chaining into other tools. Each structured row includes a 'deepLink' and a ready-to-use markdown 'link'; whenever you present expenses, always keep that per-row link so the user can open each expense. Read-only; returns only expenses the caller is allowed to access. Set 'groupBy' to get a spend summary — server-computed totals per trip, person or project instead of individual expense rows.
list_expenses
List the active reject reasons configured for your company. Approver-only. Call this before 'reject_expense' and pass one of the returned ids as 'reasonId' — the model must never invent, guess, or paraphrase a reason. Reasons flagged 'requiresYourOwnWords' expect an additional free text note supplied as 'message' on 'reject_expense'. Results are paged: when 'hasMore' is true, fetch the next page using the returned 'nextOffset' or narrow 'search'. Read-only.
list_reject_reasons
List monthly statement rows for one finance wallet. Returns beginning balance, debit, credit, pending, and ending balance per month. Use 'list_wallets' first to get the wallet id. Read-only; finance-only.
list_wallet_monthly_statements
List finance wallets visible to the signed-in user so a wallet can be selected for spend-summary and monthly-statement tools. Optionally filter to wallets linked to one branch by passing 'branchId' from 'find_branch'. Returns wallet JSON with ids included so a wallet can be selected for follow-up tools. Read-only; finance-only.
list_wallets
Reject a Rydoo expense that is waiting for your approval, with a reason chosen from the company's configured list. Approver-only. This tool has a real effect in Rydoo and cannot be undone from here, so always confirm the specific expense with the user before calling it. Always call 'list_reject_reasons' first and pass one of the ids it returned as 'reasonId' — never invent, guess, or paraphrase a reason. Only supply 'message' when the chosen reason is flagged 'requiresYourOwnWords', and then only with the user's own words. Rejecting an expense that is already rejected is safe and has no additional effect. Get the expense id from 'list_expenses' with 'role': 'Approver' and 'pendingForMe': true.
reject_expense
Request a virtual card for yourself. Self-service only: the tool resolves your current eligible branch automatically, and resolves the limit currency automatically when there is exactly one allowed option or when your preferred currency matches an allowed option. Use 'list_branch_card_currencies' first when you want to confirm or disambiguate the currency. Ask for different details based on card type: SingleUse needs only the card details and the total limit amount. MultipleUse needs a recurring limit frequency and a total limit amount, and you should ask for the frequency before you ask for the limit amount. The request may enter a pending approval flow in Rydoo.
request_virtual_card
Send free-text feedback about the Rydoo MCP server (bugs, missing capabilities, general remarks) to the Rydoo team. Returns a short confirmation. Use this when the user wants to report a problem or request an improvement.
submit_feedback

Rydoo FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.

Get alerts for Rydoo

ChatGPT Plugin discovery is coming soon

Competitive lineup

20 tools agents can invoke