通过 MCP 把 DeepSeek Harness 接到 iHatePosting:列出已连接的社交渠道、读取各平台的发帖规则,并在 15 个平台上起草、定时或发布帖子。
安装
# npm 包(预构建)
dsh plugin --profile web add dsh-ihateposting
# GitHub 源码(首次需按提示配置 allowBuilds 构建授权后重试)
dsh plugin --profile web add github:iHatePostingOrg/iHatePosting-Agent#path:/plugins/dsh-ihateposting
装任何插件都等于在你的机器上跑第三方代码,权限和你本人一样大——能读你的文件、用你的凭据、访问网络,工具审批管不到它。GitHub 来源的插件还会在安装时执行构建脚本——pnpm 默认拦截,所以安装可能停在 ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED 或 ERR_PNPM_IGNORED_BUILDS;dsh 会打印出需要添加的确切键名,把它加进该 profile 的 pnpm-workspace.yaml 的 allowBuilds 下,重跑一次即可装上。放行构建本身就是一次信任判断:请只安装可信来源,并尽量锁定 commit(github:owner/repo#sha)。
README
该插件的 README 只有英文版本。
npm: dsh-ihateposting ·
source: iHatePostingOrg/iHatePosting-Agent
DeepSeek Harness (dsh) plugin for
iHatePosting, the social media scheduler. It connects the agent
to the iHatePosting MCP server so it can list your connected channels, fetch each platform's
posting rules, and schedule, draft, or publish posts across 15 platforms (X, LinkedIn,
Instagram, Facebook, Threads, TikTok, YouTube, Pinterest, Bluesky, Mastodon,
Discord, Slack, Telegram, and more).
Install
From the repository:
dsh plugin --profile web add "github:iHatePostingOrg/iHatePosting-Agent#path:/plugins/dsh-ihateposting"
Or from npm:
dsh plugin --profile web add dsh-ihateposting
Then give it an iHatePosting API key. Get it from iHatePosting → Settings → Agents / Dev
and export it before starting dsh, or put it in $DSH_HOME/.env:
export IHATEPOSTING_API_KEY=your-api-key
dsh web
Restart the profile after installing. Ask the agent "List my connected social media accounts" to verify the connection.
What you get
The bundle mounts two rows:
| Row | Package | Role |
|---|---|---|
ihateposting |
dsh-ihateposting (this package) |
Reads the API key, exposes ctx.ihateposting (url, headers), and registers the ihateposting skill that teaches the agent the posting workflow and the HTML content rules. |
ihateposting-mcp |
@deepseek-ai/dsh-mcp-client (shipped with dsh) |
Connects to https://app.ihateposting.com/api/mcp over streamable HTTP with a Bearer header and registers the server's tools. |
The model sees the iHatePosting MCP tools under the mcp__ihateposting__ namespace:
| Tool | What it does |
|---|---|
mcp__ihateposting__integrationList |
List connected channels (optionally filtered by group) |
mcp__ihateposting__groupList |
List customer groups |
mcp__ihateposting__integrationSchema |
Posting rules, character limits, and required settings for a platform |
mcp__ihateposting__triggerTool |
Platform helpers (list Discord channels, list Pinterest boards, look up LinkedIn pages) |
mcp__ihateposting__integrationSchedulePostTool |
Schedule, draft, or immediately publish posts |
mcp__ihateposting__postsListTool |
List posts between two dates |
mcp__ihateposting__postSettingsTool |
Update settings of an unpublished post |
mcp__ihateposting__deletePostTool |
Delete a post |
mcp__ihateposting__uploadFromUrlTool / mediaListTool / mediaStatusTool |
Put a picture or video into the media library from a public web address, find a file that is already there, check that it is ready |
mcp__ihateposting__uploadWidgetTool / uploadWidgetStatusTool |
An upload panel for files on the person's own computer (only in a client that shows panels), and the list of what was added |
The tool list comes from the server at connect time, so new iHatePosting tools appear without a plugin update.
Configuration
Override the ihateposting row in your profile's cordis.patch.yml ($DSH_HOME/profiles/web/cordis.patch.yml).
A bare id: configures the existing row:
- id: ihateposting
config:
apiKeyEnv: IHATEPOSTING_API_KEY # env var that holds the key (default)
baseUrl: https://app.ihateposting.com/api # another server that answers the same routes: https://your-server.example.com/api
skill: true # register the `ihateposting` workflow skill
| Field | Default | Description |
|---|---|---|
apiKeyEnv |
IHATEPOSTING_API_KEY |
Environment variable read at boot for the API key. |
apiKey |
'' |
Inline key. Prefer the env var; this exists for patch-level overrides. |
baseUrl |
https://app.ihateposting.com/api |
iHatePosting API address. The MCP endpoint is <baseUrl>/mcp (an address that already ends in /mcp is used as it is). Another server that answers the same routes can be named here. |
skill |
true |
Register the ihateposting skill on ctx.skills. |
Without a key the ihateposting row logs a warning naming the variable to set, and the
ihateposting-mcp row connects without credentials, which iHatePosting refuses with a 401, so it registers no tools. dsh keeps booting.
Self-hosted iHatePosting
The MCP server is part of the iHatePosting app's API and listens at /mcp (Bearer auth), so by
default the plugin connects to https://app.ihateposting.com/api/mcp. The app is hosted, so there
is no server of your own to set up; another server that answers the same routes can be named with
baseUrl.
Development
cd plugins/dsh-ihateposting
pnpm test
Link a local checkout into a profile:
dsh plugin --profile web add /absolute/path/to/iHatePosting-Agent/plugins/dsh-ihateposting
Related
- iHatePosting CLI — the
ihateposting-agentcommand-line tool and the Claude Code / Cursor / Grok plugins in this repository.
License
MIT, same as the rest of this repository.
Sections that were in this file before it followed the reference
Status
Status: 0.1.1, never run inside a real dsh (see "Unverified" below).
The profile name and the PowerShell form of the install
web is one of the profile templates dsh ships; use the profile you want.
# PowerShell
$env:IHATEPOSTING_API_KEY = "your_key"
dsh web
How the key is handled
The key is sent in one place only: the Authorization: Bearer <key> header of the ihateposting-mcp row, to the address above. The plugin never prints it, logs it or contacts any address itself (the tests check this). A key that holds a space or a control character is not used and is not repeated in the log.
The browser sign-in address is not used
https://app.ihateposting.com/api/mcp/oauth (a browser sign-in by OAuth) is not wired: the pages of dsh's MCP client that were read do not describe an OAuth flow (unverified), so this plugin uses the key.
What was verified, and from where
Read first-hand on 2026-11-15 in deepseek-ai/deepseek-harness (branch master, commit 39163dd) and in the published packages:
- A bundle is a package whose
package.jsonhas"dsh": { "bundle": { "patch": "./cordis.patch.yml" } }: docs/user/develop/basic/publish.md. - A plugin module exports
name, optionallyinject, andapply; theConfigexport must be a Schemastery schema, never a plain object: docs/user/develop/basic/index.md and config.md. - A row that lists
inject: [service]has itsconfigread as!!js ctx.<service>.<field>after the service is up, and the loader evaluates a row'sconfigonly then: publish.md (the example withctx.myAppStartup.port) and docs/cordis-primer.md. - In
@deepseek-ai/cordis4.1.0 (npm):ctx.provide(name, value),ctx.inject(deps, callback)and a callablectx.loggerwithinfoandwarn. In@deepseek-ai/schemastery3.19.0 (npm):.role().dsh's own dependency catalog pins cordis 4.0.2 and schemastery 3.18.2, which the peer ranges inpackage.json(^4.0.1,^3.18.1) include. - The MCP client row (
@deepseek-ai/dsh-mcp-client) takestransport,serverName,urlandheaders, and names toolsmcp__<serverName>__<tool>: packages/mcp/mcp-client/README.md (read on 2026-11-13, second-hand).
From the owner of this project (not checked from here): the MCP address, that the key goes in Authorization: Bearer <key>, and that the key is made under Settings > Agents / Dev. The server's refusal of a request without a key is read from the app's own code.
Unverified
- No real
dshwas run. The plugin was never loaded bydsh,dsh plugin addwas not run, and no request was made to iHatePosting's server (no network and no key were used). The tests use stand-ins for the context and, where the real package is not installed, for@deepseek-ai/schemastery; with the real package installed the same checks run against it. - Which
dshreleases it works with.engines.dshis left out on purpose rather than guessed. - The fields
skills.registeris given:name,description,contentandsource: 'runtime'follow the documentation read earlier;invocation: { modelInvocable, userInvocable }is added because another published plugin fordshpasses it, and no page read describes it. - Why other plugins export only named values: one of them says a default export makes the loader drop
injectandapply, and thatschemasteryrejects frozen objects. Neither statement was found in the documentation or the package source. This plugin uses named exports (the documented function form) and hands out a fresh plain copy of the headers on every read, which is right either way. - Whether
!!jsexpressions see a key that is only in a.envfile. Put it in the environment to be sure. - Whether the MCP client keeps header values out of its own logs and error text.
- Installing from
github:for this subfolder, and installing from npm.
链接
同类插件
Tencent/WeKnora#dsh-weknora★ 37546
把 WeKnora 知识库接入 dsh 的四个只读工具:列出知识库、混合检索原文片段、按顺序还原单篇文档,以及直接取用 WeKnora 自己带引用的 RAG 或 ReAct agent 回答(含可续聊的 session id)。
DayuanJiang/next-ai-draw-io#dsh-plugin★ 36997
dsh 的 draw.io 绘图插件:通过 next-ai-drawio MCP 服务器作图,点回复里的链接在右侧栏打开实时预览,可以手动修改图,AI 的每次修改都是可以恢复的版本。需 Node.js 18+,首次使用由 npx 下载 MCP 服务器。
superdesigndev/treg★ 8164
给 Agent 的工具目录:按「要做的事」检索约 2,600 个外部接口(SEO 与 SERP、外链、社交、人物与公司信息补全、广告库、抓取),查看参数与单次调用价格后直接调用,凭据由服务端注入。附带技能,MCP 行在未设置 TREG_TOKEN 前保持禁用。
T-Auto/dsh-ops★ 5864
为 Windows 的 DSH 提供 bash、PowerShell 7 及 Rust 高性能工具,减少 token 消耗。
sixtysevenlf/dsh-blender-plugin★ 2147
让 DSH agent 通过直连 TCP 通道驱动本地 Blender,提供 15 个工具:视口帧、自定义视角渲染、Python 执行、无头与作业卸载、事务回滚,以及 34 个 family / 228 个 op 的规划层。
helloHub1212/dsh-windows-mcp★ 1456
通过官方 MCP 客户端桥接层把 CursorTouch/Windows-MCP 桌面自动化服务器接入 DSH,把截屏、UI 树快照、鼠标键盘输入、剪贴板、进程与注册表等工具注册成 mcp__windows__* 供模型调用,并附带 windows_mcp_doctor 诊断工具;Computer Use 默认关闭,需在插件面板里打开。
社区评论
评论公开保存在 GitHub Discussions。加载评论会连接 GitHub 和 Giscus;发表内容需要 GitHub 账号。