dsh-oauth-mcp-client

KO | EN

gitlite — search

#windows #ios #rust #command-line #ai-agent #monitoring #golang #self-hosted #electron #gemini

dsh-oauth-mcp-client

(★ 9)

OAuth 2.1 Streamable HTTP MCP client plugin for DeepSeek Harness.

File Explorer

ZIP Download

- client.tsx
- connection.ts
- dsh-web.ts
- dsh.ts
- index.ts
- oauth.ts
- profile-config.ts
- registry.ts
- tools.ts
- transport.ts
- web-manager.ts
- dsh.spec.ts
- oauth.spec.ts
- profile-config.spec.ts
- registry.spec.ts
.gitignore
LICENSE
package.json
pnpm-lock.yaml
pnpm-workspace.yaml
README.md
README.zh-CN.md
springbrand.cordis.yml
tsconfig.build.json
tsconfig.client.json
tsconfig.json
tsdown.config.ts
vitest.config.ts

# Use via CDN

jsDelivr

jsDelivr serves any public GitHub repository as a CDN with zero setup. Pick a version and a file to get a ready-to-paste link and snippet.

Version

File

Link

Example

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

English | [简体中文](./README.zh-CN.md)

An OAuth 2.1 Streamable HTTP MCP client plugin for
[DeepSeek Harness](https://github.com/deepseek-ai/DeepSeek-Harness).

It extends the native `dsh-mcp-client` connection flow with PKCE, dynamic
client registration, browser authorization, a loopback callback, persistent
token storage, reconnect handling, and MCP tool registration. The bundled
configuration connects to the Springbrand production MCP Gateway.

This plugin is maintained by [SpringBrand](https://springbrand.ai), an
AI-assisted marketplace for business services. See the
[SpringBrand DeepSeek Harness page](https://springbrand.ai/deepseek-harness)
for product information.

## Features

- OAuth 2.1 authorization code flow with PKCE
- Dynamic OAuth client registration
- Browser login with a loopback callback
- Token and client metadata storage through the DSH credential service
- Streamable HTTP transport with automatic reconnects
- MCP tool discovery, registration, and execution
- DSH Web connection management with live status and capability discovery
- One-click persistent connection setup followed by browser OAuth

## Requirements

- Node.js 22.19 or later
- Git
- A browser for the first OAuth login

## Install

Clone and build the plugin:

```sh
git clone https://github.com/springbrand-lab/dsh-oauth-mcp-client.git
cd dsh-oauth-mcp-client
corepack enable
pnpm install
pnpm build
```

Install the built checkout into a DSH profile and start DSH:

```sh
PLUGIN_DIR="$PWD"
npx --yes @deepseek-ai/dsh@latest plugin --profile web add "$PLUGIN_DIR"
npx --yes @deepseek-ai/dsh@latest web
```

This repository is not published to npm, so installation currently uses the
local checkout. Adding the bundle to the profile also adds the bundled
Springbrand MCP connection; there is no separate MCP registration step.

The first startup opens a browser for Springbrand login and consent. After
authorization, open **Settings → Plugins → MCP Connections** to see the live
connection status and registered capabilities. You can also use these tools to
verify the bundled connection:

- `mcp__springbrand__search_capabilities`
- `mcp__springbrand__execute_capability`

## Use

Ask the agent to search the Springbrand capability catalog, for example:

```text
Search the Springbrand marketplace for resources and list the first 10.
```

The expected call flow is:

```mermaid
flowchart LR
  User["User request"] --> Search["search_capabilities"]
  Search --> Name["Copy the complete capability name"]
  Name --> Execute["execute_capability"]
  Execute --> Result["MCP result"]
```

When calling `execute_capability`, use the complete `name` returned by
`search_capabilities`, such as
`platform:springbrand@0:springbrand.resources.list`. Do not replace it with
the shorter `action_id`, such as `springbrand.resources.list`.

The plugin adds this tool-selection guidance to the agent automatically, so a
normal user request is sufficient; manual tool invocation is not required.

## Manage connections in DSH Web

Open **Settings → Plugins → MCP Connections**, enter a unique server name and
the server's HTTPS MCP URL, then select **Add and sign in**. Complete the OAuth
flow in the browser that opens. DSH loads the new connection and the page shows
its live status and actual registered tools. Select **Remove** on a connection
to unload its tools and remove or disable it in the permanent profile.

The button writes the connection permanently to
`~/.dsh/profiles/web/cordis.patch.yml`. Restarting DSH keeps the connection;
there is no temporary `--patch` command.

```mermaid
flowchart LR
  Add["Add and sign in"] --> Config["Permanent Web profile config"]
  Config --> OAuth["Browser OAuth"]
  OAuth --> Tools["Connected tools in DSH Web"]
```

## Configuration

The bundled defaults are defined in
[`springbrand.cordis.yml`](./springbrand.cordis.yml):

| Field | Description | Default |
| --- | --- | --- |
| `serverName` | Namespace used in registered DSH tool names | `springbrand` |
| `url` | HTTPS Streamable HTTP MCP endpoint | `https://connector.springbrand.ai/mcp` |
| `credentialRef` | DSH credential reference | `SPRINGBRAND_MCP_OAUTH_PRODUCTION` |
| `scope` | Optional OAuth scope | Discovered from the server |
| `callbackPort` | Loopback callback port; `0` selects a free port | `0` |
| `authorizationTimeoutMs` | Browser authorization timeout | `300000` |
| `toolCallTimeoutMs` | Timeout for one MCP tool call | `60000` |
| `failOnStartupError` | Fail activation when the first connection fails | `true` |
| `reconnect` | Exponential reconnect policy | Enabled |

## Manual configuration

The Web page is the default setup path. To configure a connection manually,
add it to the same permanent Web profile file at
`~/.dsh/profiles/web/cordis.patch.yml`:

```yaml
- insert:
    - id: my-oauth-mcp
      name: '@dsh-external/dsh-oauth-mcp-client'
      config:
        serverName: my-mcp
        url: https://mcp.example.com/mcp
        credentialRef: MY_MCP_OAUTH
        failOnStartupError: true
```

The server must support OAuth and MCP Streamable HTTP. Its first connection
opens the browser authorization flow. `serverName` must be unique within the
DSH process and becomes part of the registered tool names, for example
`mcp__my-mcp__search`.

## Security notes

- OAuth state is stored through the DSH credential service, not in this
  repository.
- The callback listener binds to the local loopback interface.
- Do not configure an `Authorization` header; the OAuth client owns it.
- Never commit access tokens, refresh tokens, or exported credential data.

## Development and self-check

```sh
pnpm test
pnpm typecheck
pnpm build
pnpm pack --dry-run
```

For a DSH load-level check, install the checkout into a profile and start it.
Complete the OAuth login when prompted:

```sh
PLUGIN_DIR="$PWD"
npx --yes @deepseek-ai/dsh@latest plugin --profile headless add "$PLUGIN_DIR"
npx --yes @deepseek-ai/dsh@latest --profile headless "hi"
```

## Ecosystem metadata

- Package name: `@dsh-external/dsh-oauth-mcp-client`
- Discovery topic: `dsh-plugin`
- Directory: [Awesome DSH Plugins](https://github.com/AdamPlatin123/awesome-dsh-plugins)

## License

MIT. `src/connection.ts` and `src/tools.ts` are adapted from DeepSeek Harness
`@deepseek-ai/dsh-mcp-client` under the MIT License.

dsh-oauth-mcp-client

Owner Repos

File Explorer

# Use via CDN

Was this content helpful?

Recent Feedback

dsh-oauth-mcp-client

Owner Repos

File Explorer

# Use via CDN

Was this content helpful?

Recent Feedback

Download README