
Gnu Global Cpp Vscode Config Pack
io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.2Updated Oct 24, 2026
21 rules that read the values in a shared .vscode folder, plus 45 snippets. VS Code loads a wrong va
Overview
A local stdio MCP package that supplies VS Code configuration rules and snippets for GNU Global C++ projects, reading values from a shared .vscode folder.
- What you can do
- Provides 21 rules that read values from a shared .vscode folder, plus 45 snippets, for GNU Global C++ setups in VS Code. The registry description also mentions VS Code loading a wrong value, suggesting the rules help keep editor configuration consistent. No tools are listed in the manifest, so the package appears to contribute configuration and snippet content rather than callable actions. The README is titled readystack-themes and describes VS Code themes by ReadyStack, which does not clearly match the C++ configuration purpose.
- When to use it
- Worth considering if you maintain a GNU Global C++ project in VS Code and want shared .vscode configuration rules and snippets kept consistent across a team. Less relevant if you need an assistant to perform actions rather than supply editor configuration content.
- Requirements
- Runs as a local process over stdio, installed with npx from the npm package @readystack/gnu-global-cpp-vscode-config-pack. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Gnu Global Cpp Vscode Config Pack in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
2- v0.1.2LatestSep 19, 2026
- v0.1.1Sep 18, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.