Locus plugin
Pay-per-use APIs for coding agents. This plugin connects the LocusMCP server and teaches your agent how to use it well: cited web research, paiddata and API lookups, and thousands of metered provider endpoints billed to oneprepaid workspace credit balance.
One repo, one plugin, many agents. The same plugin installs into Claude Code,Codex, Cursor, Grok, OpenClaw, and any client that speaks theAgent Plugins orAgent Skills open standards.
What you get
- MCP server connection to
https://api.paywithlocus.com/api/credits/mcp(streamable HTTP). Sign-in is OAuth with browser consent; no keys are storedin configuration. - The
locusskill: operating instructions for the agent covering toolrouting, cost quotes, idempotent billing, error recovery, and spend safety. - The
locus-setupskill: full self-serve onboarding — account creation(human sign-up through the OAuth page, or agent-owned accounts viaAgentID), capability selection, and a user-requested Stripe fundinghandoff — so the whole product works from inside the plugin.
No account yet? The OAuth sign-in page includes account creation, and thesetup skill walks agents through the rest: platform.paywithlocus.com.
Install
Claude Code
/plugin marketplace add locus-technologies/locus-pro-plugin
/plugin install locus@locus
Then run /mcp, select locus, and authenticate.
Already added the server manually as
locus-proviaclaude mcp add? Removeit first (claude mcp remove locus-pro) so you don't carry two connectionsto the same server.
Codex
codex plugin marketplace add locus-technologies/locus-pro-plugin
codex plugin add locus@locus
codex mcp login locus
Cursor
Add the MCP server directly in ~/.cursor/mcp.json:
{
"mcpServers": {
"locus": {
"url": "https://api.paywithlocus.com/api/credits/mcp",
"headers": { "X-Source-Name": "cursor-plugin" }
}
}
}
Cursor's OAuth flow completes in the browser on first use. Once the Locuslisting clears Cursor Marketplace review, you will also be able to installit from Customize → Plugins (search "Locus") or with /add-plugin locusin chat.
Grok
grok plugin install locus-technologies/locus-pro-plugin --trust
Grok requires explicit trust to install plugins (they can run MCP serversand skills); review the repo, then pass --trust. Grok discovers theserver's OAuth automatically and opens the browser flow on first use.
OpenClaw
Install the plugin from this repo as a marketplace source; the bundlealready maps the MCP server, so no manual server configuration is needed:
openclaw plugins install locus --marketplace locus-technologies/locus-pro-plugin
openclaw gateway restart
openclaw mcp login locus
A new marketplace source triggers a one-time trust prompt (pass --forcefor non-interactive installs), and the gateway restart applies pluginchanges.
Skill only (77+ agents)
npx skills add locus-technologies/locus-pro-plugin
Discovers both Locus skills (usage and setup) and installs your selectioninto whichever agents you have. The skills include the connectioninstructions; add the MCP server in your client's settings to make thetools available.
Any Agent Plugins client
npx plugins add locus-technologies/locus-pro-plugin
Plain MCP (no plugin)
claude mcp add --transport http locus https://api.paywithlocus.com/api/credits/mcp
codex mcp add locus --url https://api.paywithlocus.com/api/credits/mcp
Data handling
The plugin-managed MCP configs send one static request header,X-Source-Name (for example cursor-plugin). It identifies theconfiguration format a host selected and may be used solely for anonymousadoption telemetry; multi-format hosts can prefer a different bundleddefinition than their own overlay — OpenClaw's bundle loader, for example,honors the root .mcp.json and therefore reports grok-plugin. The headeris cosmetic: plain MCP clients that cannot configure static headers stillwork without it.
The repository contains no credential values, and its MCP configurationsstore none. Tool calls send the arguments the agent provides tohttps://api.paywithlocus.com and are billed to the authenticated workspace.If the user explicitly chooses the optional agent-owned setup path, the setupskill also calls https://api.agentmail.to to create and verify an inbox andregister a public signing key, https://api.auth.agentid.com to submit asigned approval, and https://auth.agentid.com to continue thatauthorization transaction. AgentMail receives only the user-approved emailaddress and inbox name, the user-provided one-time code, and the public key;AgentID receives the inbox identity and a one-time signed assertion. Theprivate signing key is generated locally and is never sent. Funding callshttps://api.paywithlocus.com and returns a server-provided Stripe CheckoutURL that the user opens in a browser; neither the plugin nor the agenthandles card details.
Authentication and credentials
Human-owned MCP connections use OAuth 2.1 with dynamic client registration:your client discovers it from the URL, opens a browser sign-in, and a consentscreen in the Locus dashboard scopes the connection. Access and refreshtokens stay in the client's native OAuth store, never in this repo's files.
The optional agent-owned setup path may create an AGENTMAIL_API_KEY, alocally generated P-256 signing key, and an lcac_ value stored asLOCUS_AGENT_CREDENTIAL. Keep them only in the runtime's approved secretstore; never put them in MCP configuration, chat, project files, sourcecontrol, logs, or command arguments. LOCUS_SECRET_KEY is referenced only asa credential class to protect; the skills never read or set it, and neitherlcr_ nor lcac_ values belong in MCP configuration.
Costs and safety
Paid provider calls are live and billed to your workspace credit balance;catalog discovery, quotes, and balance checks are free. The skill instructsagents to pass idempotency keys so a retry reusing its key neverdouble-charges, to quotesignificant calls with estimate_cost first, and to confirm with you beforeunusually large spends. Spend limits and approvals are configured per workspacein the dashboard.
Repository layout
| Path | Consumed by |
|---|---|
.claude-plugin/ |
Claude Code (plugin + marketplace manifest) |
.codex-plugin/, agents/codex/.mcp.json, .agents/plugins/ |
Native Codex plugin, MCP configuration, and marketplace manifest |
.cursor-plugin/ |
Cursor |
.mcp.json, skills/ |
Effective Grok components while the root plugin.json is present (Grok prefers the root manifest) |
.grok-plugin/, agents/grok/ |
Grok marketplace extraction and fallback configuration when no root manifest exists |
plugin.json, mcp.json |
Agent Plugins (open standard) |
agents/<client>/ |
Per-client MCP server config |
skills/ |
Shared Agent Skills-format instructions; metadata.openclaw is an intentional host extension for credential declarations |
Links
- Docs: https://docs.paywithlocus.com
- Dashboard: https://platform.paywithlocus.com
- MCP reference: https://paywithlocus.com/agent/mcp.md
License
MIT