Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Local-first GitHub contribution research workbench
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
One time only; it works for every server that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"gitcontribute": {
"command": "npx",
"args": [
"-y",
"gitcontribute"
]
}
}
}Use Gitcontribute and tell me what you can do for me, then show me one thing✓ If Claude says it is using Gitcontribute or shows a Gitcontribute tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Gitcontribute yet
Gitcontribute runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Gitcontribute
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user gitcontribute -- npx -y gitcontributeYou should see Gitcontribute listed as connected
Use Gitcontribute and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Gitcontribute or shows a Gitcontribute tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Gitcontribute and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Gitcontribute or shows a Gitcontribute tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
One time only; it works for every server that needs Node.js
Use Gitcontribute and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Gitcontribute or shows a Gitcontribute tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user gitcontribute -- npx -y gitcontributeClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"gitcontribute": {
"command": "npx",
"args": [
"-y",
"gitcontribute"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"gitcontribute": {
"command": "npx",
"args": [
"-y",
"gitcontribute"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"gitcontribute": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gitcontribute"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026
The registry name was verified with the GitHub account morluto, which owns the repo
Code last changed 2 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 months ago, and the latest version (3.0.2) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, OpenSEO
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Contribution research for agents: check repository guidance, related work, code context, and validation before writing a patch.
Quick start · Workflow · CLI · MCP · Safety · Documentation
gitcontribute is available as a CLI, terminal UI, and MCP server for coding agents.
GitHub can show you open issues. It cannot tell you whether an issue is still relevant, already being implemented, appropriate for an outside contributor, or supported by enough evidence to work on safely.
GitContribute collects repository guidance, related issues and pull requests, code context, accepted contribution patterns, and validation results in a local SQLite corpus. Results identify missing or stale coverage.
find work -> understand it -> check competing work -> prove the change -> prepare the handoff
[!IMPORTANT]
GitContribute never writes to GitHub. It prepares local research and drafts
for you to review.
Run the guided setup with Node.js 18 or newer:
npx --yes gitcontribute@latest setup
Choose MCP to use GitContribute from a supported coding agent, CLI for the terminal and TUI, or Both. The wizard shows every planned change before applying it. Adding a repository during setup does not contact GitHub or start a sync.
After setup, start with a repository or an exact issue:
| Task | Coding agent | CLI |
|---|
| Find candidates | Find contribution candidates in owner/repo. Rank them by contribution fit, evidence, scope, and coordination risk. | gitcontribute archive sync owner/repo gitcontribute radar owner/repo --limit 10 | | Research an issue | Investigate owner/repo#42. Check guidance, discussion, code, prior fixes, competing work, and missing evidence. | gitcontribute archive sync owner/repo --numbers 42 gitcontribute research brief issue:owner/repo#42 |
Results include source references, coverage gaps, and suggested next steps.
Other installation options
Install a persistent command:
npm install --global gitcontribute@latest
gitcontribute setup
Pin GitContribute to a project:
npm install --save-dev gitcontribute
npm exec -- gitcontribute setup --mode mcp --codex --token-source none --yes
Build from source with Go 1.26 or newer:
go install github.com/morluto/gitcontribute/cmd/gitcontribute@latest
Native npm binaries are included for macOS ARM64/x64, Linux ARM64/x64, and Windows x64. You also need git. The gh CLI is optional and can provide authentication through gh auth token.
Search a repository or rank its open issues by available evidence, scope, risks, blockers, and signs that maintainer coordination is needed.
Find contribution candidates in golang/go. Exclude issues with active
implementation work and explain why each remaining candidate is worth investigating.
The ranking only covers stored observations. Results report incomplete coverage.
Build a research brief from the issue, repository guidance, discussion, linked work, indexed code, and historical contributions. Extracted maintainer text and checkboxes are not presented as complete acceptance criteria.
Investigate issue owner/repo#42. Summarize the confirmed problem, likely scope,
relevant code, maintainer guidance, and open questions.
Look for duplicate reports, linked pull requests, closing relationships, and semantically overlapping work before investing in an implementation.
Check whether owner/repo#42 has duplicate reports or competing implementation
work. Tell me what you checked and identify any missing coverage.
Incomplete coverage is reported instead of being treated as proof that no competing work exists. In the MCP workflow, follow the returned typed recovery action, poll the durable job, and reread the affected exact thread or repository before drawing that conclusion.
Record a reproduction, test, benchmark, or other validation and compare the unmodified baseline with a candidate. Validation commands run only after explicit approval.
Validate my candidate change against the baseline. Run the approved checks,
record both results, and explain whether the evidence supports the change.
Stored runs include the command, outcome, timing, and available process metrics.
Create a local issue, pull-request, or review draft tied to the research and validation evidence already collected.
Prepare a pull-request draft for this contribution. Tie its claims to the
recorded evidence, include the validation results, and do not post anything.
Draft revisions retain their exact rendered bytes and provenance.
GitContribute stores repositories, threads, code snapshots, investigations, evidence, validation results, and contribution outcomes in SQLite. Network access is explicit; once information has been synced, corpus search and inspection work offline.
GitHub read APIs Local checkout
| | | explicit sync / hydrate | explicit index / acquire v v +------------------------------------------------+ | Local SQLite corpus | | observations · coverage · evidence · outcomes | +------------------------+-----------------------+ | offline reads +---------+---------+ v v CLI / TUI Coding agents
The CLI and MCP server use the same application services and side-effect boundaries.
The CLI exposes the same workflow without requiring an MCP client:
# Sync repository context and current threads
gitcontribute archive sync-context owner/repo gitcontribute archive sync owner/repo
gitcontribute radar owner/repo --limit 10 gitcontribute research brief issue:owner/repo#42
gitcontribute search threads "connection timeout" --repo owner/repo gitcontribute search code "context.WithTimeout" --repo owner/repo
For implementation work:
gitcontribute investigation start-thread issue:owner/repo#42 --json
gitcontribute workspace create gitcontribute validation define --kind=test --command="go test ./..." \ --working-dir=/path/to/workspace gitcontribute validation run --kind=base --execute gitcontribute validation run --kind=candidate --execute gitcontribute validation compare gitcontribute readiness opportunity gitcontribute prepare pr --approach="Bound retries with context" \ --workspace
Run gitcontribute --help or gitcontribute --help for the complete command and flag reference. Most non-interactive commands accept --json; machine-readable output goes to stdout and progress goes to stderr.
Launch the local TUI with:
gitcontribute tui
The MCP server advertises one unified catalog. Hosts such as Codex and Claude Code can discover large MCP catalogs with native tool search, so setup does not ask users to choose permanent capability profiles.
gitcontribute setup --mode mcp --codex --token-source none --yes
gitcontribute setup --mode mcp --all-clients --token-source none --yes
To start the stdio server directly:
gitcontribute mcp serve --transport=stdio
Add --read-only to remove tools that permit network access, local writes, or execution. See MCP catalog and composition for capability boundaries, snapshot recovery, resource handoffs, and common tool sequences.
GitHub users are stored as first-class actors. Live discovery records identity only; profile, social-account, organization, pinned-item, repository, and contribution facts are synchronized independently. See the actor corpus for the data and freshness model.
GitContribute separates corpus reads, GitHub reads, local writes, process execution, and external mutation.
| Operation | Network | Local write | Runs a process | GitHub write |
|---|---|---|---|---|
| Search and inspect stored research | No | No | No | No |
| Record investigations and evidence | No | Yes | No | No |
| Sync or hydrate GitHub context | Yes | Yes | No | No |
| Acquire and index code | Yes | Yes | git only | No |
| Run an explicitly approved validation | No by default | Yes | Yes | No |
See Architecture for the complete boundary definitions.
GitContribute follows platform conventions:
| Platform | Configuration | Data |
|---|---|---|
| Linux | $XDG_CONFIG_HOME/gitcontribute or ~/.config/gitcontribute | $XDG_DATA_HOME/gitcontribute or ~/.local/share/gitcontribute |
| macOS | ~/Library/Application Support/gitcontribute | ~/Library/Application Support/gitcontribute/Data |
| Windows | %APPDATA%\gitcontribute | %LOCALAPPDATA%\gitcontribute\Data |
The default corpus is gitcontribute.db in the data directory. Run gitcontribute metadata or gitcontribute doctor --json to inspect the local setup.
Linux and macOS are the primary development and test targets. Windows builds are tested in CI and use the standard %APPDATA% and %LOCALAPPDATA% locations.
make verify
go run ./cmd/gitcontribute --help
Before changing package boundaries or side effects, read docs/architecture.md. See CONTRIBUTING.md for the repository workflow.