Start with the two diagnostics, check the troubleshooting runbook, and know where to file bugs, ask questions, or report security issues.
$
kuali doctor # config, URL, auth, API reachability
$
kuali mcp verify # MCP client config, binary path, permissions
Pass --profile <name> to scope to a specific profile, or --client <name> to inspect an AI client's MCP configuration. The troubleshooting guide has a runbook for the usual failure modes.
Not yet — and the reason is a transport mismatch, not a Kuali policy. ChatGPT (chatgpt.com, the ChatGPT desktop app) only supports hosted MCP servers: ones that live at an HTTPS URL on the public internet. The Kuali Connector is a local MCP server — it runs on your own machine and talks to the AI client over stdio, so your API keys and data stay on your computer. ChatGPT can't launch a local binary, and we don't offer a hosted endpoint today.
If you want to drive Kuali from an OpenAI model right now, use OpenAI Codex CLI — it's OpenAI's terminal product and supports local MCP servers. Setup is one command:
$
kuali mcp setup --profile myschool --client codex
The other local-MCP clients (Claude Desktop, Claude Code, Gemini CLI, Copilot CLI, VS Code + Copilot) also work. A hosted offering that would let ChatGPT and Claude.ai connect is on our roadmap but doesn't have a date — file an issue if you'd like to track it.
For questions about what data you should access, which apps you have permission for, or how your institution configures Kuali, your campus Kuali administrator is almost always the fastest path — they know your local setup. Ask your department contact or IT help desk if you're not sure who that is.
Open an issue in the kuali-connector repository.
Include with the issue:
• Output of kuali version
• Output of kuali doctor --profile <name> -o json (redact the masked key if it's still shown — it shouldn't be)
• For MCP issues: kuali mcp verify --client <claude-desktop|claude-code|…>
• OS and version
• The exact command you ran or the prompt you gave your AI assistant
• What you expected to happen and what actually happened
Email security@kuali.co for anything that might be a vulnerability. Please don't disclose publicly until we've had a chance to respond.
If you'd like to compare notes with other Kuali users, the Kuali Community forum (accessible via your institution's Kuali admin) is a good place for workflows, prompts, and automation recipes.
Last updated: September 21, 2026
ON THIS PAGE
Email security@kuali.co for anything that might be a vulnerability. Please don't disclose publicly until we've had a chance to respond.
security@kuali.co
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 →