Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @quillmark/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add quillmark-mcp -- npx -y @quillmark/mcp@0.1.0Ejecútalo en una terminal.
{ "mcpServers": { "quillmark-mcp": { "command": "npx", "args": [ "-y", "@quillmark/[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
MCP integration library for Quillmark. Surfaces Quillmark's parse → resolve → validate → render pipeline as three Model Context Protocol tools that any MCP client can call.
This library is transport-agnostic: it owns the tool contracts but leaves stdio/HTTP/SSE wiring and artifact delivery to the consumer. For a turnkey HTTP server using these tools, see .
MCP integration library for Quillmark — parse → resolve → validate → MCP-envelope pipeline.
npm install @quillmark/mcp @modelcontextprotocol/sdk @quillmark/quiver @quillmark/wasm zod
Requires Node ≥ 24.
list_quills — discover available Quill formats. Returns { quills: [{ name, description }] }.get_specs — get the schema for one Quill. Returns { schema }, TOON-encoded for token-efficient LLM consumption. Includes a bundled example document when the Quill declares example_file:.create_document — render a document from YAML frontmatter + markdown. Returns { status, url?, errors? } (the success shape is whatever the consumer's Deliverer returns).import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { Quiver } from "@quillmark/quiver/node";
import { Quillmark } from "@quillmark/wasm";
import { registerQuillmarkTools, type Deliverer } from "@quillmark/mcp";
const quiver = await Quiver.fromDir("./quills");
const engine = new Quillmark();
const deliver: Deliverer = async ({ render, canonicalRef }) => {
const [artifact] = render();
// upload artifact.bytes somewhere, return a URL...
return { status: "success", url: `https://example.com/${canonicalRef}.pdf` };
};
const mcpServer = new McpServer({ name: "my-quillmark", version: "1.0.0" });
registerQuillmarkTools(mcpServer, { quiver, engine, deliver });
// connect mcpServer to your transport of choice
The library exports the three tool primitives directly (listQuills, getSpecs, createDocument) for consumers that want to call them without going through MCP.
Apache-2.0
MCP integration library for Quillmark — parse → resolve → validate → MCP-envelope pipeline.
{ "mcpServers": { "quillmark-mcp": { "command": "npx", "args": [ "-y", "@quillmark/[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
@quillmark/mcp se ejecuta localmente por stdio.
Última comprobación: 2026-11-14. MCP integration library for Quillmark — parse → resolve → validate → MCP-envelope pipeline.