Skip to main content
Kepler works with what is already on your machine: kubectl, cloud CLIs, ssh, the files in your workspaces. When you need more, you connect an integration, drop in a skill, or teach it a command. This page covers all four ways to extend it.

​
Integrations (MCP servers)

An integration gives Kepler tools for one part of your stack: query Grafana, list PagerDuty incidents, read a GitHub pull request, describe an EC2 instance. Integrations speak MCP, so anything with an MCP server can be connected. Open Settings > Tools & MCP. The catalog lists the integrations Kepler knows how to set up:
Settings > Tools & MCP in Kepler. Progressive tool discovery at the top, then Configured with two integrations marked Enabled, a Detected on this machine row counting 19 command-line tools, and the catalog below starting with RubixKube and Grafana.

​
Add an integration

1

Pick it from the catalog

Open Settings > Tools & MCP and choose the integration. Each card tells you what credential it needs.
2

Add the credential as a secret

Kepler stores tokens in your operating system keychain and refers to them by name. See Secrets below.
3

Ask for it in chat

You do not need to restart anything. On the next turn, Kepler can use the new tools.
You can also skip the settings page and ask directly:
Anything not in the catalog can be added as a custom MCP server on the same page. The page also lists the command-line tools it detected on your machine, such as kubectl, helm and your cloud CLIs, which Kepler can use directly without any setup.

​
What integrations look like in practice

MCP tools ask for your approval before they run, unless you change that in Settings > Permissions. The approval shows the tool and its arguments so you can see exactly what will be sent.
Large servers hand over their tools a few at a time, so the conversation stays fast even with many integrations connected. Progressive tool discovery in Settings > Tools & MCP controls this. Leave it on.

​
Secrets

Credentials never sit in a config file. Settings > Secrets keeps named credentials in your operating system keychain. An integration config only ever holds the name, written as ${NAME}.
1

Add a credential

In Settings > Secrets, add a name such as GRAFANA_TOKEN and paste the value.
2

Reference it by name

In the integration’s settings, use ${GRAFANA_TOKEN} wherever the token is needed.
The Secrets page shows which integrations use each credential, so you know what breaks before you delete one.

​
Skills

A skill is a capability written in Markdown: a SKILL.md file, and optionally scripts beside it, in its own folder. Kepler loads a skill the moment it is needed, or when you trigger it as a slash command. Skills live in ~/.kepler/skills for everything you do, or in .kepler/skills inside a workspace for one project. Claude Code skill folders work as they are: drop them in, or import them from Settings > Customize, which lists any Claude Code skills it finds on your machine. A skill worth writing is one you would otherwise explain every time:
Save that as ~/.kepler/skills/pod-crashloop-triage/SKILL.md. It appears in the / menu as /pod-crashloop-triage, and Kepler also reaches for it on its own when the situation fits. Manage skills in Settings > Customize: create one from a template, import from Claude Code, edit the file, add a script.

​
Custom slash commands

A custom command is a prompt you keep retyping, saved under a name. The quickest way to make one is to describe it:
Kepler drafts the command and saves it. From then on you call it by name, with arguments:
Commands are Markdown files. The file name is the command name, and $ARGUMENTS inside the file is replaced by whatever you type after the command. See Commands and shortcuts for the full built-in list.

​
Specialist agents

A specialist is a read-only agent with its own persona and tools. Kepler builds one-off specialists on its own when it fans out an investigation, so you do not have to think about them. Save one yourself when you ask the same kind of question often:
Saved specialists appear in Settings > Agents. Ask for parallel work and Kepler hands side questions to specialists that run in the background while the main conversation keeps moving:

​
Identity on your channels

When Kepler reaches you on WhatsApp, Slack, Telegram or Discord, it signs its replies with a name and emoji you choose in Settings > Customize, so its messages never read as yours. See Chat from your phone.
Standing rules and lifecycle hooks (run a command before a tool, after a run, or on approval) are listed under Settings > Customize as coming soon. They are not available in this release.

​
Where to go next

Permissions

Set MCP servers to allow, ask or block.

Commands and shortcuts

Every built-in slash command.

Everyday workflows

Prompts that use your integrations.

Settings reference

Tools & MCP, Secrets, Agents and Customize, in detail.