One MCP Server, Three Config Schemas: Wiring PDF4me Into Cursor, VS Code, Claude Desktop, Windsurf and Continue
Five MCP clients. One server command. Three different config schemas. That last part is the bit worth knowing before you wire a document API into an agent, because when you get it wrong nothing errors loudly. The server simply does not appear. Everything below comes from PDF4me's MCP getting started guide , read in full on 16 August 2026. One command, every client The server is a single command:…
PDF4me's MCP server can be configured in three different shapes, depending on the client being used. Cursor, Claude Desktop, and Windsurf require the "mcpServers" property with a server object keyed by server name, while VS Code employs a "servers" property with an explicit "stdio" transport type. Continue configures the server using an array of named entries.
The server command, "uvx pdf4me-mcp", is shared across all clients and requires the "API_KEY" environment variable. The server command must be available in the system's PATH, and running the server without a client can help differentiate server issues from configuration problems. PDF4me MCP is separate from Agent Skills, with the former allowing agents to invoke the server without needing to write REST API calls themselves.
Before integrating PDF4me into an agent, ensure the server is registered and verify the available tools within the chosen client.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
