What do I get after adding MCP?
The AI can see our print capabilities, so the code it writes fits the SDK better; it can also print locally when needed. Keep the Web Print Expert client running on the PC.
Add mcp-web-print-pdf and Claude, Cursor, or dsh understand our print SDK better — and can call local printing when needed.
{
"mcpServers": {
"webprint": {
"command": "npx",
"args": ["-y", "mcp-web-print-pdf"]
}
}
}
Three hops on your machine — no cloud relay.
npx -y mcp-web-print-pdf (stdio).Same stdio command; only the config file location differs.
| Host | Config location |
|---|---|
| Claude Desktop | %APPDATA%\Claude\claude_desktop_config.json |
| Cursor | ~/.cursor/mcp.json |
| dsh | ~/.dsh/profiles/<profile>/cordis.patch.yml |
| Claude Code / VS Code / Codex | CLI or project mcp.json (see setup guide) |
Full host table, tools and parameters: MCP setup guide.
Install and start the desktop client, then follow the setup guide for MCP. Usually takes a few minutes.
The AI can see our print capabilities, so the code it writes fits the SDK better; it can also print locally when needed. Keep the Web Print Expert client running on the PC.
No. The MCP server, client and print queue stay local; only the first npx download needs the network.
Claude Desktop, Cursor, dsh, Claude Code, VS Code Copilot, Codex CLI and other MCP stdio hosts.
See the MCP setup guide for tools, arguments and pitfalls.