llmwiki-query

llmwiki-query

Query a configured llmwiki-serve instance directly from a local project.

Usage

Use this command when you need wiki context for the current task and the project environment provides LLMWIKI_SERVE_URL.

Input:

$ARGUMENTS

If the input is empty, ask for a concise wiki query. If LLMWIKI_SERVE_URL is not set, ask the user to configure it. Do not guess private endpoints or commit endpoint values into the repository.

Privacy Rules

• Treat the query as disclosed to the configured server.
• Do not include secrets, tokens, private keys, credentials, customer data, or unrelated source files.
• Keep query text focused on the task.
• Do not request drafts unless the user explicitly confirms the server is trusted and draft serving is enabled.

Direct HTTP Calls

Start with /query:

curl -s "${LLMWIKI_SERVE_URL}/query" \
  -H "content-type: application/json" \
  -d "{\"query\":\"$ARGUMENTS\",\"limit\":4}"

Use /search to find candidate pages:

curl -s "${LLMWIKI_SERVE_URL}/search" \
  -H "content-type: application/json" \
  -d "{\"query\":\"$ARGUMENTS\",\"limit\":5}"

Use /read/{page_id} after a relevant page id is found. URL-encode page ids or paths before placing them in the URL.

curl -s "${LLMWIKI_SERVE_URL}/read/PAGE_ID"

Use /graph when relationships between pages, links, or sources matter:

curl -s "${LLMWIKI_SERVE_URL}/graph?limit=120"

Optional MCP-Style Call

If the client prefers tool-shaped calls, llmwiki-serve may expose POST /mcp as an experimental MCP-style JSON-RPC compatibility surface. This is a compatible surface, not a certification claim.

curl -s "${LLMWIKI_SERVE_URL}/mcp" \
  -H "content-type: application/json" \
  -d "{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/call\",\"params\":{\"name\":\"llmwiki_context\",\"arguments\":{\"query\":\"$ARGUMENTS\",\"limit\":4}}}"

Known tool names:

• llmwiki_context
• llmwiki_search
• llmwiki_read
• llmwiki_graph