Labsco
MCP SERVER

o3 Search

by yoshiko-pg

Put a web-searching model behind one tool call, so a client with no search integration can still answer questions about things that happened after training.

Web Search EnginesVerified
Summary
The searching happens behind the key instead of inside your transcript.

One tool, one input string: the fetching and reading that a question needs happen on the other side of the API key rather than as a chain of page loads filling your context. That is also the whole configuration surface — no result count, no site filter, no freshness window — so the question you write is the only lever you have.

What it is

A single-tool bridge to a web-searching model, called with a plain-language question.

What you get
  • A natural-language question answered by a model that searches the web, in one call
  • Current information for topics your own model has no training data for
  • Error messages and stack traces researched without leaving the session
  • A design question or half-formed idea talked through in the same call shape as a lookup
Requirements

An OpenAI API key in OPENAI_API_KEY, and a Node runtime.

Setup effort

One command plus a key — npx o3-search-mcp, then supply credentials