Kuali Connector: Guides: Claude Desktop

SET IT UP

One command, then restart

With a profile already configured (see First connection):

kuali mcp setup --profile myschool

That reads your saved URL and keychain-stored API key, finds the Claude Desktop config file for your operating system, and merges in a kuali MCP server entry. Existing servers in the config are preserved.

Fully quit, then reopen

On macOS, "quit" means Cmd+Q — closing the window isn't enough.

VERIFY

Check the wiring

kuali mcp verify

✓ config file ✓ kuali entry ✓ binary ✓ API key ✓ runnable

Inside Claude, a slider icon in the composer shows that tools are available. Click it to see the list of kuali_* tools.

ASK IT SOMETHING

Confirm the tools are reachable

“Use the Kuali tools to list the first five apps.”

“Which products does this Kuali instance have configured?”

The first time Claude uses a tool in a conversation, it may ask you to approve the call. You can approve per-call or allow all calls from the Connector for that session.

MULTIPLE PROFILES

Sandbox and production, side by side

Claude Desktop's config has one kuali entry at a time. Either rerun mcp setup when you switch, or register each profile as its own MCP server by editing the config directly:

"mcpServers": {

"kuali-sandbox": { "command": "/usr/local/bin/kuali",

"args": ["mcp", "--profile", "sandbox"] },

"kuali-prod": { "command": "/usr/local/bin/kuali",

"args": ["mcp", "--profile", "prod"] } }

Now each profile shows up as its own tool namespace — tell Claude "use the kuali-sandbox tools" to scope the conversation.

Config file location

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

%APPDATA%\Claude\claude_desktop_config.json

KEEP PRODUCTION SAFE

Read-only for anything sensitive

kuali mcp setup --profile prod --tools read-only

Only read tools (list, get, status, export, summary) are registered. Write tools (create, update, submit, approve, delete) are hidden from Claude entirely.

TROUBLESHOOTING