MCP discovery, zero config

WebMCP enabled — tools: get_setup_guide, get_spec_summary, get_tools_list

Discover and call MCP tools on any domain by name.

Like OAuth discovery with /.well-known — but for MCP. The domain advertises what it can do; your agent discovers it and calls it. No per-domain setup.

Get started Live gateway (gateway.toolingready.com) →

Overview

  1. Discovery

    Give the gateway a domain. It fetches /.well-known/mcp.json (the server card) from that domain.

  2. One domain → one tool set

    Tools for that domain are exactly what the server card lists. No mixing; the domain owns the answer.

  3. Proxy

    The gateway connects to the endpoint in the card and forwards list_tools and call_tool. Your agent talks to the gateway; the gateway talks to the domain.

In one line: domain name → well-known URL → server card → connect and proxy tools.

Why use it

  • No manual MCP config User or agent names a domain; discovery is automatic.
  • Domain owns the answer One well-known URL describes tools, endpoint, and auth.
  • Scales to many domains Same flow for every domain. Add a site by publishing a server card.
  • Familiar pattern Same discovery idea as OAuth and OpenID. Fits existing infra.

Gateway tools

The gateway exposes four tools to your MCP client (e.g. Claude Desktop).

  • discover_domain(domain) — Fetches server card and optional skill/instructions.
  • list_remote_tools(domain) — Lists tools and schemas for a discovered domain.
  • call_remote_tool(domain, tool_name, arguments) — Invokes a tool on the remote server.
  • get_domain_context(domain) — Full context (card + skill + instructions) for the content window.

Call tools by URL

MCP-enabled sites can expose tools via direct URLs. No JSON-RPC needed — just GET /tool/:name.

For example, on this site you can call:

Use Accept: application/json to get MCP-style JSON instead of markdown. For tools with parameters, pass them as query params: /tool/:name?param1=value1.

The server card (/.well-known/mcp.json) advertises tool_url_template and per-tool url so clients can discover and use these endpoints.

Setup

Add the gateway as a remote connector in Claude Desktop.

1. Add custom connector in Claude

In Claude Desktop go to Settings → Connectors → Add custom connector. Use:

  • Name: Gateway
  • Remote MCP server URL: https://gateway.toolingready.com/mcp

Save and Claude will connect to the live gateway. No config file editing required.

Then in Claude, type discover toolingready.com — it's an MCP-enabled site, so the gateway will discover its tools and you can use them.

Live gateway: MCP endpoint https://gateway.toolingready.com/mcp, health check https://gateway.toolingready.com/health.

Optional: crawl data

For faster discovery and rich skill/instructions, run the gMCP crawler and point the gateway at the output (file or Supabase). Set CRAWLED_JSON_PATH for a local file, or use a gateway build that reads from your database.

Ship domain discovery today

One gateway. Any domain that serves /.well-known/mcp.json. No per-domain config.

Setup guide