Connect

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.

Ask about your matches

“Which funds fit my seed round?” — answered from your live ranked shortlist, not the open web.

Find warm paths

“Who can introduce me to this fund?” — pulled straight from your mapped network.

Check your pipeline

“What's stuck this week?” — a live summary of your raise, without opening the app.

Update your pipeline

“Move Meridian to committed at €500k.” — your assistant asks before every change runs.

Draft outreach in your voice

“Draft an intro ask for Northlake.” — a ready draft, in your tone. Oka never sends it; you do.

Server URL

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. It only ever sees what your account is allowed to see.

https://getoka.ai/api/mcp
Setup

About a minute, in any client.

Every client follows the same pattern: add the server URL, sign in with Oka, done. No API keys, nothing to install.

Claude
  1. 01Open Settings → Connectors → Add custom connector.
  2. 02Paste https://getoka.ai/api/mcp as the remote MCP server URL and confirm.
  3. 03Sign in with your Oka account when prompted, and approve the connection. Enable the connector in a chat via the + menu.
ChatGPT (OpenAI)
  1. 01In Settings → Apps, enable Developer mode (paid plans; workspace admins may need to allow it).
  2. 02Create a new app/connector and paste https://getoka.ai/api/mcp as the MCP server URL.
  3. 03Choose OAuth as authentication and sign in with your Oka account when prompted.
Cursor
  1. 01Open Cursor Settings → MCP, or edit ~/.cursor/mcp.json.
  2. 02Add a server entry with "url": "https://getoka.ai/api/mcp".
  3. 03Cursor opens the OAuth sign-in in your browser — approve with your Oka account.
Claude Code
  1. 01Run: claude mcp add --transport http oka https://getoka.ai/api/mcp
  2. 02In a session, run /mcp to authenticate.
  3. 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.

What it can access

Your workspace, your rules — here too.

You sign in — no API keys

The connection uses OAuth: your assistant redirects you to Oka, you sign in, you approve. Nothing to paste except the URL.

It sees what you see

The connector is scoped to your account and workspace. Your role and plan apply exactly as in the app — it can never see another workspace, and it never returns investor email addresses.

Changes are confirmed, sends don't exist

Pipeline updates run only after your assistant asks you. Outreach is drafted as text — Oka has no way to send it. Disconnect anytime from your client's settings.

More on how we handle your data on the trust page.

Works with

Same workspace, every assistant.

Oka speaks the open MCP standard, so it isn’t tied to one AI — any assistant can work your raise, grounded in the network your Gmail, LinkedIn, and calendar feed into Oka. These clients support remote MCP connections today:

Claude
Claude Code
ChatGPT (OpenAI)
Codex (OpenAI)
Cursor
VS Code
Perplexity
Windsurf

…and any other client that supports remote MCP servers. More are adding support continuously.

Troubleshooting

If something doesn’t connect.

The connector doesn't appear after adding it
Make sure you used the exact URL https://getoka.ai/api/mcp (https, no trailing slash) and that your plan supports custom connectors — in ChatGPT, custom MCP apps require Developer mode on a paid plan. Then reload the client and check its connector/MCP list again.
I'm stuck in a sign-in loop
Disconnect (remove) the Oka connector in your client, then add it again and complete the sign-in in one go. If your browser blocks third-party cookies or popups for the sign-in window, allow them for getoka.ai and retry.
Connected, but the tools don't load or calls fail
Your session may have expired — remove and re-add the connector to sign in fresh. If a specific action is declined, your workspace 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. You can reconnect the same way you set it up.

Run your raise from your AI assistant.

Start free. No credit card required. Bring your team.

Start free · No credit card required