Locus MCPサーバー
コミット 2026年11月7日コーディングエージェント向けに、従量課金制のAPIを提供します。プリペイド式のクレジット残高を使用して、ウェブリサーチ、データ検索、および従量課金制のプロバイダーエンドポイントへのアクセスが可能です。
別名 locus-technologies/locus-pro-plugin, locus-pro-plugin
- スター
- 0
- ツール
- —
- ダウンロード数(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キーを保存する必要はありません。セットアップには、エージェントがツールのルーティング、コスト見積もり、およびエラーリカバリを管理するのに役立つ特定のSKILLが含まれています。ヘッドレスランタイムの場合、AgentIDを使用したエージェント所有のアカウントパスが利用可能です。開発者は、中央管理ダッシュボードを通じて、クレジットの管理、利用限度額の設定、およびツールの利用設定を行うことができます。
できること
- 1引用付きのウェブリサーチの実行AIエージェントはLocus接続を使用して、適切な引用を含むウェブ検索を行うことができます。
- 2従量課金制プロバイダーエンドポイントの管理コーディングエージェントは、単一のプリペイド残高で請求される幅広いサードパーティサービスにアクセスできます。
- 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を開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
人間が利用する場合、このサーバーにはAPIキーが必要ですか?
いいえ、人間が所有する接続にはブラウザでの同意を伴うOAuthを使用するため、設定ファイルにキーを保存する必要はありません。
リトライ時に誤って二重課金されるのを防ぐにはどうすればよいですか?
LocusのSKILLは、エージェントがべき等性キーを使用するように指示します。これにより、同じキーを使用して呼び出しをリトライしても、2回目の課金が発生することはありません。
ツール呼び出しを実行する前に、コストを見積もることはできますか?
はい、エージェントは実行前に重要な呼び出しの見積もりを取得するために、estimate_costツールを使用するように指示されています。