pdf-card-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_pdf_to_card_htmlA | Convert a local PDF into a portable, source-linked HTML reader. The generated reader is static HTML with embedded assets. It keeps source text intact, includes source-page previews for verification, and crops detected tables, figures, and display formulas as images. Optional MCP sampling is limited to validated style-token choices or boundary-only card polish; raw CSS and source-text rewrites are rejected. |
| validate_reader_annotationsB | Validate a notes/highlights sidecar against a generated reader HTML file. |
| publish_reader_bundleB | Publish a static reader bundle with selected notes and highlights. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: conversion, publishing, and validation. No overlap between them.
All tools follow snake_case verb_noun pattern consistently (convert_pdf_to_card_html, publish_reader_bundle, validate_reader_annotations).
Three tools is appropriate for the focused domain of PDF-to-card HTML conversion and management.
Covers core workflow (create, publish, validate) but lacks operations for updating or deleting bundles/annotations.