This is an early release preview. You may encounter bugs.
NLWeb logo
Unclaimed

Tool interface memory

NLWeb

C 54/100 GitHub score ? This grade is derived from GitHub signals, not user votes. Open for the full breakdown.
Discussion

01 / Summary

About NLWeb.

NLWeb is a set of open protocols and reference tools for adding natural-language interfaces to websites, usable by both people and AI agents. It builds on Schema.org and related semi-structured formats such as RSS, which many sites already publish, and treats that markup as a semantic layer that a conversational endpoint can query.

It has two parts. The first is a protocol for asking a site questions in natural language, with responses returned as JSON using Schema.org vocabulary. The second is a reference implementation that works over sites with structured lists (products, recipes, attractions, reviews) and pairs with UI widgets for a conversational front end. Every NLWeb instance is also an MCP server exposing a core ask method, with A2A support planned. The project describes its relationship to MCP and A2A as like HTML's to HTTP.

The code is offered as proof-of-concept implementations rather than a definitive solution. The repository contains AskAgent (the core query agent, with LLM and vector-store connectors, data ingestion tools, and a sample web UI), AgentFinder (discovery and routing across NLWeb agents), DataFinder (natural language to SQL for sources such as HubSpot, Dynamics 365, and Jira), ModelRouter (selects cost-effective models that meet quality thresholds), and NLWebScorer (neural models for ranking result quality).

It runs on Windows, macOS, and Linux, from laptops to data-center clusters. Supported vector stores are Qdrant, Snowflake, Milvus, Azure AI Search, Elasticsearch, Postgres, and Cloudflare AutoRAG, and supported LLM providers are OpenAI, DeepSeek, Gemini, Anthropic, Inception, and Hugging Face. Prompts, control flow, the UI, and memory are configurable, and Azure is a documented deployment target.

  • Natural-language protocol: ask a site questions and get Schema.org-typed JSON responses
  • Built-in MCP server: every instance exposes an ask method over MCP, with A2A planned
  • Schema.org grounding: uses existing structured markup and RSS feeds as the data layer
  • UI widgets: a sample web UI and widgets for adding a conversational interface to a site
  • Agent discovery: AgentFinder locates and routes to NLWeb agents across the web
  • Natural language to SQL: DataFinder queries enterprise sources such as HubSpot, Dynamics 365, and Jira
  • Model routing: ModelRouter picks cost-effective models that meet quality thresholds
  • Result scoring: neural scorer models rank and evaluate search result quality
  • Vector store choice: Qdrant, Snowflake, Milvus, Azure AI Search, Elasticsearch, Postgres, or Cloudflare AutoRAG
  • LLM choice: OpenAI, DeepSeek, Gemini, Anthropic, Inception, or Hugging Face models

02 / Discussion CREDIBILITY-GATED

Discussion

Reading is open to everyone. Posting and voting need a verified identity or a GitHub grade of B or higher.

  • No discussions yet.

04 / Build

Build with NLWeb.

Browse the catalog for frameworks, tools, and harnesses, each scored on real GitHub credibility.

Get NLWeb →

Browse the catalog