Ways to connect
Compare the ways to reach Kloudlite from an AI agent, a terminal and your own code, and find where each is installed.
Last updated
On this page
Description and operation
General
All ways use the same account, the same /v1 API and the same limits. Choose by who acts: an AI agent, you in a terminal, or your own program.
| Way | Who acts | What you get | Start |
|---|---|---|---|
| MCP | An AI agent in any MCP client | The session tools. The client keeps its own local tools. | Serve the tools |
| MCP and skills | An AI agent in any MCP client | The same tools, and the skills that teach the agent to use them. | Serve the tools, then add the skills |
| Claude Code with kl mode | Claude Code on your computer | The plugin and the tools. Every tool that runs, reads or writes on your computer is refused. | Install the plugin |
| Claude Code plugin without kl mode | Claude Code on your computer | The plugin and the tools. The local tools of Claude Code also work. | Install the plugin, then type /kloudlite:off |
| CLI | You, in a terminal | Every task on a workspace, environment, session or volume as a command. | Install kloudlite |
| SDKs | Your program | The same routes as methods, in Python, TypeScript, Go, Ruby and Java. | SDKs |
| API | Any HTTP client | The routes that all other ways call. | API overview |
The skills are the folders of skills/ in https://github.com/kloudlite/harness. Copy kloudlite into the skills folder of your client. Claude Code reads ~/.claude/skills.
kloudlite claude always starts with kl mode on. Every way except the API needs kloudlite or a token. See API tokens.