dsh-github-mcp

DSH-GitHub bridge: exposes the official GitHub MCP server as DSH-native tools, and fixes the issue where DSH's bridge discards file content.

After install, the agent can reach GitHub and read files directly through the mcp__github__* tool family and the github_file_read tool — no local Git or gh CLI in between.

Install

dsh plugin --profile web add github:GitRuozhi/dsh-github-mcp

Set GITHUB_TOKEN and restart dsh web. If gh is already logged in on this machine, you can just ask DSH to configure it for you.

Features

Tools

Two tool families are added on install:

github_file_read — read a file's contents (decoded to UTF-8 text) or list a directory; private repos work too (needs GITHUB_TOKEN).

**mcp__github__* (44 tools from GitHub's official MCP server)**

• Search: search_repositories, search_code, search_issues, search_pull_requests, search_commits, search_users
• Repos: create_repository, fork_repository, list_repository_collaborators, list_branches / create_branch, list_tags / get_tag, list_commits / get_commit
• Files: get_file_contents, create_or_update_file, delete_file, push_files
• Releases: list_releases, get_latest_release, get_release_by_tag
• Issues: list_issues, issue_read, issue_write, sub_issue_write, add_issue_comment, get_label, list_issue_types / list_issue_fields, get_teams / get_team_members
• Pull requests: list_pull_requests, pull_request_read, create_pull_request, update_pull_request, update_pull_request_branch, merge_pull_request, pull_request_review_write, add_comment_to_pending_review, add_reply_to_pull_request_comment, request_copilot_review
• Other: get_me, run_secret_scanning

> Model-facing names all carry the mcp__github__ prefix.

Minimal presets

This plugin registers its tools globally, so every preset inherits the GitHub tools — including minimal presets. To opt a preset out, filter them from each system-prompt assembly. Note: DSH's built-in minimal preset cannot mask global plugins; create your own custom minimal preset instead.

> Filter at system-prompt/assemble rather than snapshotting ctx.tools.schemas() at apply time: the plugin registers its tools asynchronously (MCP discovery plus a ctx.effect registration), so a one-time snapshot is empty at apply time and no restriction gets installed. Assembly-time filtering is registration-time independent — whatever registered before the request is filtered out.

// restrict-github.js
const name = 'restrict-github';
const inject = ['tools'];

function apply(ctx) {
  ctx.on('system-prompt/assemble', async (_assembly, _context, next) => {
    const assembled = await next();
    try {
      const tools = assembled && Array.isArray(assembled.tools) ? assembled.tools : [];
      const filtered = tools.filter((tool) => {
        const toolName = tool && typeof tool.name === 'string' ? tool.name : '';
        return !(toolName.startsWith('mcp__github__') || toolName === 'github_file_read');
      });
      if (filtered.length === tools.length) return assembled;
      return { ...assembled, tools: filtered };
    } catch (error) {
      // A filter bug must never brick a session: keep every tool.
      return assembled;
    }
  });
}

export { apply, inject, name };

# in that preset's agent.cordis.yml
- id: restrict-github
  name: ./restrict-github.js