v0 + SpendixAI
v0 can use custom MCP servers while it generates, and its documentation lists OAuth as one of four sign-in types. Setup details for the OAuth form were only partly documented, so treat this page as a starting point.
Connect in a few minutes.
In v0, SpendixAI would be added from the MCPs entry in the prompt form as a custom server with OAuth.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the MCP server URL.
Open the MCPs menu
In the v0 prompt form open the + menu and choose MCPs.
Configure a custom server
Choose a custom MCP server rather than a preset. Enter a name, paste the server address and set authentication to OAuth.
Connect and approve
Complete the authorisation. On the SpendixAI consent screen sign in, choose your workspace and pick a permission preset, starting with Read only.
https://spendix-api.kriva.studio/mcpv0’s other sign-in types are No Auth, Custom Headers and Bearer Token. SpendixAI uses OAuth with no key to paste.
What you need
- A v0 account that can add custom MCP servers
- A SpendixAI workspace
- The server address from Developer → MCP connections
Good to know
- The exact field labels in v0’s OAuth form were not confirmed. v0’s API reference for OAuth servers asks for an authorization address, a token address and a client ID, so the form may need more than a server address. We could not confirm that v0 registers itself automatically with SpendixAI.
- The documentation did not state the transport type or which plans include custom MCP servers.
- v0 has three permission modes. Ask confirms unmatched calls, Auto generally runs them, and Full skips approval. v0 says a potentially destructive operation is not guaranteed to need approval, so use Ask and keep SpendixAI on Read only.
- MCP tools are only used by v0 while it generates. The app it builds cannot call them.
Questions to start with.
These need only read access. Add records or upload statements once you have moved to a broader preset.
Start read only. Widen it later.
Ask about transactions, summaries and reports. Nothing can be added, changed or uploaded.
Ask questions, add expenses and upload statements or receipts.
Everything above, plus categorisation rules and insights. Billing and member settings stay in the console.
v0 and SpendixAI.
Will v0 connect to SpendixAI without extra details?
We could not confirm this. If the form asks for a client ID or endpoints that SpendixAI does not show, the connection may not work, and a different assistant from the MCP page may suit you better.
Can the app v0 builds read my expenses?
No. v0 says MCP tools are used only while it generates, and the generated app cannot call them.
Do I need to paste an API key?
No. The connection uses your SpendixAI sign-in and a consent screen, with dynamic client registration, so there is no secret to copy into a config file.
Can I keep the connection read only?
Yes. Read only is the recommended preset, and you can grant more access later or disconnect the assistant at any time from Developer → MCP connections.
Setup steps were checked against Vercel’s own documentation in November 2026. Menus and commands change, so if a step does not match what you see, follow the vendor’s current guide.
Bring v0 into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.