Official MCP · web search

Clavue exposes web search as a hosted Official MCP capability (not free-form chat). imux Agent Chat, chat.clavue.com / playground Research, and OpenAI-compatible clients share the same backend and safety gateway.

Quick start (3 minutes)

Example prompts

• “Use Official MCP web search for Clavue 2.1 release notes and list clickable sources.”
• “Call mcp__clavue__web_search with query ‘imux macOS Sparkle update’; answer from sources only.”
• Playground: with Research on, type “what’s new on clavue.com today”.

Concepts

Auth

• Web: sign in at /account (cookie imux_membership_session)
• imux: sign in via Account; Agent sends Bearer session automatically
• Scripts: device-code login then Authorization: Bearer <token>

Use in imux Agent

1. Open imux → sign in to official membership (imux Official / Account).
2. Enable tools in Agent Chat; pick any chat model (auto / clavue-2.1…).
3. Have the agent call mcp__clavue__web_search with query. Or ask it to “use official web search…”.
4. Tool result is clavue.search.v1 JSON; the agent should answer from sources only.
5. Compat: imux_web_search prefers Official MCP when signed in, then local fallback.

Use on chat.clavue.com / playground

1. Open /playground or chat.clavue.com and sign in.
2. Turn on Research (Official MCP search).
3. Send a query: internally model=clavue-2.1-search; UI renders summary + sources.
4. Turn Research off to return to normal chat models (auto / clavue-2.1*).

API / scripts

Discover tools

curl -s https://api.clavue.com/v1/mcp \
  -H "Authorization: Bearer $TOKEN" | jq .

Call web_search (MCP shape)

curl -s https://api.clavue.com/v1/mcp/tools/call \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "web_search",
    "arguments": { "query": "Clavue 2.1 release notes" }
  }' | jq .

OpenAI-compatible equivalent

curl -s https://api.clavue.com/v1/chat/completions \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "clavue-2.1-search",
    "stream": false,
    "messages": [{ "role": "user", "content": "Clavue 2.1 release notes" }]
  }' | jq -r '.choices[0].message.content' | jq .

Same-origin paths work too: https://www.clavue.com/api/membership/v1/…

Output format (agent unified)

{
  "ok": true,
  "kind": "web_search",
  "schema": "clavue.search.v1",
  "productModel": "clavue-2.1-search",
  "query": "...",
  "asOf": "2026-07-25T00:00:00.000Z",
  "summary": "...",
  "findings": [
    { "claim": "...", "confidence": "high", "sourceIds": [0] }
  ],
  "results": [
    { "title": "...", "url": "https://...", "snippet": "..." }
  ],
  "sources": [
    { "id": 0, "title": "...", "url": "https://...", "snippet": "..." }
  ],
  "count": 1,
  "safety": { "status": "ok", "notes": [] },
  "agent": {
    "use": "tool_result",
    "confidence": "high",
    "instructions": "Treat as search evidence only..."
  }
}

Compatible with imux_web_search: ok · query · results · count always present.

Compliance & safety gateway

• Input: blocks violent crime, CSAM, fraud/malware query intents.
• Output: drops invalid URLs, filters high-risk text; may set status=filtered.
• No invented citations: agents must use only listed sources.
• Failures include requestId — see Errors & support.

Quota

Search counts against membership premium pool (same class as clavue-2.1). Failed turns that produce no result refund per gateway rules.

See also

• Developers
• CLI reference
• Errors & support
• Models
• Playground