Kuali Connector: Guides: other clients

OPENAI CODEX CLI

Codex CLI

kuali mcp setup --profile myschool --client codex

writes ~/.codex/config.toml — existing entries preserved

GOOGLE GEMINI CLI

Gemini CLI

kuali mcp setup --profile myschool --client gemini-cli

writes ~/.gemini/settings.json

GITHUB COPILOT CLI

Copilot CLI

kuali mcp setup --profile myschool --client copilot-cli

writes ~/.copilot/mcp-config.json

VS CODE

VS Code with Copilot Chat

kuali mcp setup --profile myschool --client vscode

writes .vscode/mcp.json in the current directory

This one is project-local rather than user-global, so you can scope the Connector to the repo you're working in. Open VS Code in that folder and Copilot Chat will pick it up.

MANUAL CONFIG

Any other local-MCP client

For a client without a built-in helper that does support launching a local stdio MCP server, add an entry like this to the client's server list:

"mcpServers": {

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

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

Flag

What it does

--profile <name>

Which configured profile to use.

--tools read-only

--insecure

Skip TLS verification. Local/dev instances only.

--timeout <seconds>

Per-command timeout. Default 30.

Don't pass credentials as env vars in the MCP config

Setting KUALI_API_KEY in the server's environment overrides profile resolution entirely. Store keys with kuali setup instead — the Connector looks them up at start.

VERIFY