MCP

Connect any agent to Rithub

rithub.dev

Rithub exposes one Model Context Protocol (MCP) endpoint at https://rithub.dev/mcp. Any MCP-capable coding agent can point at it and read, search, comment on, branch, commit to, open pull requests against, merge, and import repos you can already reach with your own Rithub access token — no per-tool glue code.

Auth is a normal Rithub access token, sent as Authorization: Bearer <token>. Create one under Settings → Applications → Generate New Token. The token only grants what its own scopes already allow.

Claude Code

claude mcp add --transport http rithub https://rithub.dev/mcp --header "Authorization: Bearer <token>"

Cursor

Add to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):

{
  "mcpServers": {
    "rithub": {
      "url": "https://rithub.dev/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Codex

Add to ~/.codex/config.toml:

[mcp_servers.rithub]
url = "https://rithub.dev/mcp"
headers = { Authorization = "Bearer <token>" }

Tools

ToolWhat it does
list_reposList repos you can see, or a given owner's repos
create_repoCreate a new repo under your account
get_fileRead one file at a branch, tag or commit
search_codeGrep file contents in a repo at a ref
list_issuesList a repo's issues
create_issueOpen an issue
comment_issueComment on an issue or pull request
list_pull_requestsList a repo's pull requests
get_pull_request_diffRead a pull request's unified diff
create_pull_requestOpen a pull request from an existing branch
create_branch_and_commit_filesBranch and commit one or more files in one call
merge_pull_requestMerge a pull request
import_from_githubMigrate a GitHub repo into Rithub, issues and pull requests included

Importing a large or wiki-heavy GitHub repo can take a few minutes; Rithub keeps working even if your agent's own request times out first — run list_repos again to check.