mcpField
C
codehost-port

codehost-port

Local
github.com/CloudCorpRecordsVersion Control0Updated 2w ago
Repository

About codehost-port

codehost-port is an MCP server and CLI for GitHub repository work, using the GitHub REST API for repositories, issues, and pull requests. It provides a core subset of tools from a reference MCP server.

Key features

  1. 01Create repositories, branches, and forks
  2. 02Search repositories and code
  3. 03Read and update files
  4. 04List, create, and comment on issues
  5. 05List and create pull requests

Use cases

  1. 01Create a GitHub repository or branch
  2. 02Search repositories and code
  3. 03Update files in a repository
  4. 04Track issues and add discussion comments
  5. 05Create a pull request

MCP support

It runs as a stdio MCP server and exposes 14 tools for GitHub repositories, code, issues, and pull requests to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-codehost-port": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/codehost-port"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/codehost-port

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/codehost-port0.1.0
ocighcr.io/cloudcorprecords/codehost-port:0.1.0

Tools

14

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
namestringYesThe name of the new repository.
privatebooleanNoWhether the new repository should be private.
autoInitbooleanNoWhether to initialize the new repository with a README file.
descriptionstringNoA description of the new repository.

Details

From the project README

codehost-port

GitHub repositories, issues and pull requests as MCP tools, talking to the GitHub REST API. codehost-port is a clean-room rebuild of the core surface of the GitHub reference MCP server, under a new name: the same tool names and wire behaviour, fresh code, no copied branding.

Tools (core subset, 14)

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.

Pull-request detail/review tools, issue update tools, user search and release tools from the full reference surface are not in this subset.

Setup

Set a GitHub personal access token:

export GITHUB_PERSONAL_ACCESS_TOKEN=ghp_...

Optionally point at GitHub Enterprise with GITHUB_API_URL (default https://api.github.com). Without the token, every tool call fails with an error naming the missing variable.

CLI

npx @reneturcios/codehost-port create_issue '{"owner":"octo","repo":"demo","title":"Bug"}'
npx @reneturcios/codehost-port mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "codehost-port": {
      "command": "npx",
      "args": ["-y", "@reneturcios/codehost-port", "mcp"],
      "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..." }
    }
  }
}

Docker

docker run -i -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/cloudcorprecords/codehost-port

Development

npm install
npm run build
npm test

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.