reactive-resume
reactive-resume
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
PROJECT TOPICS
INSTALL REFERENCE
dsh plugin --profile web add github:oomol-lab/dsh-oomol
该命令指向仓库当前默认分支;尚无绑定当前 commit 的完整验证结果。
PROJECT README
Use OOMOL Connector Actions from DeepSeek Harness through progressive MCP discovery.
dsh-oomol supports OOMOL Hosted and self-hosted OpenConnector. One plugin instance connects to one Connector endpoint.
0.2.0-rc.2 or later within 0.2.0Install the plugin into the Web profile and restart Harness:
dsh plugin --profile web add -w dsh-oomol
dsh web
The plugin appears on the Plugins page as dsh-oomol. Open it to configure the Connector key.
The package connects to OOMOL Hosted by default:
- id: oomol
name: dsh-oomol
config:
endpoint: https://connector.oomol.com/v1/mcp
teamNameEnv: OOMOL_TEAM_NAME
serverName: oomol
toolCallTimeoutMs: 60000
failOnStartupError: false
Create an OOMOL MCP API key in OOMOL Console, then save it on the plugin page. Harness Credentials stores the key under OOMOL_MCP_API_KEY.
Managed environments can provide it at launch:
export OOMOL_MCP_API_KEY="api_..."
dsh web
Set a team identity when needed:
export OOMOL_TEAM_NAME="your-team"
dsh web
The Connections button opens the native Harness panel for OOMOL Hosted accounts.
Override the endpoint in the profile's cordis.patch.yml:
- update:
id: oomol
config:
endpoint: http://127.0.0.1:3000/mcp
The plugin recognizes every non-official endpoint as self-hosted. Local OpenConnector deployments can run without authentication. Deployments with runtime authentication use the key stored under OOMOL_CONNECT_RUNTIME_TOKEN:
export OOMOL_CONNECT_RUNTIME_TOKEN="oct_..."
dsh web
You can also save the runtime API key on the plugin page. Create persistent runtime keys in the OpenConnector Console Access page.
Self-hosted HTTP endpoints are limited to localhost, 127.0.0.1, and [::1]. Remote deployments use HTTPS:
- update:
id: oomol
config:
endpoint: https://connect.example.com/mcp
The Connections button opens the endpoint origin, such as https://connect.example.com, where OpenConnector serves its Console.
Both modes support an explicit credential reference:
- update:
id: oomol
config:
endpoint: https://connect.example.com/mcp
apiKeyEnv: MY_CONNECT_RUNTIME_TOKEN
Harness Credentials resolves apiKeyEnv first and the launch environment second.
Start with discovery:
Show me the connectors available to this account.
Find Actions that can create a calendar event and inspect the selected Action schema.
For operations with external effects, include the target account and proposed arguments in your request before execution.
The plugin mounts DeepSeek Harness's Streamable HTTP MCP client with the selected Connector endpoint. Connector Actions remain progressively discoverable, keeping the permanent Harness tool surface small.
OOMOL Hosted stores Provider credentials in OOMOL Connector. Self-hosted deployments store them in OpenConnector. Harness stores only the Connector client key selected by apiKeyEnv.
The browser receives the credential reference and status metadata. Connector API keys and Provider credentials stay in Host-side secret boundaries.
See Architecture for implementation details.
| Field | Default | Purpose |
|---|---|---|
endpoint |
https://connector.oomol.com/v1/mcp |
Streamable HTTP MCP endpoint |
apiKeyEnv |
Derived from endpoint |
Harness credential reference and launch environment name |
teamName |
unset | OOMOL Hosted team identity |
teamNameEnv |
OOMOL_TEAM_NAME |
OOMOL Hosted team environment name |
serverName |
oomol |
Harness MCP tool namespace |
toolCallTimeoutMs |
60000 |
Tool call timeout |
failOnStartupError |
false |
Fail Harness startup when MCP discovery fails |
Derived credential references:
| Endpoint mode | Default reference | Required |
|---|---|---|
| OOMOL Hosted | OOMOL_MCP_API_KEY |
Yes |
| Self-hosted | OOMOL_CONNECT_RUNTIME_TOKEN |
Depends on the OpenConnector deployment |
| Symptom | Action |
|---|---|
| Plugin missing from the Plugins page | Install it in the web profile and restart dsh web |
| OOMOL Hosted shows Not configured | Save an OOMOL MCP API key on the plugin page |
| Self-hosted returns Unauthorized | Save a runtime API key created by that OpenConnector instance |
| Self-hosted Console link returns 404 | Open the Console URL configured by the OpenConnector deployment |
| Expected app is missing | Open the relevant Connector Console and configure the Provider connection |
| Connections tab does not appear | Open a Session first; the Connections tab lives in that Session's right sidebar |
Run local diagnostics:
pnpm run doctor
pnpm install --frozen-lockfile
pnpm check
Build and install the checkout into a Web profile:
pnpm build
dsh plugin --profile web add -w "$(pwd)"
License: MIT
CLASSIFICATION EVIDENCE
系统优先读取 GitHub Topics,再与站内分类词典和词根规则比对。当前命中: mcp、model-context-protocol。