Tools reference
The Extentos MCP server exposes 18 deterministic tools across 7 categories — discovery, generation, guidance, validation, simulation, production, and documentation. Per-tool reference covering input parameters, response shapes, when to call each tool, and worked examples. Verified from the actual tool definitions and handler implementations in @extentos/mcp-server.
The MCP server exposes 18 deterministic tools an AI agent calls to operate Extentos. Each tool is a typed primitive — clear input schema, predictable response shape, no hidden state. The agent composes them itself; there's no planning tool.
Tools are organized by purpose:
| Category | Tools | What they're for |
|---|---|---|
| Discovery and Planning | getPlatformInfo, getExampleSpec | First calls in any new task — read the catalog, study reference specs |
| Setup and Generation | generateConnectionModule, initSpec, generateConsumer, updateSpec | Scaffold the project and mutate the AppSpec |
| Implementation Guidance | getVoiceCommandGuidance, getPermissions | Side-quest helpers during composition |
| Validation | validateSpec, inspectIntegration, validateIntegration | Correctness gates — run after every mutation |
| Simulation | createSimulatorSession, completeAuthLink, getEventLog, getSimulatorStatus | Provision and operate browser-mode simulator sessions |
| Production | getProductionChecklist, getCredentialGuide | Pre-ship checks |
| Search | searchDocs | Search the Extentos documentation by topic |
Conventions
A few conventions hold across every tool:
- All tool inputs and outputs are JSON. Tools that take an object pass it via the MCP
argumentsfield; the schemas live inmcp-server/src/tools/definitions.ts. additionalProperties: false. Unknown parameters fail validation withcode: "invalid_arguments"and afixHinttelling the agent what to drop.- Successful responses include a
summarystring — a short human-readable description of what the tool returned. Agents can surface this directly to the developer. - Errors return a structured shape —
{ code, message, fixHint?, retryable? }— instead of throwing. The agent can decide whether to retry or surface the error. - Freshness tokens guard concurrent edits. Tools that mutate the spec (
updateSpec,generateConsumer) require abasedOn: { hash, timestamp }token frominspectIntegration. Stale tokens fail fast — no silent overwrites of concurrent agent edits. - Tool calls do not count against the simulator-event meter. The 1000-event meter only counts
BrowserSimTransportruntime events during a simulator session. MCP-server-side activity is always free.
The canonical agent-driven flow
For a fresh project, the typical tool sequence is:
getPlatformInfo → searchDocs → generateConnectionModule → initSpec
→ generateConsumer → validateIntegration → createSimulatorSession
→ (developer interacts) → getEventLogFor iteration: inspectIntegration (for the basedOn token) → updateSpec → generateConsumer (if handlers/streams added) → validateIntegration.
Before shipping: getProductionChecklist → getCredentialGuide.
Per-category reference
The deep reference per tool lives on the category pages:
- Discovery and Planning →
- Setup and Generation →
- Implementation Guidance →
- Validation →
- Simulation →
- Production →
- Search →
Source of truth
Every claim on these pages is verified from mcp-server/src/tools/definitions.ts (input JSON Schemas), mcp-server/src/tools/registry.ts (handler wiring), and the per-tool handler implementations under mcp-server/src/tools/handlers/. If a doc claim conflicts with the source, the source wins — file an issue and we'll reconcile.
Configuration
Configure the Extentos MCP server — environment variables, project directory detection, default vendor.
Discovery and Planning tools
The Extentos MCP server's discovery tools — getPlatformInfo (returns the static platform catalog of vendor capabilities, library version, and spec schema) and getExampleSpec (retrieves one of 8 canonical reference patterns for studying complex spec compositions). These are the first calls an AI agent makes in any new task — cheap, all local, no side effects, no meter cost.