Skip to content
  • There are no suggestions because the search field is empty.

How Do I Create a Custom Connector in Foxit Workspace Desktop?

Answer

Quick Start

How Do I Create a Custom Connector in Foxit Workspace Desktop?

Last updated September 3, 2026 · 2 min read · Tier L1

Short answer

Beyond the built-in Asana, Atlassian, Fireflies, and HubSpot connectors, Foxit Workspace Desktop lets you add your own MCP (Model Context Protocol) connector -- either by configuring one manually, importing a JSON definition, or starting from a built-in example. Manage this from Workspace Settings > Connectors.

Applies to: Foxit Workspace Desktop (version 0.1.3 and later) and Foxit PDF Editor/Reader Desktop's AI Assistant (version 2026.2 and later) -- custom connectors are set up the same way in both. In Workspace, this is desktop-only -- see How Do I Download the Foxit Workspace Desktop App? and Why Can't I See Connectors in Foxit Workspace on the Web?Where do I manage connectors?

Open Workspace Settings > Connectors. You'll see a Connected section (a built-in Connector Manager for managing connectors within the app) and an Available section listing the built-in connectors (Asana, Atlassian, Fireflies, HubSpot, and others), each with icons to auto-start, connect, or delete it.

How do I add my own connector?

Click the + button next to "Manage Your Connectors," or the ... menu for additional options:

  • Create Connector -- configure one manually (see fields below).
  • Import JSON from Clipboard -- paste an existing MCP server JSON definition.
  • Start from an example -- ready-made templates are offered, including Arxiv MCP Server and Microsoft Docs MCP Server.

The ... menu on the Connector Manager row itself also offers Request logs and Refresh, useful if a connector isn't behaving as expected.

What do I fill in when creating a connector manually?

Choose a Type first -- this determines how Workspace talks to your MCP server:

Type Description
Stdio Run a local command through standard input and output.
SSE Connect to a remote Server-Sent Events endpoint.
Streamable HTTP Connect to a streamable HTTP MCP endpoint.

Then fill in: Name, whether to Auto start (launch this connector automatically when the workspace opens), a Timeout in seconds (300 by default), and -- for a Stdio connector -- a Command (for example uvx) and its Arguments (one per line, for example tool / run / my-mcp-server). An Environment variables field further down accepts KEY=VALUE pairs, one per line (for example API_KEY=demo), for connectors that need credentials or configuration passed in at launch.

How do I manage a connector once it's added?

Each connector row has icons to toggle auto-start (rocket icon -- "Start automatically when the workspace opens"), connect or disconnect it (play icon to connect; once connected, the icon becomes a disable/disconnect action), and delete it (trash icon).

Related Articles Tags: quick-start foxit-workspace connectors mcp desktop-app integrations