Okffs MCP Server

okffs

Turn a conversation with Claude into GitHub issues, branches, and pull requests — without leaving Claude Code.

okffs is a Model Context Protocol server that gives Claude Code a clean issue → branch → PR → close workflow on GitHub. Talk through the work in plain language; okffs creates the issues, matching branches, and pull requests, keeps them linked, and (optionally) syncs a GitHub Projects board — all in one shot.

• One-shot planning — describe a chunk of work and get every issue + branch created, with relationships wired up.
• The whole loop — create, comment, commit, open PRs, handle review feedback, and close, each as a simple ask.
• Sensible defaults — Claude infers labels, priority, and effort from the task; GitHub stays the single source of truth.
• Little to no config — signed in with the gh CLI inside your repo? You're ready.

Quick start

1. Run the setup wizard from your project root:

npx @neturely/okffs setup

It walks you through auth, repo, and any optional features, writes a .env, then runs a quick GitHub sanity check. Re-run it any time (e.g. after upgrading okffs) — it only asks about options that are new since your last run. If you're happy relying on the GitHub CLI (gh auth login) and working inside the repo you want to manage, you can skip this step entirely — okffs works with no config at all.

Already in Claude Code? Once okffs is connected you can configure it conversationally instead — run the /okffs:setup slash command and Claude will interview you and write the .env for you (no terminal needed). okffs also nudges you to run it after an upgrade introduces new options.

2. Add a .mcp.json to your project root:

{
  "mcpServers": {
    "okffs": {
      "command": "npx",
      "args": ["@neturely/okffs@latest"]
    }
  }
}

That's it — npx fetches okffs on first use, and Claude Code picks up the tools automatically. To use a token or a different repo instead of the gh/auto-detect defaults, run okffs setup (above) or edit .env by hand — see Configuration.

Now just ask Claude:

• "Create an issue called 'Fix login button' and start a branch for it."
• "Plan the work for adding user authentication and create the issues."
• "Create issues from this task list: …"
• "List all open issues."
• "Mark issue #5 as blocked by issue #3."
• "Done with issue #42 — open a PR and close it."
• "Address the review comments on PR #42."

Claude infers labels (bug, enhancement, …) from the title and description and merges them with any you've set as defaults.

Tools

Destructive tools (delete_issue, delete_branch) always warn on the first call and only act when re-called with confirmed: true, posting a comment to the issue before doing anything.

Handling PR reviews

okffs has a built-in loop for review feedback — just ask ("address the review comments on PR #42"). Claude reads the threads, fixes the valid ones, commits and pushes, replies per thread, and posts a summary. Claude brings the judgment and the fixes; okffs handles the GitHub plumbing. There's also a slash command, /okffs:address_pr_review (takes a PR number), that runs the same loop.

By default review threads are left open for you to resolve; set OKFFS_RESOLVE_THREADS=true to have okffs resolve them once addressed.

Autopilot (minimum interference)

For a hands-off session, ask Claude to "fully handle this" (or "minimum interference") — or set OKFFS_AUTOPILOT=true to make it the default. In autopilot, Claude stops asking you to choose between options for reversible decisions, takes the recommended option at each fork, and drives an issue all the way to a PR into the base branch (and a base merge when OKFFS_AUTO_MERGE_BASE=true) — then posts an "Autopilot decisions" report (one line per choice, with a one-line why) to the PR and the issue, so you can redirect anything in a single message.

It removes confirmation friction; it does not grant new powers. The hard stops always interrupt, even in autopilot: destructive tools (delete_issue / delete_branch), and anything into OKFFS_PROTECTED_BRANCH (merge/tag/publish), billable, or irreversible that you have not opted into. An explicit env opt-in is the consent and is never re-asked: OKFFS_PROMOTION_AUTO_REVIEW (the Copilot review is your own GitHub billing choice), OKFFS_AUTO_MERGE_PROTECTED, OKFFS_TAG_RELEASE. Correctness stops — a failing check, a pending review, an unresolved thread, a moved branch tip — are never overridden by a flag. And for a real missing-information call — where only you hold the context — Claude still asks one quick question rather than guess. Off by default.

Releases and the promotion gate

prepare_release bumps the version and rolls the changelog on a release/X.Y.Z branch into your base branch. promote_branch then opens the issue-less promotion PR (e.g. develop → main), boards it, optionally requests reviewers such as Copilot, and lists the releases the promotion carries. From there, each further step is your call, or an explicit opt-in:

With both flags on, the loop is: promote_branch → review lands → address it → re-run promote_branch merges and tags. okffs still refuses, and tells you why, when a check fails, a requested review is pending, a thread is open, or the target branch moved past the merge commit. A tag usually triggers your CI publish, which cannot be undone — turn these on deliberately.

Keeping CLAUDE.md in sync

The /okffs:update_guidance slash command reviews the changes on the current branch and maintains one okffs-owned section of your CLAUDE.md — ## Project Guidance (okffs usage), delimited by HTML markers — without ever touching your hand-written content. It's guidance curation (tools, env vars, conventions), not a changelog. Set OKFFS_UPDATE_GUIDANCE=true to have create_pull_request nudge Claude to run it at PR time; the command is always available.

Automatic doc updates

With OKFFS_UPDATE_DOCS=true, create_pull_request writes doc updates onto the branch so they land in the PR diff:

• CHANGELOG.md — a per-issue Keep a Changelog fragment under .changes/unreleased/, assembled into CHANGELOG.md at release time by prepare_release. Uniquely-named fragments avoid merge conflicts across parallel branches.
• SECURITY.md — updated when security-related keywords are detected (only if the file exists).

CLAUDE.md, CONTRIBUTING.md, and README.md are intentionally left for you to maintain. Exclude specific files per repo with OKFFS_EXCLUDE_DOCS (valid: CHANGELOG.md, SECURITY.md).

GitHub Projects v2

okffs can keep a Projects v2 board in step with your workflow. It's opt-in with zero overhead when off:

OKFFS_PROJECT_ENABLED=true
OKFFS_PROJECT_ID=PVT_kwHO...     # the board's GraphQL node ID

Once enabled, list_issues shows each issue's column, priority, and effort (ordered by priority); update_project_status moves issues between Backlog, Ready, In Progress, and Review; and create_issue can set priority/effort and an initial column. Done is deliberately left to GitHub's native automation (PR merge / issue close → Done) so two systems never fight over the terminal state.

Priority & Effort work as either a project-native single-select field (any Projects-capable token) or a GitHub org-level Issue Field. Org-level Issue Fields live outside the project and need a classic PAT with admin:org plus OKFFS_CLASSIC_PAT=true — fine-grained PATs can't reach them yet, so okffs skips that path and asks you to set the value in the UI. Claude infers priority/effort per task by default, falling back to the OKFFS_DEFAULT_* values.

Auto-add (OKFFS_PROJECT_AUTO_ADD) is a fallback for boards without GitHub's native "Auto-add to project" workflow — leave it false if your board already auto-adds.

Token permission: Projects v2 is GraphQL-only and needs a Projects-capable token — a fine-grained PAT with Organization → Projects: Read and write, or a classic PAT with the project scope. A single classic token with repo + project + admin:org covers everything, including org-level Issue Fields. Missing permission surfaces a clear [okffs] error naming what's needed.

Multisite (several apps in one repo)

One repository can host several apps — say finance/ and health/ — that share the issue tracker, board, branches and token but need independent versions, changelogs, fragments, tags and release lines. okffs calls this multisite. Off unless you configure it; a flat single-app repo behaves exactly as before.

repo/
├── .env            # shared: token, board, branches, merge methods, OKFFS_APPS=finance,health
├── finance/
│   ├── .env        # OKFFS_APP=finance  (inherits ../.env — a value here wins)
│   ├── package.json  or  VERSION
│   ├── CHANGELOG.md
│   └── .changes/unreleased/
└── health/
    └── …

• Each app directory has its own .env naming the app (OKFFS_APP). It inherits the git-root .env, so shared values live once. Start Claude Code (or okffs) inside the app directory, with a .mcp.json there or okffs registered at user scope, and that session acts as that app.
• OKFFS_APPS in the root .env is the registry — used to validate app names, drive the migration warnings, and let promote_branch name every app's release.
• With an app active: tags are {app}-X.Y.Z (no v), release branches release/{app}-X.Y.Z, the app name is always an issue label and the default branch identifier (42-finance-add-budget-view), and the changelog, fragments and version file live under the app directory. create_issue / plan / create_issues_from_list accept a per-call app override; list_issues shows app: per issue.
• Versioning: package.json if the app has one, else a plain VERSION file that prepare_release creates on the app's first release.
• Root as an app: set OKFFS_APP in the root .env too. Leave it unset and a root session keeps the plain v tag and root changelog.
• Setup: okffs setup at the root asks for OKFFS_APPS and offers to write each app's .env; run inside an app directory it configures just that app. Both make sure .gitignore ignores .env at every depth — an anchored /.env would leave finance/.env committable.

Migrating an existing repo. Only needed when you turn multisite on. Move each app's changelog, .changes/unreleased/ fragments and version file under its directory; okffs warns at startup about pending root fragments no app release would assemble, an OKFFS_APP missing from OKFFS_APPS, and a root session with a registry but no OKFFS_APP. Existing vX.Y.Z tags stay as they are; an app's first release links its tag rather than a compare range. Single-site users need do nothing.

Configuration

The quickest way to configure okffs is the wizard — npx @neturely/okffs setup — which writes and maintains the .env described below for you. The rest of this section documents what it (or you, by hand) can set.

okffs resolves a token and a target repository with fallbacks, so most users need little config.

Token (first match wins):

1. GITHUB_TOKEN in a .env file — either a fine-grained PAT (recommended; least privilege) with Issues, Contents, Pull requests (read/write), Metadata (read), and Administration (read/write) on the repo, or a classic PAT with the repo scope (broader — grants access across all your repos).
2. Otherwise the GitHub CLI token — if you've run gh auth login, it just works.

Repository (first match wins):

1. GITHUB_OWNER / GITHUB_REPO in .env.
2. Otherwise auto-detected from the origin git remote of the directory okffs runs in.

okffs loads .env automatically from that directory — no --env-file flag needed. A minimal explicit .env:

GITHUB_TOKEN=ghp_your_token_here
# Optional — auto-detected from the git origin remote when omitted:
GITHUB_OWNER=your-github-username
GITHUB_REPO=your-repo-name

Optional settings

All optional; unset unless noted. Grouped by concern — the same groups appear in .env.example, a copyable template. (GITHUB_TOKEN / GITHUB_OWNER / GITHUB_REPO are covered under Setup above.)

Branching & pull requests

Issue defaults & inference

PR review

Docs & changelog

GitHub Projects v2 (board)

Branch promotion & releases (promote_branch)

Multisite (several apps in one repo)

Autopilot (minimum interference)

Conventions

• Branches: {issue-number}-{kebab-title-slug} (title truncated to ~5 words), e.g. 42-add-hero-section-to-homepage.
• PRs: titled Close #42 - Add hero section to homepage; the body always includes Closes #42. GitHub auto-closes the issue when the PR merges into the repo's default branch. If OKFFS_BASE_BRANCH points at a non-default branch (e.g. develop), close the issue manually with close_issue — create_pull_request flags this.
• Destructive tools require confirmed: true; bulk-creating tools confirm first.
• GitHub is always the source of truth for issue state — never local.
• Prefer okffs tools over raw git/gh. When an okffs tool covers the action — issues, PRs, comments, review threads (resolve_review_thread / address_pr_review), releases, project status — use it and honour its env toggles (OKFFS_RESOLVE_THREADS, OKFFS_BASE_BRANCH, OKFFS_PROTECTED_BRANCH, …) rather than re-deriving the behaviour. Fall back to raw git/gh only when no okffs tool fits.

Contributing

Bug reports, feature ideas, and PRs are welcome — see CONTRIBUTING.md for development setup, how to add a tool, commit/branch conventions, and publishing. Release notes live in CHANGELOG.md and on the Releases page.

License

MIT