Project Context

Name: Project Context
Author: sandovalrr

by sandovalrrversion 0.4.0i★ 1iRuns on your computer

Registry nameio.github.sandovalrr/project-context

How to install

What it does

Safely manage repository-scoped issues across Linear, GitHub Issues, and Jira Cloud.

Connects Runs on your computer
Account or key No key needed
Category Developer tools

Install

Pick the AI app you use, then copy the settings.

Passed 2/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

ClaudeWeb · app · phoneChatGPTWebClaude CodeTerminalCursorCode editorVS CodeCode editorOtherOther apps

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

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Project Context for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "project-context": { "command": "npx", "args": [ "-y", "@sandovalrr/project-context-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Project Context tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Open the Claude desktop app’s settings file
SettingsDeveloperEdit Config
Done

Paste these settings and save the file

{
  "mcpServers": {
    "project-context": {
      "command": "npx",
      "args": [
        "-y",
        "@sandovalrr/project-context-mcp"
      ]
    }
  }
}

Done

Quit Claude and open it again
Done
Try it
Use Project Context and tell me what you can do for me, then show me one thing
✓ If Claude says it is using Project Context or shows a Project Context tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

PROJECT_CONTEXT_CONFIG_DIR Optional absolute path to the host-local configuration directory
PROJECT_CONTEXT_STATE_DIR Optional absolute path to the host-local runtime state directory
PROJECT_CONTEXT_CWD Optional repository fallback when the MCP client provides no filesystem root

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Project Context yet

Project Context runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Project Context

Steps for Claude →Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Steps for Claude Code →Install Node.js on your computer first (one time)
Steps for Cursor →Install Node.js on your computer first (one time)
Steps for VS Code →Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Sentry✓ ChatGPT
Compiler Explorer✓ ChatGPT
GitDiagram✓ ChatGPT

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Project Context for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user project-context -- npx -y @sandovalrr/project-context-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Project Context tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Open Terminal
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Done

Paste this command and press Enter

claude mcp add --scope user project-context -- npx -y @sandovalrr/project-context-mcp

Done

Type /mcp in Claude Code
You should see Project Context listed as connected
Done
Try it
Use Project Context and tell me what you can do for me, then show me one thing
✓ If Claude Code says it is using Project Context or shows a Project Context tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

PROJECT_CONTEXT_CONFIG_DIR Optional absolute path to the host-local configuration directory
PROJECT_CONTEXT_STATE_DIR Optional absolute path to the host-local runtime state directory
PROJECT_CONTEXT_CWD Optional repository fallback when the MCP client provides no filesystem root

Descriptions are as written by the maker.

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)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Project Context for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "project-context": { "command": "npx", "args": [ "-y", "@sandovalrr/project-context-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Project Context tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Click this button to open Cursor
Open in Cursor
Cursor asks you to confirm; click Install
Done
Open the AI chat in Cursor in Agent mode
Done
Try it
Use Project Context and tell me what you can do for me, then show me one thing
✓ If Cursor says it is using Project Context or shows a Project Context tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

PROJECT_CONTEXT_CONFIG_DIR Optional absolute path to the host-local configuration directory
PROJECT_CONTEXT_STATE_DIR Optional absolute path to the host-local runtime state directory
PROJECT_CONTEXT_CWD Optional repository fallback when the MCP client provides no filesystem root

Descriptions are as written by the maker.

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)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Project Context for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "project-context": { "type": "stdio", "command": "npx", "args": [ "-y", "@sandovalrr/project-context-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Project Context tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

1
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v
- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Done
Click this button to open VS Code
Open in VS Code
VS Code asks you to confirm; click Install
Done
Open the AI chat in VS Code in Agent mode
Done
Try it
Use Project Context and tell me what you can do for me, then show me one thing
✓ If VS Code says it is using Project Context or shows a Project Context tool in the answer, you are connected

3 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

PROJECT_CONTEXT_CONFIG_DIR Optional absolute path to the host-local configuration directory
PROJECT_CONTEXT_STATE_DIR Optional absolute path to the host-local runtime state directory
PROJECT_CONTEXT_CWD Optional repository fallback when the MCP client provides no filesystem root

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Project Context💬 Discussion →

For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user project-context -- npx -y @sandovalrr/project-context-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "project-context": {
      "command": "npx",
      "args": [
        "-y",
        "@sandovalrr/project-context-mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "project-context": {
      "command": "npx",
      "args": [
        "-y",
        "@sandovalrr/project-context-mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "project-context": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sandovalrr/project-context-mcp"
      ]
    }
  }
}

Values you fill in

PROJECT_CONTEXT_CONFIG_DIR env
Optional absolute path to the host-local configuration directory
PROJECT_CONTEXT_STATE_DIR env
Optional absolute path to the host-local runtime state directory
PROJECT_CONTEXT_CWD env
Optional repository fallback when the MCP client provides no filesystem root

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub stars i: 1
Downloads per weeki: 79/wk
Licence i: MIT
Connection: Runs on your computer
Transport: stdio
Latest versioni: 0.4.0
Categoryi: Developer tools
Published to registryi: Jul 23, 2026
Code last changedi: Oct 10, 2026
Maker: sandovalrr
Packages: npm: @sandovalrr/project-context-mcp
Repo: sandovalrr/project-context
Website: github.com
Registry status: Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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 16, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sandovalrr, which owns the repo
✕ Fail
Still maintained
No code changes for over a year, or the repo is archived
✓ Pass
Has a licence
Uses MIT
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

Not checked yet

What we check → · JSON

Makers: ask for a re-check or report wrong info

Discussion

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.

User reviews

No reviews yet

Compared with others in Developer toolsi

More stars than 69% of the other 5925 servers in this category
Published to the registry more recently than 22% of the other 5925 servers in this category
Basic checks equal to or better than 44% of the other 5925 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Project Context safe?

It passed 2 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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed 37 days ago, and the latest version (0.4.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 18.9KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

How to connect

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

How to connect

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.5KUpdated 14 months ago

Runs in the cloud✓ service owner · mcp.cloudflare.comTried by the PopNx team

How to connect

Omnara

Deploy durable AI agents with Omnara, an open-source managed-agent platform.

by omnara-aiWidely used★ 3.4KUpdated 2 months ago

Runs in the cloud✓ service owner · omnara.com

How to connect

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.1K Stars for the whole repoUpdated 3 days ago

Computer or cloud✓ service owner · repowise.dev

Install

GitDiagram — Runs in the cloud, nothing to install · No key needed
Appllama — Runs in the cloud, nothing to install · No key needed
Cloudflare MCP — Runs in the cloud, nothing to install · No key needed · In Claude’s directory
Omnara — Runs in the cloud, nothing to install · No key needed
Repowise — Cloud or install on your computer · No key needed

README from the maker

Open the README

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

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.

Quick start

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.

Safety model

Host-local YAML determines the repository, provider, target, and expected identity. Missing or ambiguous context fails closed for writes.
Credentials resolve from files, environment variables, OS keychains, or argv-only commands. Literal secrets in YAML are rejected.
Provider calls are restricted to fixed HTTPS origins, reject redirects, cap response sizes and timeouts, and never automatically retry writes.
Linear issue operations use a fixed allowlist of Linear's hosted MCP tools; project-context never proxies the upstream server's broader tool catalog.
Prepared writes expire after ten minutes, are encrypted with AES-256-GCM, and can be claimed only once. An uncertain apply result becomes indeterminate and is never replayed automatically.
Mutation audit records contain metadata only, are mode 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.

Commands and MCP tools

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_context
list_issues
search_issues
list_users
search_users
search_issue_options
get_issue_capabilities
get_issue
list_issue_comments
prepare_issue_change
apply_issue_change

Every 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.

Documentation

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.

License and attribution

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.

Project Context

What it does

Install

Install Node.js (if you don’t have it)

Open the Claude desktop app’s settings file

Paste these settings and save the file

Quit Claude and open it again

Try it

What you can do instead

Install Node.js (if you don’t have it)

Open Terminal

Paste this command and press Enter

Type /mcp in Claude Code

Try it

Install Node.js (if you don’t have it)

Click this button to open Cursor

Open the AI chat in Cursor in Agent mode

Try it

Install Node.js (if you don’t have it)

Click this button to open VS Code

Open the AI chat in VS Code in Agent mode

Try it

Installed on your computer

Values you fill in

At a glance

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Published vulnerabilities (OSV.dev)

Discussion

User reviews

Compared with others in Developer toolsi

Common questions

Similar alternatives

GitDiagram

Appllama

Cloudflare MCP

Omnara

Repowise

README from the maker

project-context

Quick start

Safety model

Commands and MCP tools

Documentation

License and attribution