multi-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@multi-mcp Scrape https://books.toscrape.com and extract book titles and prices into a table."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
multi-mcp
Servidor MCP multi-propósito para opencode. Provee utilidades de texto/hash/tiempo y un scraper web profesional (scrape-dom).
Incluye un CLI instalador (multi-mcp-setup) que configura el MCP server y el plugin de slash commands en opencode desde cero, sin corromper la config existente ni chocar con otros servers/plugins.
Requisitos
Node.js ≥ 22
npm
Related MCP server: agent-utils-mcp
Quick Start
1. Instala el paquete
npm install -g multi-mcp
# o para desarrollo local:
# npm link # dentro del repo2. Configura opencode
multi-mcp-setup installEl comando:
Copia el plugin y sus slash commands a
~/.config/opencode/plugins/Registra el MCP server
multi-mcpen~/.config/opencode/opencode.jsonPreserva comentarios, orden y el resto de claves de tu config (edición quirúrgica JSONC)
Es idempotente: re-ejecutarlo no duplica nada
Detecta conflictos: si
mcp.multi-mcpapunta a otro server, aborta sin pisarlo
3. Reinicia opencode
Tras instalar, reinicia opencode. Tendrás las tools multi-mcp_* y los slash commands /multi-mcp-scrape, /multi-mcp-scrape-dom, /multi-mcp-dom, /multi-mcp-list-tools.
Verificar y desinstalar
multi-mcp-setup status # estado actual
multi-mcp-setup install --dry-run # previsualizar cambios sin escribir
multi-mcp-setup uninstall # quita solo lo nuestroWindows: usa
npm install -g multi-mcponpx multi-mcp-setup installen vez de ejecutarbin/cli.jsdirectamente. npm genera los wrappers.cmd/.ps1automáticamente.
Configuración manual (sin CLI)
Alternativa al Quick Start: registra el servidor en ~/.config/opencode/opencode.json como MCP local apuntando al bundle compilado:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
// ...otros servers...
"multi-mcp": {
"type": "local",
"command": ["node", "/root/.config/opencode/mcp/multi-mcp/build/server.mjs"],
"enabled": true
}
}
}Ajusta la ruta a donde tengas este repo. Tras editar el código del server:
npm run typecheck && npm run buildy reinicia opencode para que cargue las tools nuevas.
Tools
Tool | Descripción |
| Devuelve el texto de entrada |
| Fecha/hora actual (zona IANA opcional) |
| Evalúa expresiones aritméticas |
| Hash sha256/sha1/md5 |
| Codifica/decodifica base64 |
| Genera UUIDs |
| Lista todas las tools con descripciones |
| Fetch de URL con bypass Cloudflare, retries y metadata. Devuelve HTML crudo |
| Parsea HTML dado con jsdom y ejecuta operaciones (query, queryAll, attr, text, tables, forms, links...) |
| Scraper profesional: fetch + parse jsdom + extract DSL + operations + paginación |
scrape-dom — scraper profesional
Combina fetch (con bypass Cloudflare) + parseo jsdom + extracción estructurada, en una sola llamada.
Parámetros comunes
Parámetro | Tipo | Default | Descripción |
| string (URL) | — | Página a scrapear |
| GET/POST/HEAD |
| Método HTTP |
| int (1000–120000) |
| Timeout en ms |
| int (0–10) |
| Reintentos |
| object | — | Headers HTTP custom |
| array | — | Pipeline de operaciones DOM de bajo nivel |
| object | — | DSL de extracción estructurada |
| object | — | Seguir enlaces "next" y acumular resultados |
Modo 1: extract (DSL estructurado)
Ideal para scrapear listas/items repetidos o campos concretos de una página.
scrape-dom({
url: "https://example.com/list",
extract: {
itemSelector: ".card", // cada item repetido (omitir ⇒ campos leídos de la página completa)
include: ".card:not(.sold-out)", // filtro: solo items que matchean
exclude: ".ad", // filtro: descarta items que matchean
fields: [
{ key: "title", selector: "h2", transform: ["trim", "collapse"] },
{ key: "price", selector: ".price", type: "int" },
{ key: "link", selector: "a", attr: "href", resolveUrl: true },
{ key: "desc", selector: "p", optional: true },
{ key: "id", selector: ".id", default: "unknown" }
]
}
})Campo del DSL:
Campo | Descripción |
| Clave de salida |
| Selector CSS del campo (dentro del item, o de la página si no hay |
| Atributo a leer en vez del texto ( |
| Coercionar: |
| Array en orden: |
| Resolver URLs relativas contra la base de la página (con |
| Valor si el campo falta |
| Si |
Resultado (modo itemSelector): { items, count, skippedInvalid?, pagesFetched }.
Resultado (sin itemSelector): { items, count, singleItem, pagesFetched }.
Modo 2: operations (pipeline de bajo nivel)
Operaciones planas sobre todo el documento, estilo dom pero tras scrapear la URL.
scrape-dom({
url: "https://example.com",
operations: [
{ type: "title" },
{ type: "queryAll", selector: "li a" },
{ type: "tables" }
]
})Tipos de operación: title, meta, query, queryAll, attr, text, html, links, images, tables, forms, scripts, styles, custom (con scriptSelector + all).
Paginación multi-página
scrape-dom({
url: "https://example.com/news?page=1",
extract: { itemSelector: "article", fields: [{ key: "title", selector: "h2" }] },
pagination: {
nextSelector: "a.next", // selector del enlace "next"
attr: "href", // atributo con la URL (default href)
maxPages: 5 // máx páginas (1-20, default 3)
}
})Acumula los items de todas las páginas en items y lista las URLs visitadas en pagesFetched. Evita loops detectando URLs repetidas.
scrape / dom (componentes)
scrape({ url, method?, timeout?, retries?, metadata?, headers? })→ HTML crudo, conmetadata: truedevuelve status/headers/size/tiempo.dom({ html, operations? })→ parsea HTML dado con jsdom y ejecuta las mismas operaciones que el modo 2 descrape-dom.
Build
npm run build # tsup → build/server.mjs (server MCP)
npm run build:plugin # tsup → install/plugin/multi-mcp.mjs + command/*.md
npm run build:cli # tsup → bin/cli.js (instalador con shebang)
npm run build:all # los tres
npm run dev # npx tsx src/server.ts (sin build, desde fuente)
npm run typecheck # tsc --noEmit
npm run start # node build/server.mjsBun: compilar a binario con
bun build --compileno funciona — css-tree (dep de jsdom) carga../data/patch.jsoncon unrequiredinámico que el bun compile no empaqueta (Cannot find module '../data/patch.json'). Usarnpm run build(tsup).
Available Tools
10 toolsbase64B
Encode or decode base64 strings
Inputs: text (required), action (required).
domB
Parse HTML with jsdom and execute DOM operations (query, attr, text, html, links, images, tables, forms, etc.).
Inputs: html (required), operations.
echoA
Echo back the input text
Inputs: text (required).
hashC
Generate a hash of the input text using various algorithms
Inputs: text (required), algorithm.
list-toolsA
List all available tools with descriptions and usage examples
Inputs: no named parameters.
mathA
Evaluate a math expression (add, subtract, multiply, divide, parentheses)
Inputs: expression (required).
scrapeA
Fetch a URL with Cloudflare bypass, retries, and optional metadata. Returns raw HTML.
Inputs: url (required), method, headers, retries, +2 more.
scrape-domA
Scrape a URL, parse with jsdom, and extract data via structured DSL or low-level operations. Supports pagination.
Inputs: url (required), method, extract, headers, +4 more.
timestampA
Get the current date and time
Inputs: timezone.
uuidB
Generate one or more UUIDs
Inputs: count.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
The utility tools are clearly distinct, but scrape, scrape-dom, and dom overlap in fetching URLs and working with HTML/DOMs, so an agent could select the wrong one. Descriptions clarify raw HTML vs structured extraction vs in-memory DOM operations, but the boundaries are not immediately obvious from names alone.
All names are lowercase, but the set mixes single-word nouns (timestamp, math, uuid), single-word verbs (echo, scrape), and hyphenated verb-noun names (list-tools, scrape-dom). The naming is readable and predictable in tone, but not structurally consistent.
Ten tools is within a reasonable scope for a multi-purpose server, and each tool has a defined function. The utility side adds some trivial tools, but the overall count is not excessive or too thin.
The utility side covers common helper operations, and the scraping side provides raw fetch, structured extraction, and DOM manipulation with pagination support. There are minor gaps like limited HTTP request customization, but no critical dead ends for the apparent purpose.
Maintenance
Related MCP Connectors
Deterministic web intake and data utilities for autonomous agents.
Unified 15-tool SEO, SERP, clean Markdown & GEO (LLM citation Share-of-Voice) MCP server.
All public upAPI operations as MCP tools: web scraping, search, screenshots, PDF, OCR and more.
MCP tools: timestamps, UUID v4, gas prices, domain WHOIS, text extraction, and persistent memory.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides advanced web scraping with HTTP client, smart content extraction to Markdown, browser automation via Playwright, screenshot/PDF generation, and Docker sandbox execution environments.1MIT
- FlicenseAqualityCmaintenanceSwiss-army-knife utility MCP server for AI agents. 18 tools for JSON validation/formatting, base64 encode/decode, hash generation, UUID generation, URL parsing, regex testing, markdown↔HTML conversion, text stats, slug generation, datetime conversion, cron parsing, text diffing, CSV↔JSON conversion, and JWT decoding. Zero API Key required185-
- AlicenseNot gradedqualityDmaintenanceOpen-source web scraper and extraction MCP server with JavaScript rendering, markdown output, PDF/DOCX parsing, structured errors, and validated extraction contract diagnostics for agents.2AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceProvides a wide range of tools including math, image processing, filesystem, git, text utilities, network, date/time, security, and browser console capture. Designed as a clean, modular foundation for building MCP servers with comprehensive error handling and testing.1-