MCP.so
Sign In

Locus Pro MCP Server

@Locus Pro

Basic information

Transport

streamable-http

Authentication

OAuth

Category

Developer Tools

Author

Locus Pro

About Locus Pro MCP Server

Locus Pro connects agents like Claude Code and Codex to thousands of pay-per-use APIs through one hosted MCP server and one prepaid credit balance. Your agent searches the catalog, checks prices, runs approved endpoints and Recipes, and saves Workflows, while you control tool access and spending limits.

Connection details

https://api.paywithlocus.com/api/credits/mcp

Setup

claude mcp add locus-pro --transport http https://api.paywithlocus.com/api/credits/mcp

Locus Pro MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Locus Pro MCP Server?

The Locus Pro MCP server gives your agent access to thousands of paid APIs, including search, research, enrichment and data providers, through one connection and one prepaid credit balance. It is hosted at https://api.paywithlocus.com/api/credits/mcp and uses browser OAuth.

Locus Pro is built so you do not need separate accounts and cards for every provider. You approve which tools your agent can use and fund the balance; the agent finds the right endpoint, checks its price, calls it and reports what it spent. Locus's examples draw on providers such as BuiltWith, Apollo, Hunter, ZeroBounce, Firecrawl and RentCast. Locus Pro is separate from Pay With Locus, the company's USDC wallet product, and does not require a crypto wallet.

How to use Locus Pro MCP Server?

Add the server to your client and complete the browser sign-in; you can create your Locus account when the agent first connects. New accounts start with a zero balance, so add credits by card (Stripe Checkout) under Credits. At the default rate, 1 credit equals $0.001.

Server URL:

https://api.paywithlocus.com/api/credits/mcp

Claude Code

claude mcp add --transport http locus-pro https://api.paywithlocus.com/api/credits/mcp

Then authenticate from /mcp. Locus also offers a plugin that includes this connection plus skills for setup, tool use and Workflows.

Claude Desktop

Add a custom connector named Locus with the MCP URL (Settings, then Connectors, then Add custom connector) and sign in. For claude.ai and Claude Cowork, Locus also suggests uploading its three skill archives (locus, locus-setup, locus-workflows).

Cursor

{
  "mcpServers": {
    "locus-pro": {
      "url": "https://api.paywithlocus.com/api/credits/mcp"
    }
  }
}

Add this to ~/.cursor/mcp.json and complete OAuth in the browser.

VS Code

{
  "servers": {
    "locus-pro": {
      "type": "http",
      "url": "https://api.paywithlocus.com/api/credits/mcp"
    }
  }
}

Add this to .vscode/mcp.json and start the server to sign in.

Locus also documents Codex (codex mcp add locus-pro --url <URL>, then codex mcp login locus-pro), ChatGPT and Cline. Headless clients can use the OAuth device-authorization grant. Enterprise setups can use a scoped Agent Connection credential sent as Authorization: Bearer ${LOCUS_AGENT_CONNECTION}.

Key features of Locus Pro MCP Server

  • One balance for thousands of pay-per-use endpoints, discovered at runtime rather than loaded as individual tools.
  • Discovery and execution tools: search_apis, describe_api, estimate_cost, execute, get_call_result and get_balance.
  • request_tool_access creates a human approval link for a tool that is not yet enabled.
  • Recipes such as web_research, web_extract, gtm_enrich, router_web_search and travel_flights for common multi-provider outcomes.
  • Workflows (workflow_definition, workflow_validate, workflow_run, workflow_runs) to save and rerun a process with a hard credit ceiling.
  • Standard or compact mode (?surface=compact) to control how many tool definitions load into context, and ?tool=provider/endpoint to pin up to 20 endpoints as direct tools.
  • Spending controls: monthly spend caps, low-balance alerts, auto-reload, and per-call and per-run limits on enterprise connections.

Use cases of Locus Pro MCP Server

  • Prospect research: "Find 20 US brands using Shopify Plus and Klaviyo, add the head of ecommerce and a verified work email, and show me an estimate before starting."
  • Competitive analysis: "Use Locus to research three competitors, read their current pricing pages and compare features with sources."
  • Property comparisons: "Compare these five rental listings with property records, rent estimates and commute distances."
  • Record enrichment: "Enrich this company with field-level sources using gtm_enrich."
  • Repeatable jobs: "Save this research process as a Workflow and run it on next week's list with a 5,000-credit ceiling."

Troubleshooting Locus Pro MCP Server

  • Paid calls are refused. Read-only consent (mcp:read) allows discovery, balance checks and estimates; paid calls and Workflows need mcp:execute. Reconnect and grant execute access.
  • A tool is not available. Search returns enabled tools by default. Ask the agent to call request_tool_access and approve the link.
  • Too many tool definitions in context. Switch to compact mode with ?surface=compact, then refresh the connection or start a new session.
  • Calls stop after a spend cap. A monthly spend cap blocks new calls when reached; raise it or add credits under Credits.
  • A second agent app cannot connect. One active OAuth client is included; the Plus ($20/month, 3 clients) or Unlimited ($200/month) plan adds more.

Frequently asked questions

1

Is Locus Pro free?

There is no monthly subscription on the included plan, but tool calls use prepaid credits (1 credit = $0.001 by default), and new accounts start at zero. Optional plans add more connected clients.

2

How does authentication work?

Browser OAuth is the usual connection: add the URL, sign in and approve. Enterprise workspaces can also use scoped Agent Connection credentials sent as a Bearer token.

3

Does my agent see every API at once?

No. Locus does not load the entire catalog as MCP tools; your agent discovers endpoints with search and calls them through `execute`, unless you pin specific endpoints.

4

Can I control spending?

Yes. You can set a monthly spend cap, low-balance alerts and auto-reload, ask for an exact quote with `estimate_cost`, and run Workflows with a hard credit ceiling.

5

Which clients are supported?

Locus documents Claude Code, Claude (claude.ai, Cowork), ChatGPT, Codex, Cursor and Cline, and any client that supports Streamable HTTP with OAuth.

6

Is Locus Pro a crypto product?

No. Locus Pro does not require a crypto wallet; Pay With Locus is the company's separate USDC wallet product.

7

What is the Locus Pro remote MCP server?

The Locus Pro remote MCP server is a hosted Model Context Protocol endpoint at https://api.paywithlocus.com/api/credits/mcp, so AI assistants can connect to it without installing or running anything locally.

8

How do I connect to the Locus Pro MCP server?

Add the endpoint https://api.paywithlocus.com/api/credits/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

9

Does the Locus Pro MCP server require authentication?

Yes. Locus Pro uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

10

Which transport does the Locus Pro MCP server use?

Locus Pro exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments