Skip to content

docs: remove web search and the MCP server - #100

Merged
crstian19 merged 1 commit into
mainfrom
chore/remove-public-web-search
Sep 25, 2026
Merged

crstian19 merged 1 commit into
mainfrom
chore/remove-public-web-search

Conversation

@crstian19

Copy link
Copy Markdown
Contributor

Why

NaN is retiring its web search (POST /v1/search on api.nan.builders) and the remote MCP server. The MCP server's only tool was web_search.

What

  • Deleted docs/mcp (en + es). The sidebar order and the API reference entry are renumbered. src/middleware.ts sends a 301 from /docs/mcp and /es/docs/mcp to agent-setup.
  • src/data/openapi.json: removed the /search and /mcp paths, their tags and their schemas, the web-search budget sentence, and the search_unavailable error row.
  • Content pages (en + es): removed the web search and MCP sections or links from examples, agent-setup, agents, claude-code, gentle-ai, intro and getting-started.
  • Tests: updated for the removed routes and anchors, plus redirect tests.

Test

npm run build passes, npm test passes 1290 tests, and npm run check reports 0 errors.

NaN is decommissioning its web search: POST /v1/search and the remote MCP
server at /mcp, whose only tool was web_search. Drop every trace of both
from the site.

- Delete the MCP server page (en + es) and 301 /docs/mcp and /es/docs/mcp
  to the agent setup page that linked to it.
- Remove /search and /mcp from the OpenAPI spec, with their Search and MCP
  tags, the four schemas only they used, the web search budget and the
  search_unavailable 503 row.
- Remove the web search snippets from Examples and the links, cards and
  callouts in agent-setup, agents, claude-code, gentle-ai, getting-started
  and intro, in both languages.
- Close the gap the page left in the docs order.
@crstian19
crstian19 merged commit e634763 into main Sep 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants