> ## Documentation Index
> Fetch the complete documentation index at: https://linkly.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Linkly AI in QoderWork

> Connect your Linkly AI local knowledge base to QoderWork, letting the desktop AI work assistant search and read your private documents

## What You Can Do

<AccordionGroup>
  <Accordion title="Retrieve local materials in automated tasks">
    When creating tasks in QoderWork, use the Linkly AI Connector to let AI
    first search local documents, then combine browser automation, file
    processing, and other tools to complete complex workflows grounded in real
    materials.
  </Accordion>

  <Accordion title="Multiple connectors working together">
    Combine Linkly AI with Slack, Microsoft 365, Calendar, and other Connectors
    to access both local documents and online services in a single task —
    breaking down information silos.
  </Accordion>

  <Accordion title="No need to re-upload documents">
    Configure once, then share the same local knowledge base across all tasks
    and conversations in QoderWork. AI retrieves on demand — no need to upload
    attachments every time.
  </Accordion>
</AccordionGroup>

## Prerequisites

* [QoderWork](https://www.qoderwork.com) installed
* Linkly AI Desktop running with the MCP service active

## Configuration Steps

<Tabs>
  <Tab title="Local MCP HTTP (Recommended)" icon="globe">
    <Steps>
      <Step title="Open the Connectors page">
        Click **Extensions → Connectors** in the left navigation.

        <img src="https://mintcdn.com/linklyai/PdV3hIc9lsrn2ArH/images/qoderwork-connectors.webp?fit=max&auto=format&n=PdV3hIc9lsrn2ArH&q=85&s=fa54deb63b8e5ab0e75819441cea5772" alt="QoderWork Connectors page" width="2712" height="1672" data-path="images/qoderwork-connectors.webp" />
      </Step>

      <Step title="Add a new connector">
        Click **+ Add** in the top right, then select **Fill in Config
        Manually** from the dropdown.

        <img src="https://mintcdn.com/linklyai/PdV3hIc9lsrn2ArH/images/qoderwork-add-menu.webp?fit=max&auto=format&n=PdV3hIc9lsrn2ArH&q=85&s=a69a3a4730661697237d3b8a86e8b312" alt="Select Fill in Config Manually" width="2712" height="1672" data-path="images/qoderwork-add-menu.webp" />
      </Step>

      <Step title="Fill in the configuration and add">
        In the **Add MCP Server** dialog, fill in the following:

        * **Server Type**: `Streamable HTTP`
        * **Server Name**: `linkly-ai`
        * **Server URL**: `http://127.0.0.1:60606/mcp`

        Click **Add** to finish.

        <img src="https://mintcdn.com/linklyai/PdV3hIc9lsrn2ArH/images/qoderwork-http-local.webp?fit=max&auto=format&n=PdV3hIc9lsrn2ArH&q=85&s=2bcf000ac03e113422a28efa0307453e" alt="Fill in Streamable HTTP local configuration" width="2712" height="1672" data-path="images/qoderwork-http-local.webp" />
      </Step>
    </Steps>
  </Tab>

  <Tab title="Remote MCP" icon="cloud">
    Complete [remote access configuration](/en/use-in-remote) first, with the
    desktop tunnel showing <Badge stroke color="green">● Connected</Badge>.

    <Steps>
      <Step title="Open the Connectors page">
        Click **Extensions → Connectors** in the left navigation.
      </Step>

      <Step title="Add a new connector">
        Click **+ Add → Fill in Config Manually**.
      </Step>

      <Step title="Fill in the remote configuration and add">
        In the **Add MCP Server** dialog, fill in the following:

        * **Server Type**: `Streamable HTTP`
        * **Server Name**: `linkly-ai`
        * **Server URL**: `https://mcp.linkly.ai/mcp`

        Click **Add** to finish.

        <img src="https://mintcdn.com/linklyai/PdV3hIc9lsrn2ArH/images/qoderwork-http-remote.webp?fit=max&auto=format&n=PdV3hIc9lsrn2ArH&q=85&s=a468129273f508c53266bf00ee2df57c" alt="Fill in Streamable HTTP remote configuration" width="2712" height="1672" data-path="images/qoderwork-http-remote.webp" />
      </Step>
    </Steps>
  </Tab>

  <Tab title="CLI Stdio (Fallback)" icon="terminal">
    [Install Linkly AI CLI](/en/use-cli) first.

    <Steps>
      <Step title="Open the Connectors page">
        Click **Extensions → Connectors** in the left navigation.
      </Step>

      <Step title="Add a new connector">
        Click **+ Add → Fill in Config Manually**.
      </Step>

      <Step title="Fill in the CLI configuration and add">
        In the **Add MCP Server** dialog, fill in the following:

        * **Server Type**: `STDIO`
        * **Command**: `linkly mcp`

        Click **Add** to finish.

        <img src="https://mintcdn.com/linklyai/PdV3hIc9lsrn2ArH/images/qoderwork-stdio.webp?fit=max&auto=format&n=PdV3hIc9lsrn2ArH&q=85&s=da7e5da7aba7621b534e7b57f4d84b5f" alt="Fill in STDIO CLI configuration" width="2712" height="1672" data-path="images/qoderwork-stdio.webp" />
      </Step>
    </Steps>
  </Tab>
</Tabs>

## Enable in Conversations

After adding, you still need to manually enable the connector in each
conversation. Click the plugin icon in the input toolbar, select
**Connectors**, and toggle on **linkly-ai**.

<img src="https://mintcdn.com/linklyai/PdV3hIc9lsrn2ArH/images/qoderwork-chat-toggle.webp?fit=max&auto=format&n=PdV3hIc9lsrn2ArH&q=85&s=799acb0bec2540e9f2ab7772ac43d791" alt="Enable linkly-ai connector in the chat toolbar" width="2712" height="1672" data-path="images/qoderwork-chat-toggle.webp" />

## FAQ

<AccordionGroup>
  <Accordion title="Cannot find it in the Connectors list after adding">
    Switch to the **Installed** tab on the Connectors page to see the installed
    list. If still not visible, try clicking the refresh button in the top
    right.
  </Accordion>

  <Accordion title="Remote MCP connection timed out">
    Make sure the remote access feature in Linkly AI Desktop is enabled and the
    desktop tunnel shows "Connected." You can check this in the MCP section of
    Linkly AI settings.
  </Accordion>

  <Accordion title="STDIO mode: command not found">
    Confirm Linkly AI CLI is correctly installed by running `linkly --version`
    in a terminal.
  </Accordion>
</AccordionGroup>