jolvAPI
jolv.app Open Jolv

AI agents (MCP)

Connect Jolv to Claude, ChatGPT, Gemini Enterprise, Microsoft 365 Copilot, Cursor or VS Code through the Model Context Protocol. Read-only, under each user's own permissions.

Jolv exposes its data to AI assistants through the Model Context Protocol (MCP), a read-only server at:

Endpoint
https://jolv-mcp.vercel.app/mcp

It is the same code as the REST API: one tool per endpoint, same parameters, same response, same authorisation under the user's own Jolv account. An assistant cannot see more than the person who connected it, and it cannot write anything.

Agent setup prompt
Paste this in any MCP-capable assistant to have it connect itself and explain what it can read.
Setup prompt
Connect to the Jolv MCP server at https://jolv-mcp.vercel.app/mcp (streamable HTTP).
Authentication is OAuth 2.1 with dynamic client registration: open the authorisation
page it returns, sign in with your Jolv account and click Authorise. The server is
read-only and scoped to my own Jolv permissions. Once connected, list the available
tools, then call get_fund_synthesis to show the published NAV of the funds I can see,
and tell me which other reads (valuation sheets, waterfalls, audit threads, portfolio,
cap tables, deal flow) you can use.

#Supported clients

Any client that supports remote MCP over streamable HTTP with OAuth 2.1 and dynamic client registration can connect. Jolv's consent page only returns the authorisation code to the clients below; another client is refused at the consent step and no data is shared.

ClientHow to add JolvReturn address accepted
Claude (web, desktop, mobile, Claude Code)Settings → Connectors → Add custom connector → URL aboveclaude.ai, claude.com, local loopback
ChatGPT (Business, Enterprise, Edu; developer mode)Settings → Connectors → Create → MCP server URL above, OAuthchatgpt.com
Gemini EnterpriseAdmin → Tools → Add MCP tool → URL above, OAuthvertexaisearch.cloud.google.com
Microsoft 365 Copilot (Copilot Studio)Agent → Tools → Add tool → Model Context Protocol → URL above, OAuth 2.0global.consent.azure-apim.net, token.botframework.com
CursorSettings → MCP → Add server → type streamable-http, URL abovecursor.com, cursor: scheme, local loopback
VS Code (Copilot agent mode)Command palette → MCP: Add Server → HTTP → URL abovevscode.dev, vscode: scheme, local loopback

#Step by step with Claude

  1. Add the connector

    In Claude, open Settings → Connectors, choose Add custom connector, name it Jolv and paste the endpoint above. Leave the OAuth fields empty: Claude discovers them.

  2. Authorise

    Claude opens the Jolv consent page. Sign in (MFA included if enabled on your account), check which application asks for access, and click Authorise.

  3. Ask

    For example: "What is the published NAV of Buyout I and how did the fair value of each holding move since the previous campaign?"

A guided version with screenshots is available on the Jolv website: Connect Claude to Jolv.

#What the assistant can read

The tool names are the endpoint names of the API reference: get_fund_synthesis, get_valuation_fiche, get_waterfall, get_audit_thread, list_portfolio, get_cap_table, list_pipeline… Tool descriptions are in French, the working language of most Jolv teams; this documentation is the English reference for the same reads.

The connector answers from persisted values only. It never estimates, never writes, and tells you when a fund has no published NAV.

#Revoking an assistant

Remove the connector on the client side, or revoke the authorisation in the Jolv authorisation server (Supabase Auth → OAuth Apps). An access token already issued expires within one hour.