The AI Assistant allows you to build custom connectors, supporting three different connection types to fit local process, real-time streaming, and remote HTTP service scenarios. Required fields are marked with an asterisk * to ensure critical configuration is provided.
Supported connector types by communication protocol:
stdio: A local executable launched and managed by Foxit PDF Editor, communicating via standard input/output (stdin/stdout).
Streamable HTTP: A remote HTTP endpoint that accepts POST requests and returns incremental (streamed) responses, typically using chunked transfer encoding.
SSE: A long-lived HTTP connection initiated by Foxit PDF Editor to receive push-style streamed responses from the MCP (Model Context Protocol) server, following the Server-Sent Events (SSE) protocol.
When creating a connector, provide the following details depending on the communication type.
For stdio connectors:
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 connectors:
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 connectors 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 connector for accurate setup instructions and to install the appropriate dependencies.