GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PROJECT_CONTEXT_CONFIG_DIR, PROJECT_CONTEXT_STATE_DIR, PROJECT_CONTEXT_CWDYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"project-context": {
"command": "npx",
"args": [
"-y",
"@sandovalrr/project-context-mcp"
],
"env": {
"PROJECT_CONTEXT_CONFIG_DIR": "your-value",
"PROJECT_CONTEXT_STATE_DIR": "your-value",
"PROJECT_CONTEXT_CWD": "your-value"
}
}
}
}Run this in your terminal
claude mcp add project-context --env PROJECT_CONTEXT_CONFIG_DIR=your-value --env PROJECT_CONTEXT_STATE_DIR=your-value --env PROJECT_CONTEXT_CWD=your-value -- npx -y @sandovalrr/project-context-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"project-context": {
"command": "npx",
"args": [
"-y",
"@sandovalrr/project-context-mcp"
],
"env": {
"PROJECT_CONTEXT_CONFIG_DIR": "your-value",
"PROJECT_CONTEXT_STATE_DIR": "your-value",
"PROJECT_CONTEXT_CWD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"project-context": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sandovalrr/project-context-mcp"
],
"env": {
"PROJECT_CONTEXT_CONFIG_DIR": "your-value",
"PROJECT_CONTEXT_STATE_DIR": "your-value",
"PROJECT_CONTEXT_CWD": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
PROJECT_CONTEXT_CONFIG_DIR envPROJECT_CONTEXT_STATE_DIR envPROJECT_CONTEXT_CWD envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
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 6, 2026
The registry name was verified with the GitHub account sandovalrr, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
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
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 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 –, and the latest version (0.4.0) reached the registry 4 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: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
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.
project-context is a local, provider-neutral MCP server for repository-scoped issue handling. It gives agents one guarded interface to Linear, GitHub Issues, GitHub Projects v2, and Jira Cloud while keeping project mappings and credentials outside source repositories.
The server resolves the current Git repository, selects its configured issue provider, verifies the authenticated account, and separates every write into a preview and a single-attempt apply step. Pull requests, releases, repository administration, Git authentication, and commit signing are intentionally out of scope.
Requirements: Node.js 22 or newer on Linux or macOS.
VERSION=0.1.0
npx -y --package="@sandovalrr/project-context-mcp@$VERSION" project-context setup npx -y --package="@sandovalrr/project-context-mcp@$VERSION" project-context doctor
The first command creates secure, host-local starter files without overwriting anything that already exists:
~/.agents/config/project-context/projects.yaml
~/.agents/config/project-context/credentials.yaml ~/.agents/config/project-context/templates/ ~/.agents/config/project-context/secrets/ ~/.local/state/project-context/
Copy and adapt the sanitized examples in examples/, validate the result, and then register the project-context-mcp stdio command in your MCP client. The complete Codex, Claude, Zed, and VS Code configurations are in docs/installation.md.
indeterminate and is never replayed automatically.0600, and rotate locally. The project has no telemetry.Read docs/threat-model.md for trust boundaries and residual risks, and docs/routing-and-safety.md for operational behavior.
project-context --help
project-context setup --guided project-context config validate project-context resolve --cwd /path/to/repository project-context issue list --status open --status in_progress project-context issue list --parent linear:ENG-42 project-context issue user search "John Smith" project-context issue capabilities project-context issue option search labels security project-context issue option search cycle current project-context issue get linear:ENG-42 --include-relations project-context issue comment list github:#42 --limit 20 project-context issue prepare create --title "Child task" --parent ENG-42 project-context doctor project-context audit list project-context skill status project-context integration manifest --client codex
The stdio server exposes eleven tools:
resolve_project_contextlist_issuessearch_issueslist_userssearch_userssearch_issue_optionsget_issue_capabilitiesget_issuelist_issue_commentsprepare_issue_changeapply_issue_changeEvery tool has an input and output schema. Starting the server has no setup side effects; when host configuration is absent, tools return an actionable structured error.
Linear additionally supports target-scoped subissues, due dates, estimates, cycles, milestones, blocking/related/duplicate relationships, comment replies and edits, archived listing, and relation-expanded reads. SLA fields, permanent deletion, and non-issue Linear features are not exposed.
GitHub additionally supports repository issue types and milestones, native parent/subissue hierarchies, blocking dependencies, duplicate relationships, comment edits, direct-subissue listing, and relation-expanded reads. GitHub custom-field mappings, generic related-to relationships, threaded comment replies, pull requests, and repository administration are not exposed.
integration manifest prints the provider-neutral command definition by default. Pass --client codex, claude, zed, or vscode to emit native, ready-to-paste configuration pinned to the installed package version. Add --json when automation needs an envelope containing the client, format, and configuration.
The optional project-issues agent skill is packaged but never installed as an npm lifecycle side effect:
project-context skill status
project-context skill install
Use --replace only after reviewing status; replacement creates a timestamped backup.
docs/installation.md: package and MCP client setup.docs/configuration.md: host-local YAML and credential resolvers.docs/architecture.md: components and runtime boundaries.docs/provider-behavior.md: provider-specific behavior.docs/releasing.md: bootstrap, semantic release, npm, and MCP Registry.CONTRIBUTING.md: development and review requirements.SECURITY.md: supported versions and private reporting.This project is available under the MIT License, copyright 2026 Richard Sandoval. The copyright and permission notice must remain with copies or substantial portions of the software.
If this repository is used as the starting point for another project, a visible acknowledgment is appreciated:
Based on project-context, created by Richard Sandoval.