Github MCP Server vs Okffs
A side-by-side look at the Github MCP Server and Okffs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Github MCP Server for version control work over a hosted endpoint; choose Okffs for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Github MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GITHUB_OAUTH_CALLBACK_PORT. - You want tools like
get_file_contents, getFileContents.
Choose Okffs when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
create_issue, create_issues_from_list, plan.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 81/100 · Excellent | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | GITHUB_OAUTH_CALLBACK_PORT | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 33,791 | 2 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 23 |
| Full listing | View Github MCP Server | View Okffs |
Tools & capabilities
Github MCP Server tools 2
get_file_contentsgetFileContents
Okffs tools 23
create_issueCreates an issue and a matching branch (an **Epic** gets no branch or draft PR — work lands on its children). Infers labels, a board `priority`/`effort`, and a native Issue Type from the task (toggle with `OKFFS_INFER_PRIORITY`/`OKFFS_INFER_EFFORT`/`OKFFS_INFER_TYPE`). Optional `assignees`, `labels…create_issues_from_listCreates many issues + branches from a task list in one shot. Confirms first. Per-task `labels`, `assignees`, `milestone`, `priority`, `effort`, `type`.planGive it a free-text description plus the breakdown Claude generates (titles, descriptions, labels, priority/effort/type, relationships); it creates every issue + branch, wires up relationships, and opens draft PRs when `OKFFS_AUTO_PR=true`. Confirms first.list_issuesLists open issues with branch, linked PR, board column, `priority:`/`effort:`, native `type:`, and relationships as a tree — ordered by priority so the most important work is on top.get_issueFull details for one issue: title, body, labels, assignees, branch, status.comment_issuePosts a comment — handy for logging what a branch did.link_issuesLinks two issues (`blocked_by`, `blocking`, `parent`), stored under a `## Relationships` section.close_issueCloses an issue and tips you to `/clear` before the next one.create_pull_requestOpens a PR for an issue branch — generates the title/body, pushes the branch, always includes `Closes #N`, and comments back. Can write changelog fragments when `OKFFS_UPDATE_DOCS=true`. Pass `allow_empty: true` to backfill a **draft** tracking PR on a branch with no commits (pushes an empty init c…commit_and_updateStages tracked changes (untracked need `include_untracked: true`), commits (your `message` verbatim, or an auto-generated one), pushes, and posts a progress comment to the issue. Refuses secret-looking files.merge_pull_requestAutonomously merges a green, review-resolved issue PR into the **base** branch (e.g. `develop`) using `OKFFS_BASE_MERGE_METHOD`, then closes the issue. Opt-in (`OKFFS_AUTO_MERGE_BASE=true`) and heavily gated — never touches `OKFFS_PROTECTED_BRANCH`, independently verifies checks/mergeability/thread…fix_into_baseOpens (and, under the same `OKFFS_AUTO_MERGE_BASE` gates, merges) an **issue-less** fix PR into the base branch — for small cleanups such as review-comment fixes. Never targets `OKFFS_PROTECTED_BRANCH`.- +11 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Github MCP Server
{
"mcpServers": {
"github-github-mcp-server": {
"url": "https://api.githubcopilot.com/mcp/"
}
}
}
Okffs
{
"mcpServers": {
"okffs": {
"command": "npx",
"args": [
"-y",
"@neturely/okffs"
]
}
}
}
Frequently asked questions
Github MCP Server is categorized under Version Control and uses a remote HTTP/SSE transport. Okffs belongs to Version Control and uses a local stdio subprocess. Pick Github MCP Server for version control work and Okffs for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Github MCP Server is listed as free. Auth: oauth 2.0. Okffs has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add github-github-mcp-server and okffs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Github MCP Server has a quality signal of 81/100 (Excellent) with 6 views, 0 installs and 33,791 GitHub stars. Okffs has 56/100 (Good) with 1 views, 0 installs and 2 GitHub stars.