NLWeb vs Model Context Protocol
The map lists them as complementary: sites and agents commonly implement both. Model Context Protocol is a prerequisite of NLWeb.
| NLWeb | Model Context Protocol MCP | |
|---|---|---|
| Lifecycle step | 5 Act: Do something for me | 5 Act: Do something for me |
| Answers | How can a site expose a natural-language question-answering interface grounded in its own Schema.org-structured content, for both humans and agents? | How does an AI application call tools and pull structured context, prompts, and data from an external server? |
| Governed by | Originated at Microsoft; the reference implementation now lives under a separate community GitHub org (nlweb-ai), not microsoft/NLWeb directly — github.com/microsoft/NLWeb redirects to github.com/nlweb-ai/NLWeb | Agentic AI Foundation (Linux Foundation umbrella); day-to-day spec work in the modelcontextprotocol GitHub org via public SEPs (Specification Enhancement Proposals) and working groups |
| Status (issuer's words) | "Main reference implementation... implemented in Python"; described by its own README as a proof-of-concept the community is invited to build alternative implementations of, not a definitive solution | Active open specification, current dated release 2026-07-28 |
| Phase | draft | living |
| Version | unversioned; MIT-licensed, actively committed | 2026-07-28 (2026-07-28) |
| Form / transport | endpoint | endpoint |
| Found at | none confirmed; nlweb.ai (including nlweb.ai/spec) was unreachable via curl and firecrawl in this verification pass | GET {endpoint}/server-card (SEP-2127 Server Card, Final 2026-10-06; found via an AI Catalog entry) |
| Adoption | unmeasured | claimed — Wikipedia (OpenAI, Google DeepMind adopted MCP by March 2025) and WorkOS ('adopted by OpenAI, Google DeepMind, Microsoft, and thousands of development teams') |
| Evidence | 2 verified, 1 reported | 7 verified, 2 reported |
| Primary use case | Let agents act on my website | Expose tools to agents |
| Last verified | 2026-10-19 (current) | 2026-10-19 (current) |
| Specification | https://github.com/nlweb-ai/NLWeb | https://modelcontextprotocol.io/specification/2026-07-28/index |
When to use which
- Choose NLWeb when your question is “How can a site expose a natural-language question-answering interface grounded in its own Schema.org-structured content, for both humans and agents?” and you accept its maturity: phase draft, adoption unmeasured.
- Choose Model Context Protocol when your question is “How does an AI application call tools and pull structured context, prompts, and data from an external server?” and you accept its maturity: phase living, adoption claimed (Wikipedia (OpenAI, Google DeepMind adopted MCP by March 2025) and WorkOS ('adopted by OpenAI, Google DeepMind, Microsoft, and thousands of development teams')).
Read the full articles
- NLWeb: How can a site expose a natural-language question-answering interface grounded in its own Schema.org-structured content, for both humans and agents?
- Model Context Protocol: How does an AI application call tools and pull structured context, prompts, and data from an external server?