Tooling Ready

WebMCP lets websites tell AI agents what they can do.One server card, instant discovery, direct tool calls — no vision models, no scraping, no wasted tokens.

Comment

Tooling Ready

The first agent-native website — where AI agents discover, connect, and call tools without ever seeing a pixel.

💡 Inspiration

AI agents waste billions of tokens on vision models and DOM parsing just to figure out what a website can do. We asked a simple question:

What if sites just told agents directly?

⚙️ What It Does

Tooling Ready is the first agent-native website. It publishes a machine-readable server card at /.well-known/mcp.json so AI agents can discover, connect to, and call tools — no screenshots, no scraping, no guessing.

Three core tools power it:

  • Regenerate — Self-updating agent-facing docs via Tavily + LLMs
  • Extract Entities — Structured NER powered by GLiNER2 (Pioneer)
  • Discovery + Proxy Gateway — Turns any domain name into a full tool set

🏗️ How We Built It

We built a gateway called gMCP that fetches server cards from any domain and proxies MCP tool calls in real time. The site itself exposes skill.md, instructions.md, and llms.txt so agents get structured tooling on first contact.

Stack:

Layer Tech
Search & Extract Tavily
Doc Regeneration OpenAI + Anthropic
Entity Extraction Pioneer (GLiNER2)
Discovery Protocol gMCP Gateway

🧱 Challenges We Ran Into

Getting the discovery flow right was the hardest part — making sure the server card format was clean enough for agents to parse in one call without extra context. We spent real time balancing what goes in skill.md vs. instructions.md vs. llms.txt so agents get exactly what they need without overloading the context window.

🏆 Accomplishments We're Proud Of

We built the first website where an AI agent can type one command, discover every available tool, and start chaining calls — zero vision, zero DOM parsing.

OAuth-style discovery for the agentic web, working today.

📚 What We Learned

Agents don't need to see your site. They need to know what your site can do.

The gap between "sites for humans" and "sites for agents" is smaller than people think — you don't have to rebuild everything, just expose capabilities in a standard way.

🚀 What's Next

  • Expanding the gateway to support more domains
  • Refining the server card spec
  • Pushing toward a standard so any site owner can make their site agent-native in minutes

The goal: WebMCP becomes the default way the web talks to AI agents.

Built With

Share this project:

Updates