Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated 3 days ago
Install
Locus
Overview
Description from the maker (original English)
Pay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 0 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://api.paywithlocus.com/api/credits/mcpRun this in your terminal
claude mcp add --transport http locus https://api.paywithlocus.com/api/credits/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"locus": {
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"locus": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://api.paywithlocus.com/api/credits/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ! Caution
Maker matches the repo
The publisher (paywithlocus.com) is not the repo owner (locus-technologies); someone else may have listed it
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Search & AI memoryi
- More stars than 0% of the other 7241 servers in this category
- Published to the registry more recently than 47% of the other 7241 servers in this category
- Basic checks equal to or better than 35% of the other 7241 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Locus safe?
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.37) reached the registry last month.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 20 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated 44 days ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 `locus` skill: operating instructions for the agent covering tool routing, cost quotes, idempotent billing, error recovery, and spend safety.
- The `locus-setup` skill: 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-workflows` skill: 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:locusComplete browser consent, then start a new Code session. The plugin loads all three skills and the Locus MCP connection together.
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. If the current custom-skill picker rejects the production archives, keep the MCP app and use get_locus_guide for the same versioned operating guides.
Codex
codex plugin marketplace add locus-technologies/locus-pro-plugincodex plugin add locus@locus codex mcp login locus
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-pluginSelect 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.
Grok
grok plugin install locus-technologies/locus-pro-plugin --trustGrok 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-pluginDiscovers 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-pluginPlain MCP (no plugin)
claude mcp add --transport http locus https://api.paywithlocus.com/api/credits/mcpcodex 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 |
.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/ / | Per-client MCP server config; the Hermes skill view is generated from skills/ |
skills/ | Canonical Agent Skills-format instructions; metadata.openclaw is an intentional host extension for credential declarations |
Development and releases
Changes merge into stage. Before promotion, a maintainer explicitly chooses one semantic version for every host manifest and w
Only the beginning is shown; read the rest in the repo