Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

3.3.9: MCP config references another user's Python virtualenv

Open Beginner friendly
#97 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
devtools

Research direction

Start by inspecting .mcp.json and the make mcp-doctor setup path mentioned in the report to find where the virtualenv interpreter path is set. Make the configuration use the installing user's virtualenv or be generated for the local machine. Done when a fresh setup no longer references another user's path and make mcp-doctor reports the expected interpreter.

Written by the indexing model from the issue text.

Description

I'm setting up SpliceKit 3.3.9 with Final Cut Pro 12.3.

The modded FCP is running and its bridge is listening, but MCP
wasn't working. Running make mcp-doctor reports:

[ok] venv interpreter: /Users//.venvs/splicekit-mcp/bin/python (Python 3.13.4)
[ok] mcp package: 1.30.0
[warn] .mcp.json command: /Users/briantate/.venvs/splicekit-mcp/bin/python
(expected /Users//.venvs/splicekit-mcp/bin/python)
[ok] FCP bridge listening on 127.0.0.1:9876

Expected:
The MCP configuration should reference the installing user's
virtualenv, or setup should generate a machine-local config.

Actual:
.mcp.json references /Users/briantate/... on my machine.

Correcting the path resolves the MCP connection issue

Dominant language
Objective-C
Stars
185
Forks
34
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elliotttate/SpliceKit

All issues in elliotttate/SpliceKit

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.