What the Connector is, what it costs, where your data goes, and which clients and platforms work.
A small program that runs on your computer and gives your AI assistant — or your terminal — a structured, secure way to talk to your Kuali instance. It's a local MCP server; the same binary also works as a full kuali command-line tool.
No. You install the Connector, run one setup command per AI client, and then talk to Kuali in plain English from the chat you already use. The CLI is available if you want it, but never required.
Yes — free for any institution with an active Kuali subscription. You will, however, be using tokens against whichever AI client you've set up; that billing is between you and the AI vendor.
Only what the AI client normally sends. The assistant calls the Connector's tools locally, the Connector calls your Kuali instance directly, and tool responses go to the assistant's model for reasoning. Your API key never leaves your machine, and nothing routes through a Kuali-operated proxy.
Yes — set the profile up with --tools read-only. Write tools are hidden entirely. For belt-and-braces protection, issue an API key that itself has read-only permissions in Kuali.
No. The Connector authenticates with a Kuali API key — a signed token you create under Settings → API Keys, inheriting that user's permissions, revocable at any time.
Any client that supports local MCP servers (stdio): Claude Desktop, Claude Code, OpenAI Codex CLI, Google Gemini CLI, GitHub Copilot CLI, and VS Code with Copilot Chat. Others can be added with a manual config entry.
Not yet. ChatGPT only supports hosted MCP servers at public HTTPS URLs; the Connector is a local server on your machine. Use OpenAI Codex CLI to drive Kuali from an OpenAI model today — a hosted offering is on the roadmap, no date yet. Claude.ai (web) is in the same boat; use Claude Desktop or Claude Code.
No. The Connector targets the Kuali Platform (*.kualihub.com, *.kualibuild.com, and regional variants). Any *.kuali.co sign-in address is Classic, and the Connector won't connect to it.
macOS 12+ (Intel and Apple Silicon), Windows 10+ (amd64 and arm64), and any modern 64-bit Linux. Binaries are statically linked — no runtime dependencies.
No — give each its own profile and pick per command or per MCP server entry. A common pattern is sandbox full-access, production read-only.
Yes. Every capability is a plain kuali command with JSON output, per-profile env vars for credentials, and --dry-run for safety.
On request: kuali update check tells you if a newer version is out; kuali update install replaces the binary in place.
File an issue — we'd rather add an answer than have you guessing.
Ask on GitHub ->
Ready-to-use prompts for curriculum, research, build apps, imports, workflow analysis, and reporting.
Browse prompts →
Tips for Claude Desktop, Claude Code, Codex, Gemini, Copilot, and VS Code.
AI assistants →
Skip the chat — every capability is also a plain kuali command, ready for scripts and CI.
Command reference →
