Alimenter votre agent
La commande propre à l'éditeur. Ce n'est pas un endpoint PlugMCP.
Host a copy with our keys and logs.
npx -y @quillmark/[email protected]Claude Code n'a pas de lien d'installation pour une commande locale. Copiez la commande ci-dessous et exécutez-la dans un terminal.
claude mcp add quillmark-mcp -- npx -y @quillmark/mcp@0.1.0À exécuter dans un terminal.
{ "mcpServers": { "quillmark-mcp": { "command": "npx", "args": [ "-y", "@quillmark/[email protected]" ] } }}claude_desktop_config.json
URL distante ou commande sur votre machine ? Ce qui distingue les deux installations
Exécuter sur 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.
LancerDe l'éditeur
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]" ] } }}Outils
Pas encore de liste d'outils. Les serveurs distants en obtiennent une après le premier contrôle d'état.
FAQ
Copiez sur cette page la configuration stdio pour Cursor, Claude Desktop, Claude Code ou VS Code. Elle utilise l'installation de l'éditeur, pas un proxy PlugMCP.
Aucune variable d'environnement requise n'est indiquée sur cette fiche.
@quillmark/mcp s'exécute en local via stdio.
Dernière vérification : 2026-11-15. MCP integration library for Quillmark — parse → resolve → validate → MCP-envelope pipeline.