Connecting AI assistants to Kademi (MCP)
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:
| Connection | What it gives the assistant | Where it connects |
|---|---|---|
| Admin MCP | Admin / back-office tools (profiles, support, reporting, …) | your admin address |
| Website MCP | Website / member-facing tools | your website address |
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:
| App | For Admin MCP | For Website MCP |
|---|---|---|
| KMCP | Enable in Admin | Enable in Admin and Website |
| KOAuth2 | Enable in Admin | Enable in Admin and Website |
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
| Connection | Roles the user needs |
|---|---|
| Admin MCP | AdminViewer and KMCPAdminUser |
| Website MCP | KMCPWebsiteUser |
Tool roles (examples)
Each tool requires its own role. Grant the ones the user needs:
| To use… | Give the user the role |
|---|---|
| Auction tools | AuctionViewer |
| Support tools (create / find tickets) | ksupportUser or ksupportAdmin |
| Support admin tools (e.g. leads needing action) | ksupportAdmin |
| Agent timer / workflow tools | Content Viewer |
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://kademi.admin.kademi.us/mcp/kmcp
kademiis just a name for the connection — choose whatever you like.- Replace the address with your account's admin or website address.
- Run
/mcpin 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.
Other assistants
Any assistant that supports remote MCP connections can use the same https://…/mcp/kmcp address and Kademi sign-in.
Troubleshooting
| Problem | What to check |
|---|---|
| The assistant can't connect / says client registration is disabled | Ask your administrator to turn on Allow Dynamic Client Registrations in KOAuth2 for that connection (Admin vs Website). |
| Connected, but no tools appear | You're missing a base role (AdminViewer + KMCPAdminUser for Admin, KMCPWebsiteUser for Website), or KMCP isn't enabled for that area. |
| A specific tool is missing | You don't have that tool's role (see Access and roles). |
| The address won't load | Double-check your admin/website address, and that KMCP is enabled there. |