Locus MCP server
2026년 11월 7일 커밋코딩 에이전트가 웹 리서치, 데이터 조회 및 종량제 제공업체 엔드포인트에 액세스할 수 있도록 선불 크레딧 잔액 기반의 사용량 기반 API를 제공합니다.
다른 이름 locus-technologies/locus-pro-plugin, locus-pro-plugin
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.3.40
- 마지막 커밋
- 2026년 11월 7일
- 라이선스
- MIT
Locus MCP란?
코딩 에이전트가 웹 리서치, 데이터 조회 및 종량제 제공업체 엔드포인트에 액세스할 수 있도록 선불 크레딧 잔액 기반의 사용량 기반 API를 제공합니다.
프로젝트 README에서 생성된 요약
Locus MCP server 정보
Locus는 코딩 에이전트가 단일 선불 크레딧 잔액을 통해 유료 웹 리서치, 데이터 조회 및 수천 개의 종량제 제공업체 엔드포인트에 액세스할 수 있는 방법을 제공합니다. streamable HTTP 연결을 통한 원격 MCP server로 작동하여, 개발자가 다양한 API 비용을 하나의 워크스페이스로 통합할 수 있습니다. 이 시스템은 Claude Code, Cursor, Codex, Grok을 비롯한 다양한 클라이언트와 IDE 기반 에이전트에서 사용할 수 있도록 설계되었습니다.
사용자는 브라우저 기반 승인을 사용하는 OAuth 2.1을 통해 서비스에 연결하며, 이는 로컬 설정 파일에 API key를 저장하지 않음을 의미합니다. 설정에는 에이전트가 도구 라우팅, 비용 추정 및 오류 복구를 관리할 수 있도록 돕는 특정 SKILL이 포함되어 있습니다. 헤드리스 런타임의 경우 AgentID를 사용하는 에이전트 소유 계정 경로를 사용할 수 있습니다. 개발자는 중앙 집중식 대시보드를 통해 크레딧을 관리하고, 지출 한도를 설정하며, 도구 가용성을 구성할 수 있습니다.
활용 사례
- 1출처가 명시된 웹 리서치 수행AI 에이전트는 Locus 연결을 사용하여 적절한 인용이 포함된 웹 검색을 수행할 수 있습니다.
- 2종량제 제공업체 엔드포인트 관리코딩 에이전트는 단일 선불 잔액으로 청구되는 매우 다양한 제3자 서비스에 액세스할 수 있습니다.
- 3내구성이 있는 자동화된 워크플로 실행사용자는 장기 실행 작업에 대한 복구 기능을 포함하는 호스팅된 워크플로를 작성하고 실행할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Locus MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Locus MCP 설치
$ claude mcp add --transport http locus-pro-plugin https://api.paywithlocus.com/api/credits/mcpCursor에 Locus MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"locus-pro-plugin": {
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}VS Code에 Locus MCP 설치
.vscode/mcp.json
{
"servers": {
"locus-pro-plugin": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}VS Code CLI에 Locus MCP 설치
$ code --add-mcp '{"name":"locus-pro-plugin","type":"http","url":"https://api.paywithlocus.com/api/credits/mcp"}'Codex에 Locus MCP 설치
$ codex mcp add locus-pro-plugin --url https://api.paywithlocus.com/api/credits/mcpCodex config.toml에 Locus MCP 설치
~/.codex/config.toml
[mcp_servers.locus-pro-plugin] url = "https://api.paywithlocus.com/api/credits/mcp"
Gemini CLI에 Locus MCP 설치
$ gemini mcp add -s user --transport http locus-pro-plugin https://api.paywithlocus.com/api/credits/mcpGemini settings.json에 Locus MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"locus-pro-plugin": {
"url": "https://api.paywithlocus.com/api/credits/mcp",
"type": "http"
}
}
}자동 검사
2026년 11월 15일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능locus-technologies/locus-pro-plugin is public and reachablegithub.com/locus-technologies/locus-pro-plugin ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-07github.com/locus-technologies/locus-pro-plugin ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기Locus plugin
Pay-per-use APIs for coding agents. This plugin connects the Locus MCP server and teaches your agent how to use it well: cited web research, paid data and API lookups, and thousands of metered provider endpoints billed to one prepaid workspace credit balance.
One repo, many agents. Claude Code, Codex, and Grok can install the plugin directly today. Other clients can use the same repository's MCP configuration, three Agent Skills, or the one-URL bootstrap below.
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 stored in configuration. - The
locusskill: operating instructions for the agent covering tool routing, cost quotes, idempotent billing, error recovery, and spend safety. - The
locus-setupskill: onboarding when the user asks the agent to do it. Human sign-up through the OAuth page is the default. Agent-owned accounts via AgentID exist for headless runtimes, and only they get agent-driven capability selection and a user-requested Stripe funding handoff; human-owned accounts manage both in the dashboard. - The
locus-workflowsskill: safe hosted Workflow authoring, fixtures, bounded pilots, immutable versions, and durable run recovery through the same authorized connection.
No account yet? Authenticate the server and create the account on the OAuth sign-in page that opens; that is the whole flow for a person with a browser. Tools are enabled and credits added in the dashboard at platform.paywithlocus.com.
Install
Claude Code CLI
/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? Remove it first (claude mcp remove locus-pro) so you don't carry two connections to the same server.
Claude Code app
In Code, open Customize → Plugins → Add plugin → Add marketplace → Add from
a repository. Choose locus-technologies/locus-pro-plugin, select Sync,
then Add Locus. Authenticate the plugin from Terminal:
claude mcp login plugin:locus:locus
Complete browser consent, then start a new Code session. The plugin loads all three skills and the Locus MCP connection together.
If the login command says plugin:locus:locus is missing and
claude mcp get locus reports a legacy Local config, remove the shadowing
project entry with claude mcp remove locus -s local, restart Code, and retry.
Claude Cowork and claude.ai
Open Customize → Connectors → Yours → Add connector → Add custom connector.
Name it Locus, use
https://api.paywithlocus.com/api/credits/mcp, then connect through browser
OAuth. Under Customize → Skills → Yours → Add skill, upload all three:
ChatGPT.com
Enable Developer mode under Settings → Apps → Advanced settings, then open
Plugins → Create app. Use the production MCP URL above and OAuth. Start a
Work task and select Locus Pro from Plugins. This custom-app path
provides MCP tools. If the current Skills picker leaves the production
archives ineligible, keep the MCP app and use get_locus_guide for the same
versioned operating guides.
Codex CLI and app
codex plugin marketplace add locus-technologies/locus-pro-plugin
codex plugin add locus@locus
codex mcp login locus --scopes mcp:read,mcp:execute,offline_access
Start a new CLI or desktop session after installation. The plugin loads all three Locus skills with the MCP connection.
Hermes
Send this prompt to Hermes:
Install Locus Pro by following https://paywithlocus.com/SKILL.md. Use production.
The bootstrap installs a supported adapter and all three released skill trees,
then guides browser or device authentication. The official Hermes plugin
listing is still pending; hermes plugins install locus is not live yet.
Cline
cline mcp install locus --transport http \
https://api.paywithlocus.com/api/credits/mcp
Keep Remote (HTTP), choose OAuth, leave the client ID blank for dynamic registration, and complete sign-in in the browser. No clone, build, API key, or environment variable is required. Then install all three skills:
npx skills add locus-technologies/locus-pro-plugin
Select locus, locus-setup, and locus-workflows, then start a new session.
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 Locus
listing clears Cursor Marketplace review, you will also be able to install
it from Customize → Plugins (search "Locus") or with /add-plugin locus
in chat. Until then, install the three skills separately with
npx skills add locus-technologies/locus-pro-plugin and select all three.
Devin
In Devin, open Customize → Plugins → Add plugin → From repository and use
locus-technologies/locus-pro-plugin with subdirectory agents/devin. From the
Devin CLI:
devin plugins install locus-technologies/locus-pro-plugin/agents/devin
devin mcp login locus
Cloud sessions connect the server from the plugin's MCP under Customize → MCPs → Connect, which runs the same browser OAuth.
Grok
grok plugin install locus-technologies/locus-pro-plugin --trust
Grok requires explicit trust to install plugins (they can run MCP servers
and skills); review the repo, then pass --trust. Grok discovers the
server's OAuth automatically and opens the browser flow on first use.
OpenClaw
Send this prompt to OpenClaw:
Install Locus Pro by following https://paywithlocus.com/SKILL.md. Use production.
The bootstrap installs a supported adapter and all three released skill trees. Current OpenClaw can unpack the marketplace bundle but does not import its MCP server, so do not use the marketplace route until that host behavior changes.
Muse and Instinct
Send either agent the same tested prompt:
Install Locus Pro by following https://paywithlocus.com/SKILL.md. Use production.
Skill only (77+ agents)
npx skills add locus-technologies/locus-pro-plugin
Discovers the Locus usage, setup, and Workflow skills and installs your selection into whichever agents you have. The skills include the connection instructions; add the MCP server in your client's settings to make the tools 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
On file-capable clients, pair this with the Skill only install above. On an
MCP-only host, call get_locus_guide after connecting.
One-URL bootstrap and remote guides
Ask a capable agent to read https://paywithlocus.com/SKILL.md and set up
Locus. The bootstrap probes the actual host, preserves a healthy existing
connection, selects a supported adapter, and reports any browser consent,
restart, or runtime limitation still outstanding.
An MCP-only host does not need persistent files. After connecting, it can call
get_locus_guide to retrieve the same versioned skill and reference content
published in this repository. The public guide manifest is served from the
Locus API; customer-owned Workflow source and invocation guides remain private
account artifacts and never enter that public bundle.
Hosted Workflow tools are advertised only when the backend capability is live and the current connection can execute. A Workflow run is a constrained child of that existing connection, not a second registered agent. The first runtime supports approved TypeScript and every live catalog binding Locus has reviewed, including native Tools, maintained Recipes, and explicitly verified external buyer-rail listings. Tenant-imported and unverified external bindings require an exceptional platform approval; a server deny override can halt any binding. Connection scope, enablement, contract, availability, and run budgets still apply. The runtime also provides bounded concurrency, fixtures, pilots, durable inspection, cancellation, and resume; arbitrary npm dependencies, external connector credentials, scheduling, and publication are not implied.
Data handling
The plugin-managed MCP configs send one static request header,
X-Source-Name (for example cursor-plugin). It identifies the
configuration format a host selected and may be used solely for anonymous
adoption telemetry; multi-format hosts can prefer a different bundled
definition than their own overlay — OpenClaw's bundle loader, for example,
honors the root .mcp.json and therefore reports grok-plugin. The header
is cosmetic: plain MCP clients that cannot configure static headers still
work without it.
The repository contains no credential values, and its MCP configurations
store none. Tool calls send the arguments the agent provides to
https://api.paywithlocus.com and are billed to the authenticated workspace.
If the user explicitly chooses the optional agent-owned setup path, the setup
skill also calls https://api.agentmail.to to create and verify an inbox and
register a public signing key, https://api.auth.agentid.com to submit a
signed approval, and https://auth.agentid.com to continue that
authorization transaction. AgentMail receives only the user-approved email
address and inbox name, the user-provided one-time code, and the public key;
AgentID receives the inbox identity and a one-time signed assertion. The
private signing key is generated locally and is never sent. Funding calls
https://api.paywithlocus.com and returns a server-provided Stripe Checkout
URL that the user opens in a browser; neither the plugin nor the agent
handles 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 consent screen in the Locus dashboard scopes the connection. Access and refresh tokens 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, a
locally generated P-256 signing key, and an lcac_ value stored as
LOCUS_AGENT_CREDENTIAL. Keep them only in the runtime's approved secret
store; never put them in MCP configuration, chat, project files, source
control, logs, or command arguments. LOCUS_SECRET_KEY is referenced only as
a credential class to protect; the skills never read or set it, and neither
lcr_ 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 instructs
agents to pass idempotency keys so a retry reusing its key never
double-charges, to quote
significant calls with estimate_cost first, and to confirm with you before
unusually large spends. Spend limits and approvals are configured per workspace
in 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 |
agents/devin/ |
Devin plugin root; its skills and logo are generated from the root so the contributor AGENTS.md is not loaded as a Devin rule |
.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; the Hermes skill view is generated from skills/ |
skills/ |
Canonical Agent Skills-format instructions; metadata stays a flat string map so strict hosts load every skill |
Development and releases
Changes merge into stage. Before promotion, a maintainer explicitly chooses
one semantic version for every host manifest and writes its changelog entry;
CI checks that coordinated version but never updates it. A validated stage
to main promotion creates the immutable GitHub release, checksummed plugin
and skill archives, the Agent Skills discovery payload, and the matching MCP
Registry version. Public directories that require vendor review (OpenAI and
Cursor) are submitted through their review portals after that release.
See AGENTS.md for the branch policy, required checks, release prerequisites, and isolated local testing instructions for production and the stage MCP environment across Claude Code, Codex, Cursor, Grok, OpenClaw, Agent Plugins, Agent Skills, and ChatGPT.
Links
- Docs: https://docs.paywithlocus.com
- Dashboard: https://platform.paywithlocus.com
- MCP reference: https://paywithlocus.com/agent/mcp.md
License
Locus MCP 질문
Locus MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http locus-pro-plugin https://api.paywithlocus.com/api/credits/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Locus MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
사용자가 직접 사용할 때 API key가 필요한가요?
아니요, 사용자가 소유한 연결은 브라우저 승인을 통한 OAuth를 사용하므로 설정 파일에 키를 저장할 필요가 없습니다.
재시도 시 의도치 않은 중복 결제를 방지할 수 있나요?
Locus SKILL은 에이전트가 멱등성 키(idempotency keys)를 사용하도록 지시하므로, 동일한 키로 호출을 재시도해도 중복 결제가 발생하지 않습니다.
도구 호출 실행 전에 비용을 예측할 수 있나요?
네, 에이전트는 실행 전 중요한 호출에 대해 견적을 내도록 estimate_cost 도구를 사용하도록 지시받습니다.