NewYour AI employee is one email away →
Click to zoom
  • Sign in instead of copying a key. Connect Claude to Viktor over MCP using your Viktor account and choose the workspace Claude should work in.
  • Discover before connecting. MCP clients can see the available tools before sign-in. Running those tools still requires authentication.
  • A clearer consent screen. See that you are connecting Claude and which site the sign-in flow will return you to.

What's new

Claude can now connect to Viktor with OAuth. Instead of creating an API key and pasting it into another app, you sign in to Viktor, choose a workspace and approve the connection.

That gives Claude a way to hand work to Viktor through MCP, the protocol AI apps use to call each other's tools. You can keep the conversation in Claude while Viktor takes on a task and makes its results available there.

Tool discovery also works before sign-in. A compatible client can find out what Viktor offers before asking you to connect, but it cannot run those tools without authentication.

How to use it

In Claude's connector settings, add a custom connector with https://api.viktor.com/mcp. Choose Connect, sign in to Viktor and pick the workspace you want to use. Review the permissions and select Allow.

Using Claude Code? Add Viktor as a remote HTTP MCP server, then complete the browser sign-in from Claude Code's MCP menu.

Where it works

Claude clients with remote HTTP MCP and OAuth support, including Claude on the web, Claude Desktop and Claude Code. This adds a sign-in option to Viktor's existing MCP server; it does not require moving your chats.

Get Started for Free