search_docs

Find documentation pages by keyword or phrase across all projects — use this when you don't already know the exact project, section, and page. Hybrid lexical ranking (full-text + BM25 + trigram) returns the best-matching pages first, each with a snippet (matched terms wrapped in bold) and per-page metadata. Structured results carry project, section, page, title, score, snippet, stability (stable or unstable), and markdownLink, plus summary, mtime, sha, and buildHash when available. buildHash is the corpus provenance stamp — cite it alongside any claim derived from these results. A plain-text fallback lists the same hits. Use get_page to fetch a page once you know its project, section, and page; use list_projects to enumerate available projects.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Natural-language or keyword query (minimum 2 non-whitespace characters). Examples: \"linear types\", \"deploy install\", \"kli init\". Stopword-only or pure-negation queries return no results."
    }
  },
  "required": [
    "query"
  ]
}

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_docs",
    "arguments": {
      "query": "linear types"
    }
  }
}

Applicable Error Codes

Back to MCP Server