Support per-project `mcp.json` files
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
VS Code (and various other clients) can support mcp.json files located in a project directory. This provides per-project MCP server configuration. We should implement some way of supporting this. Tracking projects is easy, but we will need to consider issues such as:
- What is the UX for adding a new project? We can have additional CLI commands or UI views for this, but we may want to explore using IDE plugins to assist the process and make it seamless for developers.
- It seems like different clients expect mcp.json in different paths of the project, e.g.
.vscode/mcp.jsonand.cursor/mcp.json.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are identified. Start by reviewing the existing project-tracking flow and the possible CLI or UI entry points, then compare the expected project paths such as .vscode/mcp.json and .cursor/mcp.json. Done should include a defined user experience and support for the required client-specific configuration locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, vscode
- Domain
- ai, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100