Connect Claude

Add Kokar to Claude as a custom connector, so you can manage your workspace from a conversation.

Before you start

  • A Kokar workspace on a paid plan. MCP connections are not available on Free.
  • Membership of that workspace. You will sign in to Kokar during the setup.

Any Claude plan works, including the free one.

Add the connector

Open Claude's settings

In a browser at claude.ai or in the desktop app, click your name at the bottom of the sidebar and choose Settings.

Go to Connectors

In the settings sidebar, select Connectors.

Add a custom connector

Click Add in the top right and choose Custom connector. The Add custom connector dialog opens.

Fill in the two fields

FieldValue
NameKokar
Remote MCP server URLhttps://mcp.kokar.krd/mcp

Claude checks the server and fills in the rest. Keep what it detects:

SettingKeep
AuthenticationAlways required — every Kokar capability needs you signed in.
OAuth clientUse Anthropic's hosted client metadata (recommended). Nothing to enter; Kokar supports it. "Register one automatically" also works.
Additional request headersNone.

Never enter a client ID or secret — Kokar does not use them.

Click Add.

Approve the connection in Kokar

Claude opens Kokar in your browser. Sign in if you are asked, then you will see an approval screen naming the app and what it is requesting.

Pick your default workspace — the one Claude works in when you do not name another — then click Allow access. The connection reaches every workspace you belong to; this is only the starting point.

Start using it

You are returned to Claude, connected. Turn the Kokar connector on in a chat and ask for something:

  • "List my projects in Kokar"
  • "What tasks are overdue?"
  • "Create a task 'Draft the Q3 proposal' in Client Onboarding, due 15 July"
  • "Mark the onboarding checklist task as Done"

More than one workspace? One connector is enough

The connection covers every workspace you belong to, and Claude will not let you add the same URL twice anyway. Ask "list my Kokar workspaces" to see them; say "in Acme, …" to work in one without switching; say "switch my default Kokar workspace to Acme" to change the default for good. The default is also shown under Settings → Connected apps.

What Claude can do once connected

Claude acts as you — it has exactly the permissions you have, and no others.

See Capabilities for everything it can do and the permission each one needs.

Narrowing what Claude may use

Kokar decides what Claude is allowed to do; Claude decides what it actually reaches for. You can tighten the second half from Claude's side.

In Settings → Connectors, click Kokar. You get the list of every capability the connection exposes, and for each one you can:

  • turn it off, so Claude never uses it at all, or
  • have Claude ask you first, so nothing happens without your say-so, or
  • let it run without asking, for the ones you use constantly.

This does not change your Kokar permissions

Turning a capability off here only stops Claude from using it. It does not change what you can do in Kokar, and it does not affect any other AI app you have connected.

Disconnecting

In Kokar, open Settings → Connected apps, find the connection and revoke it. Access stops immediately — the next request Claude makes is refused, and reconnecting means going through the approval screen again.

Kokar is the side that decides, so revoke there. Deleting the connector in Claude removes it from your Claude settings, but whether that also tells Kokar to drop the grant is up to Claude.

If something goes wrong

What you seeWhat to do
Claude reports it can't reach the serverConfirm the URL is exactly https://mcp.kokar.krd/mcp, including /mcp at the end.
The approval screen says your plan doesn't include MCPThe workspace you picked as default is on Free. Pick another, or move it to Standard or above under Settings → Billing, then connect again.
Claude says a workspace's plan doesn't include MCPThat one workspace is on Free; your other workspaces keep working. Upgrade it under its Settings → Billing.
Claude says it can't find a workspaceAsk it to list my Kokar workspaces and use one of those names. It only sees workspaces you are a member of.
The approval screen sends you to login and back in a loopSign in to Kokar first in the same browser, then add the connector again.
Claude connects but looks at the wrong workspaceIt is using the default. Name the workspace you mean in the request, or ask it to switch the default — no need to reconnect.
Claude says it doesn't have permission for somethingIt has your permissions, not more. If you cannot do it in the app, Claude cannot do it either.

Frequently asked questions

Do I need a paid Claude plan?

No. Adding a custom connector by URL works on any Claude plan, including the free one. It is the pre-built connectors in Claude's directory that require Pro, Max, Team or Enterprise. What you do need is a paid Kokar plan — MCP is not available on Kokar Free.

What should I pick under Authentication and OAuth client?

Keep what Claude detects — "Always required" and "Use Anthropic's hosted client metadata". Kokar supports both, and you never need to enter a client ID or secret.

Which workspace does Claude get access to?

All the workspaces you belong to, with the one you pick on the approval screen as the default. Name another workspace in your request to work there, or ask Claude to switch the default. You cannot add Kokar twice in Claude, and you do not need to.

Can Claude see private spaces I am not a member of?

No. Claude acts as you, so it has exactly the permissions you have. A private space you are not a member of stays invisible to it.

Can I stop Claude using only some of the capabilities?

Yes. In Claude, open Settings → Connectors and click Kokar. Each capability can be turned off, set to ask you before it runs, or allowed to run without asking.

How do I disconnect Claude?

In Kokar, open Settings → Connected apps and revoke it. Access stops immediately. Revoke it there rather than only deleting the connector in Claude, since Kokar is the side that decides.

Keep reading