pdf-merger-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port (only when TRANSPORT=http) | 4000 |
| TRANSPORT | No | Transport mode: stdio or http | stdio |
| PDF_MERGER_API_URL | No | Base URL of the PDF Merger App API | http://localhost:3000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pdf_merger_upload_pdfsA | Upload one or more PDF files to the PDF Merger service for later merging. Each file must be a valid PDF (≤100 MB). Up to 30 files can be uploaded per session. If session_id is provided, files are appended to that existing session; otherwise a new session is created. Args:
Returns (JSON): { "session_id": "uuid", "files": [ { "id": "uuid", "name": "doc.pdf", "size": 102400, "sizeFormatted": "100.0 KB" } ] } Examples:
Error Handling:
|
| pdf_merger_remove_fileA | Remove a single PDF file from an upload session on the PDF Merger service. The file is permanently deleted from cloud storage. This operation cannot be undone. Args:
Returns (JSON): { "success": true } Error Handling:
|
| pdf_merger_mergeA | Merge previously uploaded PDFs in a specified order into a single PDF. Returns a one-time download token. Use pdf_merger_get_download_url to build the download link. The session is consumed after merging — re-upload files to merge again. Args:
Returns (JSON): { "token": "uuid", "page_count": 45, "size_formatted": "2.3 MB", "download_url": "https://..." } Workflow:
Error Handling:
|
| pdf_merger_get_download_urlA | Build a one-time download URL for a merged PDF. The token is returned by pdf_merger_merge. Each token can only be used once; after the first download the link expires and all associated cloud files are cleaned up. Args:
Returns (JSON): { "download_url": "https://your-api.example.com/download/" } Notes:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/NikhilBelwate/pdf-merger-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server