Home / Docs / Install

Local-first install

Default setup takes two commands.

The default setup is local-first. You install the package globally, start the local HTTP service, and manage credentials from the browser UI running on your machine. 

npm install -g @simonsbs/keylore
keylore-http start

What happens next

First-run checklist.

1

Install the package

Run npm install -g @simonsbs/keylore to install the KeyLore CLI and supporting components on your system.

2

Start the local HTTP service

Run keylore-http start. This launches the local service used by the UI and client integrations.

3

Open the local UI

Visit http://127.0.0.1:8787/ in your browser. From there you can add credentials and define the metadata that AI tools will use for discovery.

4

Connect a supported client

After adding credentials, connect Codex, Gemini CLI, Claude CLI, or another MCP client so it can inspect metadata and request brokered access.

Install FAQ

Two common install questions.

Is KeyLore local by default?

Yes. The standard install starts a local HTTP service and browser UI on your machine. That makes evaluation straightforward and keeps the initial deployment model simple.

Do I need to move everything out of .env immediately?

No. Most teams start by migrating the highest-risk credentials first: tokens currently exposed to AI coding tools, broad-scope developer keys, or secrets that are often copied between repos and shells.

Next step

Use the UI

See the actual add token, test token, and connect MCP workflow.

Then integrate

Connect your MCP client

Pick Codex, Gemini CLI, or Claude CLI and follow the client-specific setup path.