Run your fundraise on AI, from your own assistant.
Connect Oka to Claude, ChatGPT, or any MCP client and work the full loop from a chat: your matches, your warm paths, your pipeline — including updates and drafted outreach. Answered from your workspace, not the open web.
“Which funds fit my seed round?” — answered from your live ranked shortlist, not the open web.
“Who can introduce me to this fund?” — pulled straight from your mapped network.
“What's stuck this week?” — a live summary of your raise, without opening the app.
“Move Meridian to committed at €500k.” — your assistant asks before every change runs.
“Draft an intro ask for Northlake.” — a ready draft, in your tone. Oka never sends it; you do.
One address. That’s the whole setup.
Oka is a standard remote MCP server (Streamable HTTP + OAuth). Paste this address into your assistant, sign in with your Oka account, and you’re connected.
https://getoka.ai/api/mcpAbout a minute, in any client.
Add the URL, sign in, done. No API keys, nothing to install.
- 01Open Settings → Connectors → Add custom connector.
- 02Paste https://getoka.ai/api/mcp as the remote MCP server URL and confirm.
- 03Sign in with your Oka account when prompted, and approve the connection. Enable the connector in a chat via the + menu.
- 01In Settings → Apps, enable Developer mode (paid plans; workspace admins may need to allow it).
- 02Create a new app/connector and paste https://getoka.ai/api/mcp as the MCP server URL.
- 03Choose OAuth as authentication and sign in with your Oka account when prompted.
- 01Open Cursor Settings → MCP, or edit ~/.cursor/mcp.json.
- 02Add a server entry with "url": "https://getoka.ai/api/mcp".
- 03Cursor opens the OAuth sign-in in your browser — approve with your Oka account.
- 01Run: claude mcp add --transport http oka https://getoka.ai/api/mcp
- 02In a session, run /mcp to authenticate.
- 03Sign in with your Oka account — done.
Using something else? Any client that supports remote MCP servers (Streamable HTTP + OAuth) works the same way — add https://getoka.ai/api/mcp wherever your client manages MCP servers or custom connectors, then sign in.
Your workspace, your rules — here too.
The connection uses OAuth — you sign in at Oka and approve. Nothing to paste except the URL.
Scoped to your account and workspace. It never sees another workspace and never returns investor email addresses.
Pipeline updates run only after your assistant asks you. Outreach is drafted as text — Oka has no way to send it.
More on how we handle your data on the trust page.
Same workspace, every assistant.
Oka speaks the open MCP standard, so it isn’t tied to one AI. Clients that support remote MCP today:
…and any other client that supports remote MCP servers. More are adding support continuously.
If something doesn’t connect.
- The connector doesn't appear after adding it
- Check the exact URL (https, no trailing slash) and that your plan allows custom connectors — ChatGPT needs Developer mode on a paid plan.
- I'm stuck in a sign-in loop
- Remove the connector and add it again, completing the sign-in in one go. If your browser blocks popups or third-party cookies, allow them for getoka.ai.
- Connected, but the tools don't load or calls fail
- Your session may have expired — remove and re-add the connector. If one action is declined, your role may not allow it (pipeline changes and drafting need editor access).
- How do I disconnect?
- Remove the connector in your client's settings — that ends its access immediately.
Run your raise from your AI assistant.
Start free. No credit card required. Bring your team.