- Home
- MCP servers
- PDFDancer
PDFDancer
- typescript
1
GitHub Stars
typescript
Language
6 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.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"menschmachine-pdfdancer-mcp": {
"command": "npx",
"args": [
"-y",
"@pdfdancer/pdfdancer-mcp"
],
"env": {
"PDFDANCER_DOCS_BASE_URL": "https://your-docs-endpoint.com"
}
}
}
}You can connect PDFDancer to MCP-compatible AI coding assistants so you can write, run, and refactor PDFDancer SDK code directly from your editor or agent. This MCP server enables seamless in-context PDF manipulation tasks across TypeScript, Python, and Java projects, making it practical to build production workflows and tooling that transform real-world PDFs within your apps.
How to use
You install the PDFDancer MCP server in your MCP client and then connect to it through the client’s MCP integration. Once connected, you can describe the PDF transformation you want, and your assistant will generate and refine code against the PDFDancer SDK. Typical tasks include redacting, stamping, repositioning elements, or creating document workflows that operate on PDFs in production.
How to install
Prerequisites you need to fulfill before installation are the following: Node.js version 18.0.0 or newer. An MCP client such as Cursor, Claude Code, VS Code, Windsurf, Zed, or any MCP-compatible client.
Install the MCP server for your preferred client using one of the provided configurations. The standard local, stdio-based setup uses the following command after you have a running Node environment.
Additional configuration and usage notes
The PDFDancer MCP server can be run in a local stdio configuration with the following command: use npx to execute the package and pass the MCP entry point as an argument.
Security and environment
If you customize the documentation endpoint for PDFDancer, you may provide an environment variable to point the server at your documentation service. This variable is optional and only needed if you have a non-default docs base URL.
Examples and workflow notes
A typical workflow with the MCP server is to install the server, connect a codebase that uses PDFDancer, describe the desired behavior in code, and then let your assistant generate the necessary SDK usage. You test and iterate until the produced PDFs meet your requirements.
Troubleshooting tips
If the MCP server does not appear connected, verify that your MCP client is configured to point at the same stdio server process. Check that the npm or npx command is available in your environment and that the process is running. Ensure any environment variables you rely on are set before starting the server.
Configuration and runtime details
Configuration for MCP clients is provided as explicit snippets in the options for each client. The server supports a standard stdio connection using npm tooling and the pdfdancer-mcp package. When you configure the server for a client, you typically specify the command and arguments to launch the MCP server.
Developer note
The server exposes a small set of tooling endpoints to explore documentation, check versions, and search or fetch documentation routes. Use these tools to understand and implement PDFDancer SDK capabilities in your projects.
Demo scenario
You can prompt your MCP-enabled assistant to build a PDF application that writes a simple PDF with the text Hello World, leveraging the PDFDancer SDK through the MCP interface. The assistant will generate the project structure, install dependencies, and run the sample to produce an output PDF.
Available tools
help
Display a comprehensive overview of PDFDancer SDK capabilities with code examples in TypeScript, Python, and Java.
version
Return the current version of the pdfdancer-mcp server.
search-docs
Search the official PDFDancer SDK documentation by keyword and return relevant routes with snippets and relevance scores.
get-docs
Retrieve the full documentation content for a specific route, including code examples and API references.