mcpServer.startOnActivate is not working as expected

Open
#594 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
vscode
Domain
tooling

Research direction

Reproduce the issue using the VS Code settings.json entry "mcpServer.startOnActivate": true, then search the project for that setting and the MCP server activation path. Done means reopening VS Code automatically starts the configured MCP Servers, with the behavior covered by an appropriate test if the project provides one.

Written by the indexing model from the issue text.

Description

Hi,

In the VSCode settings.json file, I added the following configuration to autostart MCP Servers:

"mcpServer.startOnActivate": true,

If I close and reopen VSCode, the MCP Servers are never started.

Dominant language
Python
Stars
407
Forks
99
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 microsoft/semanticworkbench

All issues in microsoft/semanticworkbench

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.