CasdoorMarketplace

DeepSeek Harness · App integration

Give DeepSeek Harness your MCP servers through Casdoor

The Casdoor plugin for DeepSeek Harness (dsh) signs dsh in to Casdoor with the authorization code flow and PKCE, lists the MCP servers of your organization in Casdoor and adds the ones you turn on to dsh. Every tool call goes through the Casdoor MCP gateway as the DeepSeek Harness agent acting for the signed-in user, so the tool permissions, call records, trace IDs and identity tokens of Casdoor apply. The token is renewed by itself. It runs only with a Casdoor that has a commercial edition license.

Verified by CasdoorCommercial editionAI agentMCPOAuthPKCE
You need a running Casdoor, self-hosted or on Casdoor Cloud. In the examples, replace https://auth.example.com with your Casdoor address (on Casdoor Cloud, something like https://acme.casdoor.com) and the other example.com addresses with your own.

Set up DeepSeek Harness with Casdoor

  1. 1

    Register DeepSeek Harness in Casdoor

    In the Casdoor console, open Applications, add an application for DeepSeek Harness, and on its OIDC/OAuth tab copy the Client ID and Client secret. Add this redirect URL to Redirect URLs:

    • http://127.0.0.1:3080/casdoor/callback
  2. 2

    Install from the Marketplace

    On the Marketplace page of Casdoor, install DeepSeek Harness with the address you open dsh at. Casdoor creates the application with the callback /casdoor/callback and an agent of the same name. Download casdoor-dsh-plugin-1.0.1.tgz under Downloads of the installed integration.

  3. 3

    Install the plugin in DeepSeek Harness

    In dsh, open Plugins in the sidebar, choose to install a plugin and enter the full path of the downloaded file, such as C:\Users\me\Downloads\casdoor-dsh-plugin-1.0.1.tgz. Without the web page, run dsh plugin --profile web add <path of the file> and restart dsh web.

  4. 4

    Open the connection link

    Open this link in the browser where dsh is open. It opens the Casdoor page of dsh with the address, client ID and client secret filled in, and Save and sign in takes you to Casdoor. The page is also at /casdoor/ of dsh, where you can enter them by hand.

    Casdoor addresshttps://auth.example.com
    Client ID<client ID>
    Client secret<client secret>
    http://127.0.0.1:3080/casdoor/#casdoor=https://auth.example.com&clientId=<client ID>&clientSecret=<client secret>
  5. 5

    Choose the MCP servers

    After signing in, the page lists the MCP servers of your organization with their allowed tools. The ones turned on appear in dsh as mcp__casdoor-<server>__<tool> and show their connection state; turn a server off to take its tools away from dsh.

  6. 6

    Govern the calls in Casdoor

    Turn on Record MCP tool calls in the security policy of the organization, and each call is recorded under the MCP server with the user, the agent DeepSeek Harness and a trace ID. Turn on Tool permissions of a server to require an MCP tool permission for every call, and add the agent to a permission to decide what dsh may do: the agent never gets more than the user it acts for. Disable the agent on the Agents page to stop dsh at once.

Good to know

  • The plugin asks Casdoor for its license every 10 minutes and removes the Casdoor MCP servers from dsh when Casdoor runs as the Community edition.
  • The client secret and tokens are kept in the dsh credentials file (.credentials.yaml under the dsh home), not in its configuration.
  • dsh web on another address, such as behind a reverse proxy, needs that address in the redirect URLs of the application.

DeepSeek Harness settings are from its documentation as of November 2026 (DeepSeek Harness, Casdoor: MCP gateway). DeepSeek Harness is a trademark of its owner.