Foxit PDF Editor supports seamless integration with MCP servers, allowing the AI Assistant to connect with local tools, remote services, and enterprise systems. Supported MCP server types are categorized by communication protocol:
stdio-based MCP Server: A local executable launched and managed by Foxit PDF Editor, communicating via standard input/output (stdin/stdout).
Streamable HTTP-based MCP Server: A remote HTTP endpoint that accepts POST requests and returns incremental (streamed) responses, typically using chunked transfer encoding.
SSE-based MCP Server: A long-lived HTTP connection initiated by Foxit PDF Editor to receive push-style streamed responses from the MCP server, following the Server-Sent Events (SSE) protocol.
When connecting to an MCP server, provide the following details in the MCP Manager dialog box depending on the communication type.
For stdio-based MCP servers:
Server Name: The name of the MCP server.
Command: The command or executable name to be launched locally by Foxit PDF Editor. This may refer to a direct binary (e.g., python, node) or an abstraction/wrapper such as uvx.
Parameters: A list of command-line arguments passed to the Command at runtime.
Environment Variables: Optional key-value pairs for the launched process. If a key matches an existing variable, the value overrides it within the launched process only.
For Streamable HTTP/SSE-based MCP servers:
Server Name: The name of the MCP server.
URL: Full endpoint address (e.g., https://example.com/mcp)
Headers: Custom authentication or content headers.
Some stdio-based MCP servers require specific runtime environments depending on how the server is implemented. For example:
Servers provided as Python packages require the necessary Python libraries to be installed.
Servers provided as npm packages require a Node.js environment and relevant npm modules.
Note: Please refer to the official documentation of each MCP server for accurate setup instructions and to install the appropriate dependencies.