Forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint.
MCPpedia last refreshed this data
io.github.CloudCorpRecords/codehost-remote is an MCP server that forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 56/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"codehost-remote": {
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your-token"
},
"args": [
"-y",
"@reneturcios/codehost-remote",
"mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Forward GitHub tools to the hosted GitHub Copilot remote MCP endpoint.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@reneturcios/codehost-remote' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @reneturcios/codehost-remote against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for io.github.CloudCorpRecords/codehost-remote and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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).
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
Every tool is a subcommand taking one JSON argument object:
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.
npx -y @reneturcios/codehost-remote mcp
{
"mcpServers": {
"codehost-remote": {
"command": "npx",
"args": ["-y", "@reneturcios/codehost-remote", "mcp"],
"env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "your-token" }
}
}
}
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.
npm install
npm run build
npm test
Tests run entirely on fake-fetch fixtures, including plain-JSON and SSE upstream bodies; no network is used.
MIT — see LICENSE.