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.
Authorization: Bearer <token>. Create one under Settings → Applications → Generate New Token. The token only grants what its own scopes already allow.claude mcp add --transport http rithub https://rithub.dev/mcp --header "Authorization: Bearer <token>"
Add to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):
{
"mcpServers": {
"rithub": {
"url": "https://rithub.dev/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Add to ~/.codex/config.toml:
[mcp_servers.rithub]
url = "https://rithub.dev/mcp"
headers = { Authorization = "Bearer <token>" }
| Tool | What it does |
|---|---|
list_repos | List repos you can see, or a given owner's repos |
create_repo | Create a new repo under your account |
get_file | Read one file at a branch, tag or commit |
search_code | Grep file contents in a repo at a ref |
list_issues | List a repo's issues |
create_issue | Open an issue |
comment_issue | Comment on an issue or pull request |
list_pull_requests | List a repo's pull requests |
get_pull_request_diff | Read a pull request's unified diff |
create_pull_request | Open a pull request from an existing branch |
create_branch_and_commit_files | Branch and commit one or more files in one call |
merge_pull_request | Merge a pull request |
import_from_github | Migrate a GitHub repo into Rithub, issues and pull requests included |