Locus MCP server
{
"mcpServers": {
"locus": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}{
"mcpServers": {
"locus": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}{
"mcpServers": {
"locus": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}{
"servers": {
"locus": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}{
"mcpServers": {
"locus": {
"type": "http",
"url": "https://api.paywithlocus.com/api/credits/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.3.37
What it does
This MCP server connects agents to Locus, a pay-per-use API platform that provides web research, data lookups, and access to thousands of metered provider endpoints billed against prepaid workspace credits. It is for developers building agents that need to call external APIs with centralized billing and cost management.
- Query external data sources and APIs from within an agent, with all costs billed to a single Locus workspace credit balance.
- Perform cited web research and data lookups as part of agent workflows, with cost estimates before execution.
- Access thousands of metered provider endpoints through a single integration point with idempotent billing and spend safety controls.
Tools this server exposes
| Tool | Does |
|---|---|
| locus | Operating instructions for the agent covering tool routing, cost quotes, idempotent billing, error recovery, and spend safety when using Locus APIs. |
| locus-setup | Self-serve onboarding skill for account creation, capability selection, and Stripe funding handoff to set up a Locus workspace. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.