Codehost Remote

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

Forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint.

VerifiedSTDIODesktop only

Overview

Codehost Remote's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Codehost Remote in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

codehost-remote

codehost-remote gives you the familiar GitHub tool surface — repositories, branches, files, search, issues and pull requests — without a local REST client. Every call is forwarded as a JSON-RPC tools/call to GitHub's hosted remote MCP endpoint at https://api.githubcopilot.com/mcp/, and the hosted answer, whether plain JSON or a streamed SSE response, is what you get back.

That makes it the lightweight option: no GitHub API versioning to track locally, and the hosted service does the work. The trade-off is that you depend on the hosted endpoint's availability and behaviour.

Only a core subset is exposed here: 14 tools. The hosted endpoint actually serves a much larger, dynamic set of toolsets (40+ tools); this package deliberately pins the repos / issues / pull-requests core and never claims the full hosted surface.

Set GITHUB_PERSONAL_ACCESS_TOKEN; it is sent as a Bearer token. GITHUB_REMOTE_MCP_URL overrides the endpoint (useful for testing).

Install

bash
npx @reneturcios/codehost-remote get_issue '{"owner":"octocat","repo":"hello-world","issue_number":1}'docker run -i -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/cloudcorprecords/codehost-remote

CLI

Every tool is a subcommand taking one JSON argument object:

bash
codehost-remote search_repositories '{"query":"mcp language:typescript"}'codehost-remote create_issue '{"owner":"me","repo":"proj","title":"Bug: startup crash"}'codehost-remote --version

Exit codes: 0 success, 1 error, 2 usage error.

MCP server

bash
npx -y @reneturcios/codehost-remote mcp
json
{  "mcpServers": {    "codehost-remote": {      "command": "npx",      "args": ["-y", "@reneturcios/codehost-remote", "mcp"],      "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "your-token" }    }  }}

Tools

create_repository, fork_repository, create_branch, get_file_contents, create_or_update_file, push_files, search_repositories, search_code, list_issues, get_issue, create_issue, add_issue_comment, list_pull_requests, create_pull_request.

A missing token is reported as a tool error naming GITHUB_PERSONAL_ACCESS_TOKEN.

Development

bash
npm installnpm run buildnpm test

Tests run entirely on fake-fetch fixtures, including plain-JSON and SSE upstream bodies; no network is used.

License

MIT — see LICENSE.

Source: README.md at commit feaec91

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts