Skip to main content

Search

Hi there, how can we help?

About the Rydoo MCP server

  • Updated

🚧 Beta. The Rydoo MCP server is currently in beta. What it can do may change as we add features.

The Rydoo MCP server lets you connect your Rydoo account to an AI assistant like Claude and ask about your expenses in plain language, without opening the Rydoo app. You ask a question in your chat, and the assistant reads the answer directly from your Rydoo data.

This article explains what the Rydoo MCP server is, what you can do with it, and how your access works. To connect and start using it, see the related articles at the end.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI assistants securely connect to other tools and data sources, a bit like a plug-in system. Once an assistant is connected to a platform through MCP, it can read data from that platform to answer your questions.

The Rydoo MCP server is Rydoo's implementation of this standard. It gives your assistant a secure connection to your Rydoo data so you can ask about your expenses, trips, and policy directly in the assistant you already use.

What you can do

Depending on your roles and permissions in Rydoo, you can ask your assistant to:

  • Search your expenses by date, status, or trip
  • Find company card expenses that are still missing a receipt
  • Pull up the details of a specific expense
  • Look up and review your business trips, including status and spend
  • Ask expense-policy questions, such as what is reimbursable and which limits apply

For the full list and example prompts, see What you can do with the Rydoo MCP server.

💡These capabilities are still growing during beta. Actions that change data in Rydoo, such as creating or submitting expenses, are planned for a later release.

How access and security work

Your Rydoo permissions come with you. The connection respects your role and access: the assistant can only see data you're already allowed to see in Rydoo.

Access is secured with OAuth using your own Rydoo login. When you connect, a browser window opens Rydoo's login page, where you sign in with your username and password or via single sign-on (SSO), exactly as you would in the Rydoo web app. The assistant never sees your password. You approve access, then return to your assistant, ready to go.

Because access mirrors each person's Rydoo permissions, two people can ask the same question and see different results, based on what each is allowed to see.

How this differs from the Rydoo API

The Rydoo MCP server and the Rydoo API both reach your Rydoo data, but they're for different people. The Rydoo API needs developers to build integrations in code. The MCP server lets you query Rydoo in natural language from an AI assistant you already use, without code.

Common questions

Can the assistant change or approve anything in Rydoo?

No. This version is read-only. The assistant reads and explains your data but cannot yet create, edit, submit, or approve anything. Rydoo stays the single source of record.

Does the assistant see my password?

No. You sign in on Rydoo's own login page (username and password, or SSO) via OAuth. The assistant only receives permission to access your data and never your password.

What data can it access?

Only the data you can already see in Rydoo. Your existing role and permissions always apply.

Whose expenses can I ask about?

The first version answers questions about your own expenses.

Which AI tools are compatible?

Claude offers one-click setup today. The Rydoo MCP server also works with ChatGPT, Claude Code, Cursor, Codex, and other MCP-compatible clients. For more, check out: Connect your AI assistant to Rydoo.

Where to go next