PDFSpark

Server Details

Free HTML/URL to PDF conversion API. Convert HTML content or any URL to high-quality PDF documents. No API keys required.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Last Tested: 2026-09-06 15:46
Transport: Streamable HTTP
URL

Available Tools

5 tools

html_to_pdfBInspect

Convert HTML content to a PDF document

ParametersJSON Schema

Name	Required	Description
`html`	Yes	HTML content to convert to PDF
`scale`	No	Scale factor 0.1-2
`format`	No	Paper format (default: A4)
`margin`	No	Page margins in CSS units
`outline`	No	Auto-generate PDF outline/bookmarks from HTML headings (h1-h6 hierarchy)
`metadata`	No	PDF document metadata (title, author, subject, keywords)
`password`	No	Password-protect the PDF with AES-256 or RC4 encryption
`landscape`	No	Landscape orientation
`watermark`	No	Add diagonal text watermark on every page
`printBackground`	No	Print background graphics
`emulateMediaType`	No	CSS media type emulation: "print" for clean PDFs, "screen" for screen styles

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only restates the conversion action and provides no information about return format, external resource handling, permission requirements, or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no filler or redundant information. It is appropriately sized for its purpose and front-loads the core action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a rich input schema, the description omits return value behavior and usage context. Since no output schema exists, the description should have explained what the tool returns or what side effects occur. A one-line description is insufficient for an 11-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 11 parameters. The description adds no parameter-level meaning, but per the rubric baseline this is acceptable when the schema is comprehensive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Convert') and resource ('HTML content') to clearly state the tool's function. It also distinguishes itself from sibling tools like url_to_pdf (which handles URLs) and merge_pdfs/split_pdf (which manipulate existing PDFs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives. The sibling tool url_to_pdf exists for URL-based conversion, but the description does not mention it or any conditions that would make html_to_pdf the preferred choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

merge_pdfsBInspect

Merge multiple PDF documents into a single PDF

ParametersJSON Schema

Name	Required	Description	Default
`pdfs`	Yes	Array of base64-encoded PDF strings to merge (2-100 PDFs)

TDQS

B3.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the full burden. It only restates the core function and does not disclose whether input PDFs are modified, the output format, base64 handling, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundancy or filler, making it maximally concise while conveying the essential purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although the schema covers the input fully, there is no output schema and the description does not explain the return value, possible errors, or side effects. The description alone is incomplete for a tool that produces a new PDF.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'pdfs' is fully described in the schema (array, base64-encoded, min/max items), and the tool description adds no additional meaning. With high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'merge' applied to 'multiple PDF documents' and the outcome 'a single PDF', which is specific and distinguishes it from sibling tools like split_pdf and pdf_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use case (combining PDFs) but does not explicitly state when to use it over alternatives or mention exclusions or prerequisites. There is no guidance on when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

pdf_infoAInspect

Extract metadata, page count, and page dimensions from a PDF document

ParametersJSON Schema

Name	Required	Description	Default
`pdf`	Yes	Base64-encoded PDF string

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'extract' implies a read-only operation, but the description does not disclose the return format, handling of invalid/corrupted PDFs, or whether password-protected files are supported. It is adequate for a simple read tool but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One concise sentence with no filler, front-loaded with the action and outcome. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description lists exactly what will be extracted (metadata, page count, page dimensions), which covers the expected return values. It does not specify the response structure or error conditions, but given the tool's low complexity and single parameter, the description is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides 100% coverage for the single parameter 'pdf' (Base64-encoded PDF string), so the description adds no extra parameter meaning. This matches the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool extracts metadata, page count, and page dimensions from a PDF. This specific verb and resource distinguish it from sibling tools like html_to_pdf, merge_pdfs, split_pdf, and url_to_pdf, which all perform different operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context implies it should be used when you need information about a PDF, but it does not explicitly state when not to use it or name alternatives. Since none of the sibling tools serve a similar info-extraction purpose, the usage context is clear without explicit exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

split_pdfAInspect

Extract specific pages from a PDF document

ParametersJSON Schema

Name	Required	Description	Default
`pdf`	Yes	Base64-encoded PDF string
`pages`	Yes	Page range to extract (e.g. "1-3,5,8-10")

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full responsibility for disclosing behavior. It only states 'extract', without mentioning whether the operation is non-destructive, what the output format is (e.g., base64 PDF), or any edge cases. The lack of behavioral detail is a significant gap for a tool that likely returns a new PDF.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is concise and easily parsed, effectively conveying the tool's core function without verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with only two well-documented parameters, but with no output schema and no annotations, the description should ideally note return values or behavior. It covers the purpose but lacks completeness regarding output format, which is a notable omission for an agent to correctly use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema description coverage is 100%, with both 'pdf' and 'pages' clearly described. The tool description adds little beyond echoing 'specific pages', so the baseline of 3 is appropriate since the schema already provides the necessary parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Extract specific pages from a PDF document' uses a specific verb ('extract') and resource ('specific pages from a PDF'), clearly distinguishing it from siblings like merge_pdfs, html_to_pdf, and pdf_info. The action and scope are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for extracting specific PDF pages, but it does not explicitly state when to prefer this over alternatives or mention any exclusions. There is no guidance on use cases or non-use cases, leaving room for ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

url_to_pdfCInspect

Convert a webpage URL to a PDF document

ParametersJSON Schema

Name	Required	Description
`url`	Yes	URL of the webpage to convert to PDF
`scale`	No	Scale factor 0.1-2
`format`	No	Paper format (default: A4)
`margin`	No	Page margins in CSS units
`outline`	No	Auto-generate PDF outline/bookmarks from HTML headings (h1-h6 hierarchy)
`metadata`	No	PDF document metadata (title, author, subject, keywords)
`password`	No	Password-protect the PDF with AES-256 or RC4 encryption
`landscape`	No	Landscape orientation
`watermark`	No	Add diagonal text watermark on every page
`printBackground`	No	Print background graphics
`emulateMediaType`	No	CSS media type emulation: "print" for clean PDFs, "screen" for screen styles

TDQS

C2.7/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'Convert' without revealing how the conversion happens, whether network access is required, how JavaScript is handled, or any side effects. This is minimally informative.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded with the core function. It avoids unnecessary words, but its extreme brevity means it provides no structural context for the tool's many options.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 11 parameters, nested objects, and no output schema or annotations, the description is severely incomplete. It does not explain what the returned PDF looks like, how to handle the output, or any of the advanced capabilities (format, margins, encryption, watermark). While the schema covers parameters, the description lacks high-level context needed for an agent to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema fully documents all 11 parameters, including nested objects like margin and watermark. The description adds no additional meaning beyond the schema, matching the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb 'Convert' and identifies the resource ('a webpage URL') and output ('a PDF document'). It is specific enough to understand the tool's core function, though it does not explicitly distinguish from the sibling tool html_to_pdf.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like html_to_pdf. It does not state any prerequisites, exclusions, or preferred contexts, leaving the agent to infer usage solely from the tool's name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesMar 18, 2026

Changedhtml_to_pdf1 field changed

addedInput schema / properties / outline

Added value: +{
+  "description": "Auto-generate PDF outline/bookmarks from HTML headings (h1-h6 hierarchy)",
+  "type": "boolean"
+}

Changedurl_to_pdf1 field changed

addedInput schema / properties / outline

Added value: +{
+  "description": "Auto-generate PDF outline/bookmarks from HTML headings (h1-h6 hierarchy)",
+  "type": "boolean"
+}

1 tool updateMar 15, 2026
- Addedpdf_info

1 tool updateMar 14, 2026

Changedmerge_pdfs2 fields changed

changedInput schema / properties / pdfs / description

Previous value: -"Array of base64-encoded PDF strings to merge (2-20 PDFs)"New value: +"Array of base64-encoded PDF strings to merge (2-100 PDFs)"

changedInput schema / properties / pdfs / maxItems
```
Previous value: -20New value: +100
```

2 tool updatesMar 13, 2026

Changedhtml_to_pdf1 field changed

addedInput schema / properties / password

Added value: +{
+  "additionalProperties": false,
+  "description": "Password-protect the PDF with AES-256 or RC4 encryption",
+  "properties": {
+    "algorithm": {
+      "description": "Encryption algorithm (default: AES-256)",
+      "enum": [
+        "AES-256",
+        "RC4"
+      ],
+      "type": "string"
+    },
+    "ownerPassword": {
+      "description": "Password for managing permissions (defaults to userPassword)",
+      "maxLength": 128,
+      "type": "string"
+    },
+    "permissions": {
+      "additionalProperties": false,
+      "description": "Granular PDF permissions",
+      "properties": {
+        "copying": {
+          "description": "Allow copying text (default: true)",
+          "type": "boolean"
+        },
+        "modifying": {
+          "description": "Allow modifying (default: true)",
+          "type": "boolean"
+        },
+        "printing": {
+          "description": "Allow printing (default: true)",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "userPassword": {
+      "description": "Password required to open the PDF",
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "userPassword"
+  ],
+  "type": "object"
+}

Changedurl_to_pdf1 field changed

addedInput schema / properties / password

Added value: +{
+  "additionalProperties": false,
+  "description": "Password-protect the PDF with AES-256 or RC4 encryption",
+  "properties": {
+    "algorithm": {
+      "description": "Encryption algorithm (default: AES-256)",
+      "enum": [
+        "AES-256",
+        "RC4"
+      ],
+      "type": "string"
+    },
+    "ownerPassword": {
+      "description": "Password for managing permissions (defaults to userPassword)",
+      "maxLength": 128,
+      "type": "string"
+    },
+    "permissions": {
+      "additionalProperties": false,
+      "description": "Granular PDF permissions",
+      "properties": {
+        "copying": {
+          "description": "Allow copying text (default: true)",
+          "type": "boolean"
+        },
+        "modifying": {
+          "description": "Allow modifying (default: true)",
+          "type": "boolean"
+        },
+        "printing": {
+          "description": "Allow printing (default: true)",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "userPassword": {
+      "description": "Password required to open the PDF",
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "userPassword"
+  ],
+  "type": "object"
+}

4 tool updatesMar 11, 2026

Changedhtml_to_pdf3 fields changed

addedInput schema / properties / emulateMediaType

Added value: +{
+  "description": "CSS media type emulation: \"print\" for clean PDFs, \"screen\" for screen styles",
+  "enum": [
+    "screen",
+    "print"
+  ],
+  "type": "string"
+}

addedInput schema / properties / metadata

Added value: +{
+  "additionalProperties": false,
+  "description": "PDF document metadata (title, author, subject, keywords)",
+  "properties": {
+    "author": {
+      "description": "PDF document author",
+      "type": "string"
+    },
+    "creator": {
+      "description": "Application that created the content",
+      "type": "string"
+    },
+    "keywords": {
+      "description": "PDF keywords array",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "producer": {
+      "description": "Application that produced the PDF",
+      "type": "string"
+    },
+    "subject": {
+      "description": "PDF document subject",
+      "type": "string"
+    },
+    "title": {
+      "description": "PDF document title",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / watermark

Added value: +{
+  "additionalProperties": false,
+  "description": "Add diagonal text watermark on every page",
+  "properties": {
+    "color": {
+      "additionalProperties": false,
+      "description": "RGB color (default: gray)",
+      "properties": {
+        "b": {
+          "description": "Blue 0-1",
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        },
+        "g": {
+          "description": "Green 0-1",
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        },
+        "r": {
+          "description": "Red 0-1",
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "r",
+        "g",
+        "b"
+      ],
+      "type": "object"
+    },
+    "fontSize": {
+      "description": "Font size in points (default: 48)",
+      "maximum": 200,
+      "minimum": 8,
+      "type": "number"
+    },
+    "opacity": {
+      "description": "Opacity 0.01-1 (default: 0.3)",
+      "maximum": 1,
+      "minimum": 0.01,
+      "type": "number"
+    },
+    "rotation": {
+      "description": "Rotation angle in degrees (default: -45)",
+      "maximum": 360,
+      "minimum": -360,
+      "type": "number"
+    },
+    "text": {
+      "description": "Watermark text (e.g. \"DRAFT\", \"CONFIDENTIAL\")",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

Addedmerge_pdfs
Addedsplit_pdf

Changedurl_to_pdf3 fields changed

addedInput schema / properties / emulateMediaType

Added value: +{
+  "description": "CSS media type emulation: \"print\" for clean PDFs, \"screen\" for screen styles",
+  "enum": [
+    "screen",
+    "print"
+  ],
+  "type": "string"
+}

addedInput schema / properties / metadata

Added value: +{
+  "additionalProperties": false,
+  "description": "PDF document metadata (title, author, subject, keywords)",
+  "properties": {
+    "author": {
+      "description": "PDF document author",
+      "type": "string"
+    },
+    "creator": {
+      "description": "Application that created the content",
+      "type": "string"
+    },
+    "keywords": {
+      "description": "PDF keywords array",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "producer": {
+      "description": "Application that produced the PDF",
+      "type": "string"
+    },
+    "subject": {
+      "description": "PDF document subject",
+      "type": "string"
+    },
+    "title": {
+      "description": "PDF document title",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / watermark

Added value: +{
+  "additionalProperties": false,
+  "description": "Add diagonal text watermark on every page",
+  "properties": {
+    "color": {
+      "additionalProperties": false,
+      "description": "RGB color (default: gray)",
+      "properties": {
+        "b": {
+          "description": "Blue 0-1",
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        },
+        "g": {
+          "description": "Green 0-1",
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        },
+        "r": {
+          "description": "Red 0-1",
+          "maximum": 1,
+          "minimum": 0,
+          "type": "number"
+        }
+      },
+      "required": [
+        "r",
+        "g",
+        "b"
+      ],
+      "type": "object"
+    },
+    "fontSize": {
+      "description": "Font size in points (default: 48)",
+      "maximum": 200,
+      "minimum": 8,
+      "type": "number"
+    },
+    "opacity": {
+      "description": "Opacity 0.01-1 (default: 0.3)",
+      "maximum": 1,
+      "minimum": 0.01,
+      "type": "number"
+    },
+    "rotation": {
+      "description": "Rotation angle in degrees (default: -45)",
+      "maximum": 360,
+      "minimum": -360,
+      "type": "number"
+    },
+    "text": {
+      "description": "Watermark text (e.g. \"DRAFT\", \"CONFIDENTIAL\")",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

2 tool updatesFeb 18, 2026
- First observedhtml_to_pdf
- First observedurl_to_pdf

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

PageShot A
site.pageshot
Free screenshot and webpage capture API. Capture full-page screenshots, specific elements, or PDF snapshots of any URL. No API keys required.
Browser Automation Web Scraping App Automation
42
PdfBroker.io A
io.pdfbroker
Cloud PDF generation from HTML, CSS and XSL-FO, with PDF/A and PDF/UA support.
Developer Tools Workplace & Productivity
21
PDFInvoiceAPI A
com.pdfinvoiceapi
Turn HTML or templates into branded invoice & document PDFs from your agent. One call, no install.
Payments & Billing E-commerce & Retail
2
docraptor A
io.usefulapi
Turn HTML or a live URL into polished PDF and Excel files — hosted downloads, async jobs, history.
Developer Tools Workplace & Productivity
42

Related MCP Servers

rendoc
Workplace & Productivity Developer Tools
yoryocoruxo-ai
A
license
A
quality
C
maintenance
Generate professional PDFs from Claude, Cursor, and other AI tools. Create invoices, contracts, reports, and certificates from templates or inline HTML markup.
Updated 5 months ago (2026-04-14 22:53 UTC)
7
59
1
MIT
Yakpdf MCP Server
Web Scraping App Automation
BACH-AI-Tools
A
license
B
quality
D
maintenance
Enables PDF generation from URLs or HTML strings through the Yakpdf API, allowing users to convert web content into PDF documents.
Updated 9 months ago (2025-12-08 00:21 UTC)
1
MIT
HTML to PDF MCP Server
Developer Tools File Systems App Automation
jesamkim
F
license
Not graded
quality
D
maintenance
Converts HTML files or HTML content to PDF using Puppeteer's browser rendering engine with support for CSS, JavaScript, custom page formats, margins, and header/footer templates.
Updated 10 months ago (2025-11-20 01:40 UTC)
6
-
Omni File Converter MCP
Multimedia Processing File Systems Developer Tools
AI-Hub-Admin
A
license
Not graded
quality
D
maintenance
Converts various document formats to desired output formats, currently supporting PDF to image conversion. No access keys required for basic file format conversion operations.
Updated 10 months ago (2025-10-29 05:05 UTC)
3
MIT

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation5/5

Each tool targets a distinct operation: create from HTML, create from URL, merge existing PDFs, inspect PDF metadata, and split/extract pages. The two creation tools are clearly differentiated by input source, so there is minimal risk of misselection.

Naming Consistency3/5

Names follow a mix of patterns: verb_object (merge_pdfs, split_pdf), noun_info (pdf_info), and source_to_output (html_to_pdf, url_to_pdf). While all use lowercase underscores, there is no consistent verb_noun style throughout, making it slightly less predictable.

Tool Count5/5

Five tools provide a focused set of PDF utilities without bloat. Each tool covers a distinct, essential capability for a PDF toolkit, and the count is well within the ideal range.

Completeness4/5

Core operations (creation from HTML/URL, merging, splitting, and information extraction) are covered. Missing advanced features like text extraction or compression, but the toolkit appears reasonably complete for its apparent purpose.

Resources

Need Help?