Documentation Index
Fetch the complete documentation index at: https://mintlify.com/groniz/groniz-cli/llms.txt
Use this file to discover all available pages before exploring further.
The Groniz agent skill installs the same way across all supported agents — one command, no manual configuration. The differences between agents come down to where the skill file is placed and whether the agent also supports the Groniz MCP server as an alternative transport. This page covers every agent other than Claude Code, which has its own setup guide.
Install command
To let the skills CLI detect your agent automatically:
npx skills add groniz/groniz-cli
npx skills add groniz/groniz-cli -a opencode -a cline
Codex
Cline
Cursor
opencode
ChatGPT
Skill install
npx skills add groniz/groniz-cli
.agents/skills/ in your project directory. Codex reads this directory automatically.MCP setup
Codex supports MCP via ~/.codex/config.toml. Add the Groniz server by editing that file directly:[[mcp_servers]]
name = "groniz"
url = "https://mcp.groniz.com/mcp"
[mcp_servers.headers]
Authorization = "Bearer YOUR_API_KEY"
YOUR_API_KEY with your Groniz API key. Codex will pass the Authorization header on every MCP request.The GRONIZ_API_KEY environment variable must be set before Codex launches. Codex reads environment variables at startup and will not pick up changes made after it is running. Add the export to your shell profile (~/.zshrc, ~/.bashrc, etc.) so it is always present when you open a new terminal.
Authentication
Set your API key in your shell profile so it is available before Codex starts:export GRONIZ_API_KEY=your_api_key_here
~/.groniz/credentials.json is used automatically by the CLI regardless of the GRONIZ_API_KEY env var.Skill install
npx skills add groniz/groniz-cli
.agents/skills/ in your project directory. Cline reads this directory automatically — no additional configuration is required.MCP setup
Cline supports MCP via the streamable HTTP endpoint. In Cline’s MCP server settings, add a new server with:
- URL:
https://mcp.groniz.com/mcp
- Header:
Authorization: Bearer YOUR_API_KEY
Replace YOUR_API_KEY with your Groniz API key.Authentication
Run this once in your terminal:Alternatively, export your key in your shell profile:export GRONIZ_API_KEY=your_api_key_here
Skill install
npx skills add groniz/groniz-cli
.agents/skills/ in your project directory. Cursor reads this directory automatically — no further configuration is needed after install.Authentication
Run this once in your terminal:Or set your API key in your shell profile so Cursor’s terminal environment picks it up:export GRONIZ_API_KEY=your_api_key_here
Skill install
npx skills add groniz/groniz-cli
.claude/skills/ as well as .agents/skills/, so the skill is installed to .claude/skills/ for opencode. Both directories are supported — the skills CLI selects the correct one automatically.MCP setup
opencode supports MCP via opencode.json. Add the Groniz server to your opencode.json:{
"mcp": {
"groniz": {
"url": "https://mcp.groniz.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
YOUR_API_KEY with your Groniz API key. opencode will connect to the MCP server on startup.Authentication
Run this once in your terminal:Or set your API key in your shell profile:export GRONIZ_API_KEY=your_api_key_here
Skill install
npx skills add groniz/groniz-cli
.agents/skills/ in your project directory.ChatGPT agent skills are available on Business, Enterprise, and Edu plans only. They are not available on Free, Plus, or Pro plans. If you are on a plan that does not include skills, the skill file will be installed but ChatGPT will not read it.
MCP
ChatGPT cannot present a custom API key to a remote MCP server, so the Groniz MCP endpoint is not available for ChatGPT. The skill-based integration is the only supported method.Authentication
Set your API key in the sandbox environment where ChatGPT executes commands:export GRONIZ_API_KEY=your_api_key_here
groniz auth login inside the sandbox terminal to store credentials in ~/.groniz/credentials.json.
Common to all agents
Regardless of which agent you use, two things must be in place before the agent can post:
1. The Groniz CLI binary
The skill teaches the agent how to use the CLI, but the binary itself must be installed separately. If you have not already done this:
curl -fsSL https://groniz.com/install.sh | sh
groniz update.
2. Valid credentials
Every Groniz command requires authentication. Run this once:
Or set the environment variable in your shell profile:
export GRONIZ_API_KEY=your_api_key_here
~/.groniz/credentials.json persists across shell sessions and agent restarts, unlike an export that only lasts for the current session.
If your agent is not listed above, check whether it reads .claude/skills/ or .agents/skills/. If it supports either directory, install the skill manually by copying SKILL.md from github.com/groniz/groniz-cli into the appropriate folder. The file is plain Markdown and requires no modification. 