mcp-pandoc-ts: A Document Conversion MCP Server (TypeScript/Host Service Version)

Created By
mystique920a year ago
MCP-Server that can control pandoc on host from docker environment using a local pandoc host service
Overview

What is mcp-pandoc-ts?

mcp-pandoc-ts is a TypeScript-based MCP server that facilitates document conversion using the pandoc tool from a Docker environment, allowing users to convert documents between various formats such as Markdown, HTML, PDF, DOCX, and TXT.

How to use mcp-pandoc-ts?

To use mcp-pandoc-ts, set up the pandoc-host-service on your host machine, configure the PANDOC_HOST_URL, and run the mcp-pandoc-ts server in a container. You can then send conversion requests to the server.

Key features of mcp-pandoc-ts?

  • Converts documents between multiple formats using pandoc.
  • Runs in a Docker container while leveraging a host service for pandoc execution.
  • Supports various input and output formats, including Markdown, HTML, PDF, and DOCX.

Use cases of mcp-pandoc-ts?

  1. Converting Markdown documents to PDF for printing.
  2. Transforming HTML content into DOCX for word processing.
  3. Automating document format conversions in a CI/CD pipeline.

FAQ from mcp-pandoc-ts?

  • What formats does mcp-pandoc-ts support?

It supports Markdown, HTML, PDF, DOCX, and TXT formats, with LaTeX and EPUB being untested.

  • Do I need to install pandoc on the container?

No, pandoc must be installed on the host machine, and the container communicates with it via the host service.

  • Is there a way to run the service in the background?

Yes, you can use tools like nohup, screen, or tmux to run the host service in the background.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mystique920
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago