MCP Developer
Jeffallan/claude-skills
Builds and debugs MCP servers and clients in TypeScript or Python, from tool and resource definitions to transport setup and inspector-based protocol checks.
End-to-end workflow for adding, modifying, or debugging VSCode MCP tools in this repo — IPC zod schema and EventMap, bridge service registration, core ToolDefinition and tool constants, MCP/CLI…
Install Vscode MCP Tool Development
$ npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tjx666/vscode-mcp vscode-mcp-tool-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tjx666/vscode-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vscode-mcp-tool-development .claude/skills/vscode-mcp-tool-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vscode-mcp-tool-development" agent skill from https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-development into .claude/skills/vscode-mcp-tool-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-mcp-tool-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tjx666/vscode-mcp vscode-mcp-tool-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tjx666/vscode-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/vscode-mcp-tool-development .agents/skills/vscode-mcp-tool-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vscode-mcp-tool-development" agent skill from https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-development into .agents/skills/vscode-mcp-tool-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-mcp-tool-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tjx666/vscode-mcp vscode-mcp-tool-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tjx666/vscode-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/vscode-mcp-tool-development .cursor/skills/vscode-mcp-tool-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vscode-mcp-tool-development" agent skill from https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-development into .cursor/skills/vscode-mcp-tool-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-mcp-tool-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tjx666/vscode-mcp.git --path .agents/skills/vscode-mcp-tool-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tjx666/vscode-mcp vscode-mcp-tool-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tjx666/vscode-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/vscode-mcp-tool-development .gemini/skills/vscode-mcp-tool-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vscode-mcp-tool-development" agent skill from https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-development into .gemini/skills/vscode-mcp-tool-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-mcp-tool-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tjx666/vscode-mcp vscode-mcp-tool-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tjx666/vscode-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/vscode-mcp-tool-development .github/skills/vscode-mcp-tool-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vscode-mcp-tool-development" agent skill from https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-development into .github/skills/vscode-mcp-tool-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-mcp-tool-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tjx666/vscode-mcp vscode-mcp-tool-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tjx666/vscode-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/vscode-mcp-tool-development .opencode/skills/vscode-mcp-tool-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vscode-mcp-tool-development" agent skill from https://github.com/tjx666/vscode-mcp/tree/main/.agents/skills/vscode-mcp-tool-development into .opencode/skills/vscode-mcp-tool-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vscode-mcp-tool-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vscode-mcp-tool-development- GitHub stars
- 105
- Token cost
- ~1.5k tokens
- SKILL.md length
- 631 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
End-to-end workflow for adding, modifying, or debugging VSCode MCP tools in this repo — IPC zod schema and EventMap, bridge service registration, core ToolDefinition and tool constants, MCP/CLI…
- Works in 6 steps: IPC Contract → Bridge Service → Core Tool → …
- Tasks that involve MCP servers
- SKILL.md covers Golden Path, 1. IPC Contract, 2. Bridge Service and 3. Core Tool, plus 5 more sections
- Calls bun
What it does
Vscode MCP Tool Development is an agent skill from tjx666/vscode-mcp. End-to-end workflow for adding, modifying, or debugging VSCode MCP tools in this repo — IPC zod schema and EventMap, bridge service registration, core ToolDefinition and tool constants, MCP/CLI adapter behavior, workspacepath semantics, CLI flag generation, validation, and regression testing.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering MCP servers. It works with Visual Studio Code, Model Context Protocol, Zod and ESLint. The repository describes itself as: MCP server for Claude Code/VSCode/Cursor/Windsurf to use editor self functionality. ⚡ Get real-time LSP diagnostics, type information, and code navigation for AI coding agents…
When your agent uses it
- Tasks that involve MCP servers
Example prompts
- “/vscode-mcp-tool-development”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- IPC Contract
- Bridge Service
- Core Tool
- CLI Exposure
- Descriptions And Agent Steering
- Validation
What it can do on your machine
Read from SKILL.md and the folder at commit a033081. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vscode MCP Tool Development loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 631 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 631 words (~1,496 tokens).
“Use this when a change touches tool contracts, service behavior, tool output, or adapter exposure under packages/vscode-mcp-{ipc,bridge,core,server,cli}/src/.”
- name
- vscode-mcp-tool-development
Files
Just SKILL.md in .agents/skills/vscode-mcp-tool-development of tjx666/vscode-mcp.
Open the folder on GitHubat commit a033081
Compare with similar skills
Vscode MCP Tool Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vscode MCP Tool Development this skilltjx666/vscode-mcp | 105 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| MCP DeveloperJeffallan/claude-skills | 12k | — | ~1.5k | Automated safety check: Pass | MIT | |
| MCP SDK Auditawdr74100/figwright | 995 | — | ~4.1k | Automated safety check: Pass | MIT | |
| MCP Server Patternsaffaan-m/ECC | 276k | 5 repos | ~1k | Automated safety check: Pass | MIT | |
| MCP Server Patternsaffaan-m/ECC | 276k | 1 repos | ~551 | Automated safety check: Pass | MIT | |
| Typescript MCP Server Generatorgithub/awesome-copilot | 40k | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
MCP SDK Audit
awdr74100/figwright
Upgrade @modelcontextprotocol/server (the MCP TypeScript SDK v2) and prove the wire contract survived.
MCP Server Patterns
affaan-m/ECC
Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP.
MCP Server Patterns
affaan-m/ECC
使用Node/TypeScript SDK构建MCP服务器——工具、资源、提示、Zod验证、stdio与可流式HTTP对比。使用Context7或官方MCP文档获取最新API信息。
- Official
Typescript MCP Server Generator
github/awesome-copilot
Generate a complete MCP server project in TypeScript using the MCP TypeScript SDK v2 (@modelcontextprotocol/server) with tools, resources, and proper configuration
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
More from tjx666/vscode-mcp
Typescript Style
tjx666/vscode-mcp
TypeScript code style and repo conventions for VSCode MCP — inference vs explicit types, ESM import suffixes, zod schema contracts, async VSCode/Node APIs, JSON-safe IPC results, JSDoc for public…
Vscode MCP Architecture
tjx666/vscode-mcp
VSCode MCP Bridge project architecture — current monorepo layout, IPC/EventDispatcher flow, per-workspace socket discovery, MCP/CLI adapters, tool filtering, and VSCode extension services.
Related
Categories
Questions about Vscode MCP Tool Development
What does Vscode MCP Tool Development do?
End-to-end workflow for adding, modifying, or debugging VSCode MCP tools in this repo — IPC zod schema and EventMap, bridge service registration, core ToolDefinition and tool constants, MCP/CLI…. Vscode MCP Tool Development is an agent skill from tjx666/vscode-mcp. End-to-end workflow for adding, modifying, or debugging VSCode MCP tools in this repo — IPC zod schema and EventMap, bridge service registration, core ToolDefinition and tool constants, MCP/CLI adapter behavior, workspacepath semantics, CLI flag generation, validation, and regression testing.
When should I use Vscode MCP Tool Development?
Vscode MCP Tool Development fits situations like: tasks that involve MCP servers.
How do I install Vscode MCP Tool Development in Claude Code?
Run `npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a claude-code`. Or copy the skill folder (.agents/skills/vscode-mcp-tool-development in tjx666/vscode-mcp) into .claude/skills/vscode-mcp-tool-development in your project. Claude Code loads it when a task matches its description.
How do I install Vscode MCP Tool Development in Codex?
Run `npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a codex`. Or copy the skill folder (.agents/skills/vscode-mcp-tool-development in tjx666/vscode-mcp) into .agents/skills/vscode-mcp-tool-development in your project. Codex loads it when a task matches its description.
Can I use Vscode MCP Tool Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tjx666/vscode-mcp --skill vscode-mcp-tool-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vscode-mcp-tool-development, .gemini/skills/vscode-mcp-tool-development, .github/skills/vscode-mcp-tool-development and .opencode/skills/vscode-mcp-tool-development in your project.
What does Vscode MCP Tool Development need to run?
Going by SKILL.md and its folder, Vscode MCP Tool Development needs the command-line tools its instructions call (bun).
Does Vscode MCP Tool Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vscode MCP Tool Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vscode MCP Tool Development use?
Vscode MCP Tool Development has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Vscode MCP Tool Development use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vscode MCP Tool Development?
Skills that share tags, products or a category with Vscode MCP Tool Development: MCP Developer (Jeffallan/claude-skills, 12k stars), MCP SDK Audit (awdr74100/figwright, 995 stars), MCP Server Patterns (affaan-m/ECC, 276k stars) and MCP Server Patterns (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vscode MCP Tool Development?
tjx666 (a GitHub user) maintains it in tjx666/vscode-mcp, which has 105 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on August 6, 2026.
Source: tjx666/vscode-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.