Search tools
The Extentos MCP server's search tool — searchDocs, which serves the bundled conceptual documentation corpus (getting_started, custom_handlers, voice_integration, library_api, toggles, simulator_browser_mode, event_log_schema, manifest_format, file_actions, permissions, connection_ui_placement, multi_platform_projects, and more). The narrative layer that complements the action-oriented tools.
searchDocs is the conceptual / narrative layer of the MCP tool surface. The other tools answer "what / how / where" with structured data; searchDocs carries the prose that explains the why and the idiom.
searchDocs
Search the Extentos documentation corpus by topic or keyword. Topic IDs are stable; the corpus is regenerated when the library or backend changes shape.
When to use
- To learn how the SDK is meant to be composed (
custom_handlers,voice_integration) - To read the conceptual model for a specific area (
toggles,connection_state_model,permissions) - To look up the simulator dev-loop semantics (
simulator_browser_mode,auto_bind_session_lifecycle,local_bridge_discovery) - To understand the manifest schema (
manifest_format), file-action contract (file_actions), event log layers (event_log_schema)
When NOT to use
- For the live capability list — use
getPlatformInfo - For per-feature call shape — use
getCapabilityGuide - For complete compositional patterns — use
getCodeExample - For project-installed state — use
inspectIntegration
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
topic | string | conditional | The topic ID to fetch. Pass alone to retrieve full topic content (most common). |
query | string | conditional | Keyword(s) to search. Pass alone for cross-topic search; pass with topic to narrow within a topic. |
At least one of topic or query is required — calling with neither returns invalid_arguments.
Aligned post-pivot topics
Read these to learn the current model:
getting_started— the full topic index. Read first to see what's available.custom_handlers— the canonical SDK-composition doc. How to write a Handler class that subscribes to capability primitives. The post-pivot replacement for the retiredapp_callback_guide.voice_integration— STT + TTS architecture, what the simulator routes through vs what production routes through.connection_ui_placement— five placement options (dedicated_route/settings_subscreen/bottom_tab/modal_sheet/headless) with Compose + SwiftUI snippets.host_app_scaffold— copy-pasteable empty-app template for devs who don't have an existing app yet.auto_bind_session_lifecycle— how the running app reattaches to a persistent simulator session via the MCP local bridge.local_bridge_discovery— the127.0.0.1:31337/whoamiprobe protocol.device_code_flow— account-linking lifecycle whencreateSimulatorSessionreturnsauth_required.connection_state_model— the 6GlassesStatebuckets + transitions.permissions— full Android manifest + iOS Info.plist + Meta DAT scope derivation.production_checklist— categories, what's personalized vs static.concurrency_modes— running multiple handler subscriptions concurrently, restart semantics, scope lifetime.multi_platform_projects— how project identity is derived fromappPackage, dashboard grouping, Merge action.library_api— the post-pivot SDK reference:ExtentosGlasses, the 6 sub-clients (connection / camera / audio / runtime / toggles / debug / telemetry), the Photo / Videos URI helpers, the PushToTalkSession extension.toggles— all 8 runtime toggles, their enforcement status, the canonical read / write patterns.audio_video_coexistence— A2DP / HFP profile conflict policy.simulator_browser_mode— the persistent-sim model, get-or-create semantics, iteration model.event_log_schema— every event layer + type the structured log carries.manifest_format—extentos.manifest.jsonv2 shape (post-pivot — nospecfield, nointegration.{blocks,streams,triggers,handlerNames,togglesOverridden}sub-object).file_actions— the two post-pivot file-action values (create/manual_patch) and how to apply each.connection_ui—ExtentosConnectionPagecustomization layers (drop-in / themed /@ExtentosEscapeHatch).
Retired topics
trigger_types, action_types, block_types, stream_types, spec_format, template_syntax, app_callback_guide, spec_validation_rules — all retired with the pure-SDK pivot. Calling searchDocs with these IDs returns "topic not found". The conceptual ground each covered is now in custom_handlers (for the composition layer) and library_api (for the SDK surface). Pre-pivot users searching for them should be steered to those two.
Response
{
"topic": "<id>",
"title": "<topic title>",
"content": "<full topic body, ~2-30 KB depending on topic>",
"keywords": ["..."],
"relatedTools": ["getPlatformInfo", "getCapabilityGuide", "..."]
}relatedTools steers the agent to the structured tools that complement the prose.
Related
- Discovery tools — the structured tools that pair with
searchDocs - Tools overview — back to the full tool catalog
Production tools
The Extentos MCP server's production tools — getProductionChecklist (personalized ship-readiness checklist based on declared capabilities + handler names) and getCredentialGuide (step-by-step credential setup for Anthropic, OpenAI, Google Cloud, DeepL, Azure, AWS Bedrock, HuggingFace, or custom providers). Pre-ship gates.
Auth
The Extentos auth model. All 18 MCP tools, code generation, validation, on-device simulation, and real-hardware testing work with no account. The one thing that requires sign-in is the browser simulator at extentos.com/s — once linked, sessions are unlimited. Sign-in flows through the OAuth 2.0 device-code pattern (RFC 8628) so it works in any environment, including headless CI and remote shells. The completeAuthLink MCP tool polls the backend after createSimulatorSession returns auth_required, persists the token to ~/.extentos/auth.json, and the original tool call retries automatically. No manual token paste, no payment.