The official Pagr MCP server is listed on Smithery as getpagr/pagr. Smithery provides a hosted MCP setup path for clients and workflows that prefer registry-managed MCP servers.
One-click installation
Add the Pagr MCP server through Smithery:
npx -y smithery mcp add getpagr/pagr
You can inspect the published tools with Smithery:
npx -y smithery tool list getpagr/pagr
npx -y smithery tool get getpagr/pagr upload_file
Direct Smithery endpoint
Smithery lists the direct hosted endpoint for Pagr as:
https://pagr.run.tools
Required config:
PAGR_API_KEY- a Pagr API key that starts withpagr_.
Native Pagr MCP endpoint
The native Pagr remote MCP endpoint is separate from Smithery:
https://mcp.getpagr.co/mcp
Use the native endpoint when your MCP client can connect directly to remote MCP and pass Authorization: Bearer pagr_... or another supported API-key header.
Available tools
The Smithery listing exposes the same Pagr tool surface:
upload_fileupdate_fileupdate_file_by_idlist_filesdelete_filerename_file
These tools publish and manage files for the authenticated Pagr account. Updates replace the current HTML in place and do not create restore history.
Environment variables
The local and Smithery-hosted MCP flows use:
PAGR_API_KEY: required for runtime tool execution.PAGR_WORKER_URL: optional Worker URL override for local development. Defaults tohttps://pagr.linkin the local package.
Active verification and backlink
This documentation page serves as the verified backlink for the Pagr MCP listing on Smithery.
- Official listing URL: https://smithery.ai/servers/getpagr/pagr
- Official badge URL: https://smithery.ai/badge/getpagr/pagr