Locus product guide · Updated
How to add Locus to the Claude desktop app
To add Locus to the Claude desktop app, open the Code tab, go to Customize, Plugins, and add the marketplace locus-technologies/locus-pro-plugin. Add Locus, run claude mcp login plugin:locus:locus in a terminal, approve in your browser, and start a new Code session. Your agent can then pay for APIs from one credit balance.
Setup, step by step
Step 1
Create a Locus Pro account
Sign up at paywithlocus.com/pro. The Free plan has no subscription. Paid tool calls use prepaid credits.
Step 2
Add the Locus marketplace
In the Claude app, open Code, then Customize, Plugins, Add plugin, Add marketplace, Add from a repository. Enter the repository below and choose Sync.
locus-technologies/locus-pro-plugin
Step 3
Add the Locus plugin
Choose Add Locus. The plugin brings the hosted MCP server and the locus, locus-setup, and locus-workflows skills.
Step 4
Sign in from a terminal
Run this command in Terminal and approve Locus in your browser.
claude mcp login plugin:locus:locus
Step 5
Start a new Code session
Open a fresh session so the tools and skills load. Use a local session. The plugin browser is not available in cloud sessions.
Step 6
Check the connection
Ask: "What's my Locus balance?" A balance check is free. If Claude returns your credit balance, setup worked.
Why does /plugin not work in the Claude desktop app?
The Code tab does not run /plugin marketplace add as text. It opens the native Plugins screen instead. Use the Customize, Plugins path in the steps above.
The terminal CLI and the desktop app read the same settings files on one computer. A plugin installed at user scope in one shows up in the other.
Which Claude app tab should I set up?
This guide covers the Code tab. Chat and Cowork use a custom connector plus uploaded skills instead of a plugin. Follow the Claude.ai and Cowork guide for those.
| Where you use Claude | Method |
|---|---|
| Code tab in the desktop app | Plugin marketplace plus terminal login |
| Claude Code in a terminal | /plugin commands, then /mcp |
| Chat or Cowork | Custom connector plus three skill zips |
How do I fix "plugin is missing" or login errors?
An older manual MCP entry named locus can shadow the plugin in a project. Remove it, then run the login again.
If the browser approval stalls, close it and rerun claude mcp login plugin:locus:locus. Then start a new session. Existing sessions keep the tools they loaded at start.
- claude mcp remove locus -s local
- claude mcp login plugin:locus:locus
What can the agent do after setup?
Claude can search the Locus catalog, read an API's schema and price, and run the call against your credit balance. You do not need an account or key with each provider.
Try a small real task first, such as finding a company's website. Then review the charge in Locus activity.
Frequently asked questions
Do I need Claude Code installed in a terminal?
You need the claude command for the sign-in step. The plugin itself is added in the app. After login, the app loads Locus in new Code sessions.
Can I use the + button next to the prompt instead of Customize?
Anthropic documents + then Plugins then Add plugin as another way into the plugin browser. We tested the Customize path. Both reach the same Plugins screen.
Does connecting Locus cost anything?
No. Installing and checking your balance are free. Paid API calls use credits at the price shown before the call.
Implementation references
Use these first-party references for current request contracts and account requirements. Tool availability, prices, and negotiated terms can change.
Sources
Third-party details were checked on September 29, 2026. Vendors change pricing and features often, so confirm on their site before you decide.