Microtoll Engine

io.github.microtollPublished by GitHub account microtollv0.1.3Updated Oct 24, 2026

Microtoll Engine in your coding tool: docs search and a scaffold for end-to-end-encrypted apps.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local stdio MCP server that gives coding assistants Microtoll Engine documentation search, page reading, and a scaffold for end-to-end-encrypted apps.

What you can do
Search the bundled Microtoll documentation full-text and get page, section and excerpt results, with an optional result limit. Read a single documentation page as Markdown by its path or from llms.txt. Scaffold a notes starter project into an empty directory, filling in namespace, origin and name, and return the next steps as text. Documentation tools only read; the scaffold only adds files and never overwrites or deletes.
When to use it
Useful when wiring Microtoll Engine into a project inside Claude Code, Cursor or another MCP host and you want the engine's docs and a starter project available without leaving the editor or fetching anything online.
Requirements
Runs locally as a stdio process via npx from the npm package @microtoll/mcp. Needs Node 24 or later. No authentication, environment variables or headers are declared, and the tools do not use the network.
Before you install
The scaffold writes files into a directory you name; it refuses non-empty directories and never overwrites, but check the target path before calling it. The install and compose commands it returns are for you to run yourself.

Installation

In SourceWeft

  1. Open Microtoll Engine in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@microtoll/mcp

Microtoll Engine inside your coding tool. A Model Context Protocol server (over standard input and output) that Claude Code, Cursor and any MCP host can call for the engine's documentation and for a project scaffold, so an agent can wire the engine in without leaving the editor — and without leaving the machine: the pages are inside the package, nothing is fetched, nothing runs but what is in src/.

Status: published as @microtoll/mcp on npm and listed in the MCP registry as io.github.microtoll/mcp. Apache-2.0. Zero dependencies. Node 24 or later.

Add it to a host

sh
claude mcp add microtoll -- npx -y @microtoll/mcp

Any other host takes the same command (npx -y @microtoll/mcp) as a stdio server.

The three tools

ToolWhat it does
microtoll_search_docs({ query, limit? })Full-text search over the documentation — the same pages as microtoll.dev, shipped in generated/docs.json by the repository's docs build so they never drift. Returns page, section and excerpt.
microtoll_read_doc({ path })One page as Markdown, by the path a search result gives (packages/access.html) or from llms.txt.
microtoll_scaffold({ directory, namespace?, origin?, name? })Writes the notes starter into an empty directory: notes.js, page.js, index.html, docker-compose.yml, nginx.conf, package.json, README.md, with the namespace and origin filled in. Writes files and nothing else; refuses a directory that is not empty; never overwrites. The next steps (npm install, docker compose up) come back as text for the person to run.

Each tool also carries a plain title and the specification's behaviour hints (annotations), which a host may use to decide when to ask the person first. The two documentation tools only read; the scaffold writes files but only adds them (it never deletes or overwrites), and a second call with the same arguments changes nothing; none of the three uses the network.

What it speaks

JSON-RPC 2.0, one message per line: initialize (protocol version 2025-06-18, tools capability), ping, tools/list, tools/call; notifications are acknowledged by silence; a tool's failure is a tool result with isError, a protocol failure a JSON-RPC error. About 120 lines in src/protocol.js, tested against a transcript of what a host sends.

Tests

npm test: the protocol over a real child process, the search and the page reader over the shipped snapshot, the scaffold into a temporary directory (placeholders filled, a non-empty directory refused), and each tool's title and behaviour hints against what the tool does.

Source: packages/mcp/README.md at commit 25d597b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.3LatestOct 6, 2026
  2. v0.1.1Sep 27, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.