- Home
- MCP servers
- PDFSpark API
PDFSpark API
- typescript
0
GitHub Stars
typescript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You can hook into PDFSpark’s free HTML and URL to PDF conversion capabilities as an MCP server, allowing you to access the conversion API from your own client or automation. This setup supports direct HTTP access to the API and optional local development workflows so you can test and integrate PDF rendering in your applications without keys or rate limits.
How to use
Use an MCP client to connect to either the remote API or a local development server. The remote endpoint exposes a base URL for programmatic access, while the local dev server lets you run and test against the API locally before deploying. You can perform typical actions like converting HTML pages or URLs to PDFs by calling the appropriate endpoints exposed by the service.
How to install
Prerequisites you need before running the server locally:
-
Install Node.js from the official site and ensure node and npm are in your PATH.
-
Open a terminal in the project directory.
Step by step commands to set up and run locally:
# Clone the project
git clone https://github.com/softvoyagers/PDFSpark.git
cd PDFSpark
# Install dependencies
npm install
# Start development server
npm run dev
# Open in browser
open http://localhost:8080
Additional sections
Configuration and usage details address how to connect to the service and what to expect from the API. The base URL for the API is https://pdfspark.dev/api/v1, and you can verify health through the health endpoint. The service supports standard HTTP methods for interacting with examples and health checks, and it runs as a Node.js application during development.
Available tools
example_get
GET endpoint at /api/v1/example to retrieve a sample response demonstrating how to query the API.
example_post
POST endpoint at /api/v1/example to send data and receive a structured response.
health_check
Health check endpoint at /health to verify service status and readiness.