konnektor

One door between AI and your company's tools.

konnektor sits between AI clients like Claude and the systems your company runs on. People sign in once with their work account, every tool call is checked against your policy, and every decision is logged.

Talk to us See how a call travels
konnektor between AI clients and tools Three AI clients on the left connect to konnektor in the middle, which connects to Google Workspace, Linear, Grafana and your own MCP servers on the right. A call from Claude Code to Linear is allowed through. A call from another client is denied by policy at konnektor. Claude chat and desktop Claude Code in the terminal Other MCP client anything with OAuth konnektor checks every call Google Workspace Gmail, Calendar, Drive Linear issues and projects Grafana metrics and logs Your MCP servers in-house or vendor allowed denied by policy

AI assistants are already wired into work. Mostly by hand.

  • Connectors nobody approvedPeople add MCP servers and API keys to their AI clients on their own. IT can't see which ones, or what they reach.
  • A separate sign-in for every toolEach connector has its own login and its own idea of who you are. Leaving the company doesn't sign you out of them.
  • No record of what happenedWhen an assistant reads a mailbox or changes a ticket, there's rarely a log of who asked for it.

How a call travels

  1. Add one address to your AI clientYour organisation gets its own konnektor address, like floka.konnektor.no. Any client that supports MCP with OAuth connects to it like a single server.
  2. Sign in with your work accountkonnektor signs people in through your existing identity provider, such as Google Workspace, and knows which groups they're in.
  3. Connect your own accounts onceFor tools that act as you, like Gmail or Linear, each person connects their own account. konnektor stores the tokens encrypted and refreshes them.
  4. Every call is checked and loggedPolicies decide who can use which tools, down to a single tool. Each decision is logged: who called, which tool, from which client, and whether it was allowed.

What it connects to today

  • Google Workspace Available
  • Linear Available
  • Grafana Available
  • Doffin, public procurement Available
  • SSB, Statistics Norway Available
  • Your own MCP servers Available
  • Fiken Planned
  • Microsoft 365 Planned

Any remote MCP server can sit behind konnektor. Servers that register clients automatically, like Linear's, need no setup at the vendor. konnektor works with Claude, Claude Code and other MCP clients that support OAuth.

Where your data goes

Hosted in the EU
konnektor runs on Google Cloud in europe-north1 (Finland). It can also be installed in your own Kubernetes cluster.
Tokens stay encrypted
Each person's tool tokens are encrypted with a key kept apart from the database. The token your AI client holds is never passed on to the tools.
Closed by default
Nothing is reachable until a policy allows it, and a deny rule always wins over an allow.
A log of every decision
Who called which tool, from which client, and what the policy decided.
People stay in control
Everyone can see and disconnect their accounts at any time. Removing a user removes their tokens too.

Want konnektor for your organisation?

konnektor is built by Floka. We're setting up the first organisations now. Tell us which tools your people use, and we'll show you how it fits.

Email hei@floka.no