How it works
The plugin is a bundle. It adds the OAuth connection to the Locus MCP server and installs the skills. Your client signs you in through the browser and stores and refreshes the tokens.Install the plugin
The plugin lives in the locus-pro-plugin repository.- Claude Code CLI
- Claude Code app
- Codex CLI / app
- Grok
- Other plugin clients
/mcp, select locus, and choose Authenticate.- Keep one OAuth entry per client. If you added the server manually first, remove that entry.
- Update through your client’s plugin manager, then start a fresh session. See the release notes; marketplace listings may update later than GitHub.
- To connect with an agent key instead of OAuth, use the manual configuration.
Set up with one prompt
For OpenClaw, Hermes, Muse, and Instinct, send this prompt in a new agent session:- In your browser: the agent sends you a link to approve.
- With an agent key: Locus creates a 30-day agent key and puts it in the prompt. Use this for agents that run on their own. The agent saves the key and signs in to the Locus CLI with it.
Hermes does not currently have a public plugin listing, and current OpenClaw
does not import the MCP entry from its marketplace bundle. Use the one-prompt
setup for both.
Install only the skills
If you connected your client manually, add the skills on their own:Install the skills
locus, locus-setup, and locus-workflows when prompted. Skills still need an authenticated MCP connection. Clients without local skill support can load the same guides through MCP with get_locus_guide.
Next steps
Connect an MCP client
Connect a client manually, without the plugin.
MCP
See what your agent can do once connected.