Skip to main content
Use this page for assistants without a native Cekura plugin. The generic pattern is the same: install Cekura guidance, then connect MCP if your assistant supports it. Gemini CLI is an exception — it has a native extension, covered at the end.

Choose the right path

Install Cekura guidance

Try Agent Skills first:
If your assistant does not load Agent Skills, install the portable behavior preset wherever your assistant reads project rules or agent instructions:
For assistants with a dedicated rules directory, place the file there instead.

Connect MCP

If your assistant supports HTTP MCP, use:
If your assistant requires a local command shim, use mcp-remote:
For client-specific OAuth and API-key examples, see manual setup.

Verify setup

Ask your assistant:
If the assistant cannot list agents, MCP is not connected. If it lists agents but gives generic testing advice, add the behavior preset or confirm Agent Skills are enabled.

Gemini CLI

Gemini CLI has a native Cekura extension that includes the MCP server and the Cekura context file. (Gemini extensions don’t bundle Agent Skills yet, so this ships domain knowledge as context rather than SKILL.md skills.)
The --auto-update flag self-checks GitHub on each launch and applies new versions on the next restart — no manual updates. Omit it if you prefer to update manually. On first use of a Cekura MCP tool, Gemini runs an OAuth browser sign-in — no API key. The extension loads GEMINI.md (metric design, eval design, API reference, anti-patterns) as context. To update manually, or to force it now:

When to use Claude Code instead

Use Claude Code if you want the full Cekura plugin experience: Skills, slash commands, MCP auto-configuration, update support, and MCP failure help.