1ToolRing

Pay-per-call search, SEO, maps, e-commerce price and exchange-rate data for AI agents. One key, prepaid balance, OAuth sign-in.

Hosted MCP Server

npx add-mcp 'https://mcp.1toolring.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Connect 1ToolRing to your AI client

1ToolRing is a remote MCP server. Add it to your client with the URL below, then sign in with your 1ToolRing account in the browser. Nothing to paste: the client receives its own key, which you can see and revoke on the Keys page.

https://mcp.1toolring.com/mcp

Server name: 1toolring. No account yet? Sign up and add balance on the Billing page; discovering and inspecting tools is free.

Claude Code

one command, then sign in

  1. Add the server from your terminal: Copy
    claude mcp add --transport http 1toolring https://mcp.1toolring.com/mcp
    
  2. Start Claude Code, run /mcp, select 1toolring, then Authenticate. Your browser opens the 1ToolRing approval page; choose the workspace and select Allow.
  3. Or sign in straight from the shell: Copy
    claude mcp login 1toolring
    

Steps follow Claude Code: Connect to tools via MCP (checked 2026-11-02).

Claude

claude.ai, Desktop and Cowork: custom connector

  1. Open Customize > Connectors, select + Add, then Add custom connector.
  2. Name it 1toolring and enter the server URL, then select Continue: Copy
    https://mcp.1toolring.com/mcp
    
  3. The URL is all it needs: leave the OAuth Client ID and Client Secret empty (the client registers itself), then select Add.
  4. Select Connect next to the connector and approve access on the 1ToolRing page.
  5. On Team and Enterprise plans an Owner adds the connector in Organization settings > Connectors; each member then selects Connect. The Free plan allows one custom connector.

Steps follow Claude: Add an unlisted connector (checked 2026-11-02).

ChatGPT

custom MCP server (Business, Enterprise, Edu)

  1. Open Plugins, select the plus button, then Add custom MCP server.
  2. Name it 1toolring. Under Connection enter the server URL: Copy
    https://mcp.1toolring.com/mcp
    
  3. Choose OAuth for authentication, accept the risk warning, select Create as a plugin, and approve access on the 1ToolRing page when asked.
  4. Full custom MCP servers are available on ChatGPT Business and Enterprise/Edu on the web; in a Business workspace only admins and owners can add one.

Steps follow OpenAI Help: Connecting custom MCP servers in ChatGPT (checked 2026-11-02).

Cursor

one-click install link

  1. Open the install link and confirm in Cursor.
  2. Cursor signs in with OAuth the first time it connects; approve access on the 1ToolRing page.
  3. Or add it to ~/.cursor/mcp.json by hand: Copy
    {
      "mcpServers": {
        "1toolring": {
          "url": "https://mcp.1toolring.com/mcp"
        }
      }
    }
    

Steps follow Cursor: MCP install links and authentication (checked 2026-11-02).

VS Code / Copilot

one-click install link

  1. Open the install link and confirm in VS Code.
  2. Or run MCP: Add Server, choose HTTP, and enter the server URL: Copy
    https://mcp.1toolring.com/mcp
    
  3. VS Code opens a browser window to sign in on first use; approve access on the 1ToolRing page.

Steps follow VS Code: MCP servers and installation URLs (checked 2026-11-02).

Other clients

Hermes, OpenCode, Gemini CLI, Any MCP client: add a remote MCP server (streamable HTTP) named 1toolring with the URL https://mcp.1toolring.com/mcp. A client that supports MCP authorization opens the 1ToolRing sign-in page on first use. If yours does not, use an API key as below.

API key instead of sign-in

For scripts, CI and clients without OAuth support, send a key as a header. Create one on the Keys page; it is shown once.

Claude Code with a key

claude mcp add --transport http 1toolring https://mcp.1toolring.com/mcp --header "Authorization: Bearer YOUR_KEY"

JSON config with a key

The usual mcpServers shape; the exact file and field names differ per client, so check your client's documentation.

{
  "mcpServers": {
    "1toolring": {
      "type": "http",
      "url": "https://mcp.1toolring.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Plain HTTP, no MCP

The same discover, inspect and run flow over REST. See the tools reference.

curl -s -X POST "https://api.1toolring.com/api/v1/tools/discover" \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"google search results for a keyword"}'

What you get

Hundreds of tools across search and SEO, maps and places, e-commerce products and prices, and market data, from third-party providers. People or contact data, email finding, social media data and web scraping are not offered. discover_tools finds a tool by the job, inspect_tool shows its input and price, run_tool runs it and get_tool_run fetches a slow result. Calls are paid from your prepaid balance, shown in US dollars and rupiah. Each run reports what it cost, and a failed call is never charged.

Something not working?

Write to hello@1toolring.com, or read the MCP docs.