Kademi can connect to AI assistants such as Claude Code, Claude Desktop, and Claude on the web so they can use your Kademi tools on your behalf: looking up profiles, working support tickets, and more. This uses the Model Context Protocol (MCP).

There are two connections you can make:

You sign in with your normal Kademi login, and the assistant can only see and use the tools your Kademi roles allow.

Before you start (administrator setup)

An account administrator needs to do the following once.

1. Enable the required apps

Install and enable both apps for the connection(s) you want to offer:

2. Turn on client registration

In KOAuth2, turn on Allow Dynamic Client Registrations. This lets an assistant connect for the first time. KOAuth2 has separate settings for Admin and Website, so turn it on for the connection you're offering:

• Admin MCP: enable it in the Admin KOAuth2 settings.
• Website MCP: enable it in the Website KOAuth2 settings.

3. Give users the right roles

What a user can do through the assistant is controlled entirely by their Kademi roles. See Access and roles below.

Access and roles

• A user with the Administrator role has full access; nothing else is needed.
• Otherwise, a user needs the base role(s) for the connection, plus a role for each tool they want to use.

Base roles

Tool roles (examples)

Each tool requires its own role. Grant the ones the user needs:

Example: a support agent (not an administrator) who wants to work tickets through Admin MCP needs AdminViewer + KMCPAdminUser (to connect) plus ksupportUser (for the support tools).

If a user is missing the base roles they won't be able to connect. If they're missing a specific tool's role, that tool simply won't appear.

Connect your assistant

Find your address

https://<your-admin-address>/mcp/kmcp      →  Admin MCP
https://<your-website-address>/mcp/kmcp    →  Website MCP

Use the same address you use to log in to Kademi. It's different for each account.

Example (Admin MCP):

https://kademi.admin.kademi.us/mcp/kmcp

The first time you connect, a browser window opens for you to sign in to Kademi and approve access. After that it reconnects automatically.

Claude Code

claude mcp add --transport http kademi https://<your-admin-address>/mcp/kmcp

• kademi is just a name for the connection; choose whatever you like.
• Replace the address with your account's admin or website address.
• Run /mcp in Claude Code to sign in and confirm the tools loaded.

Claude Desktop

Open Settings → Connectors → Add custom connector, paste your https://…/mcp/kmcp address, and follow the sign-in prompt.

Claude on the web (claude.ai)

Open Settings → Connectors → Add custom connector, paste your https://…/mcp/kmcp address, and follow the sign-in prompt.

On a Team or Enterprise plan? Custom connectors are controlled by your Claude workspace. If Add custom connector is missing or greyed out, a workspace Owner/Primary Owner needs to either add the Kademi connector at the organisation level (so it appears for everyone) or turn on the setting that lets members add their own. This is a Claude-side permission, separate from the Kademi administrator setup above: you can have all the right Kademi roles and still need your Claude admin to enable the connector first.

Other assistants

Any assistant that supports remote MCP connections can use the same https://…/mcp/kmcp address and Kademi sign-in.

Code Mode (optional)

By default the assistant calls each Kademi tool separately, one at a time: call a tool, wait for the result, read it, then call the next. Code Mode instead gives it two meta-tools (search and execute) and lets it write a short script that does the whole job in a single step.

Why use it

• Chain steps without round-trips. The result of one tool feeds straight into the next inside one script. For example, find a profile, award it points, add a note runs as one call instead of three separate exchanges.
• Bulk actions in one shot. Loop over many records in a single call: award points to all 1,000 members of a group, tag a whole list of leads, or update a batch of products, rather than one tool call per record.
• Faster and cheaper. One request replaces dozens, so there's far less back-and-forth, which means quicker results and fewer tokens used.
• Only the data you need comes back. The script can filter, sort, and total the results before returning, so you get the answer (e.g. "the 12 members over their quota") rather than a raw dump the assistant then has to sift through.
• Scales to large tool sets. search looks up tool specs on demand instead of loading every tool's details up front, which keeps things responsive when an account exposes a lot of tools.

In short: normal mode is one tool at a time; Code Mode lets the assistant express a whole multi-step or bulk operation as a single action.

Turn it on

Add ?codemode=true to your MCP address. Nothing else changes:

https://<your-admin-address>/mcp/kmcp?codemode=true      →  Admin MCP, Code Mode
https://<your-website-address>/mcp/kmcp?codemode=true       →  Website MCP, Code Mode

Connect exactly as above (claude mcp add …, or paste it as a custom connector). Instead of the full tool list you'll see just search and execute.

What it can do, and can't

• Same roles, same limits. A script can only call the tools your Kademi roles already allow; Code Mode grants no extra access. If you can't use a tool in the normal connection, you can't use it here either.
• Sandboxed. Scripts run in a locked-down sandbox with no access to the server, the filesystem, the network, or other accounts, and with CPU and memory limits, so a long-running or oversized script is stopped automatically.
• Nothing extra to enable. As long as KMCP is enabled for the connection, Code Mode works. It's just the address flag.

Just describe what you want in plain language. The assistant uses search to find the right Kademi tools, then execute to run them. You don't write any code yourself.

Troubleshooting