Connect riven to AI clients with MCP

We’ve added a remote Model Context Protocol (MCP) server for riven.

That means AI clients can now connect to your riven account over OAuth and work with your invoicing and wallet data directly.

MCP endpoint

https://beta.mcp.riven.cash/mcp

Use HTTP transport and leave headers empty if your client supports OAuth-based MCP connections.

What clients can do

Once connected, AI tools can read and work with:

• your business profile
• clients
• invoices
• wallet balances
• transaction history

They can also take actions like:

• create a client
• create an invoice
• update a draft invoice
• send an invoice
• cancel a sent/viewed/overdue invoice

Built for real account access

This is not a static export or a demo integration.

The MCP server is connected to your real riven account through OAuth, with scoped access and user-level authorization.

That means your AI client can:

• find invoices for a specific client
• filter invoices by status, currency, due date, issue date, created date, or paid date
• paginate through invoice and client lists with cursors
• fetch balances and recent transactions
• edit draft invoices before they are sent
• cancel already-sent invoices and notify the client

Better invoice tooling for AI

We specifically improved the invoice tooling so it works more naturally with assistant workflows.

Instead of forcing the model to fetch everything and infer the rest, the MCP tools now support:

• clientId
• clientName
• status
• currency
• unpaidOnly
• dueBefore / dueAfter
• createdBefore / createdAfter
• issuedBefore / issuedAfter
• paidBefore / paidAfter
• sorting
• cursor-based pagination

There is also a dedicated tool for listing invoices for a single client.

Drafts, sends, and cancellations

The invoice lifecycle is now straightforward:

• Create → invoice starts as draft
• Update → draft invoices can be edited
• Send → invoice becomes sent
• Cancel → sent, viewed, or overdue invoices can be cancelled

When an invoice is cancelled, the client gets a cancellation email.

We also updated the generated PDF to include a diagonal cancelled watermark, and that cancelled PDF is attached to the cancellation email.

Why this matters

riven already gives you private invoices, bank rails, and onchain settlement.

MCP makes that data usable from the tools people are increasingly working inside every day:

• coding agents
• AI workspaces
• assistant-powered back offices
• finance copilots

Instead of copying data between apps, your AI client can work directly against your live riven account.

How to connect

For a client that supports remote MCP over HTTP:

• Name: riven
• URL: https://beta.mcp.riven.cash/mcp
• Transport: HTTP
• Headers: leave empty

Then authenticate through the OAuth flow.

What’s next

This is the first version of the riven MCP surface.

We’ll keep expanding it where it actually improves workflows — especially around invoices, payments, and account operations.

If you’re building with AI and want your finance stack to be usable by agents, this is the foundation.

Add this as an MCP server to your AI client:

https://beta.mcp.riven.cash/mcp