Code MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_workspaceB | Get current workspace path |
| set_workspaceC | Set the active workspace directory |
| list_workspacesB | List recently used workspaces |
| detect_vscode_workspacesB | Automatically detect open VS Code instances and their workspaces |
| present_workspace_choiceB | Present detected workspaces to user for selection |
| auto_select_workspaceC | Automatically select the most appropriate VS Code workspace |
| smart_workspace_initB | Intelligently initialize workspace with VS Code detection and user choice |
| read_fileB | Read the contents of a file |
| write_fileB | Write content to a file |
| list_directoryC | List contents of a directory with details |
| create_directoryC | Create a new directory |
| delete_fileC | Delete a file or directory |
| move_fileB | Move or rename a file or directory |
| run_pythonC | Execute Python code or script |
| run_javascriptB | Execute JavaScript code or script with Node.js |
| run_commandC | Execute a shell command |
| pip_installC | Install Python packages using pip |
| npm_commandB | Run npm commands (install, test, build, etc) |
| run_testsC | Run tests using appropriate test runner |
| git_statusC | Get git repository status |
| git_diffC | Show git diff |
| git_addB | Stage files for commit |
| git_commitB | Commit staged changes |
| git_pushB | Push commits to remote |
| git_pullC | Pull changes from remote |
| git_branchC | List, create, or switch branches |
| git_logB | Show commit history |
| analyze_codeC | Analyze code structure and dependencies |
| search_codeC | Search for patterns in code |
| create_projectC | Create a new project with boilerplate |
| install_dependenciesC | Install all project dependencies |
| start_serverC | Start a development server |
| stop_serverB | Stop a running server |
| list_processesA | List all running processes started by the agent |
| docker_check_availabilityB | Check if Docker is installed and available |
| docker_buildB | Build a Docker image from a Dockerfile |
| docker_runC | Run a Docker container |
| docker_composeC | Manage Docker Compose services |
| docker_imagesC | Manage Docker images (list, pull, push, remove, etc.) |
| docker_containersB | Manage Docker containers (list, start, stop, remove, etc.) |
| docker_networksC | Manage Docker networks |
| docker_volumesC | Manage Docker volumes |
| docker_systemC | Docker system operations and information |
| generate_dockerfileB | Generate a Dockerfile template for a specific language/framework |
| generate_docker_composeC | Generate a Docker Compose file template |
| docker_cleanupB | Clean up tracked Docker containers and resources |
| load_project_configB | Load project-specific configuration from .vscode-mcp.toml |
| save_project_configB | Save project-specific configuration to .vscode-mcp.toml |
| update_project_configC | Update specific project configuration settings |
| generate_sample_configC | Generate a sample .vscode-mcp.toml configuration file |
| start_coding_sessionB | Start a new AI coding session with automatic change tracking |
| end_coding_sessionA | End the current AI coding session |
| get_session_infoB | Get information about the current coding session |
| rollback_sessionB | Rollback all changes made in the current AI session |
| preview_changesB | Preview all changes before committing |
| auto_commit_changesC | Automatically commit AI-made changes with tracking |
| get_session_historyA | Get history of commits in current session |
| enhanced_git_diffC | Show git diff with multiple format options (unified, side-by-side, stat, word-diff) |
| get_diff_statsB | Get diff statistics (files changed, lines added/removed) |
| compare_commitsC | Compare two commits with detailed analysis |
| preview_changes_enhancedC | Enhanced change preview with multiple format options |
| compare_filesB | Compare two files and show differences with multiple format options |
| analyze_file_differencesC | Analyze differences between two files with detailed statistics |
| apply_patchC | Apply a patch file to the workspace |
| create_patchB | Create a patch file from differences between files or directories |
| find_and_replaceC | Find and replace text across multiple files with preview option |
| secure_run_commandA | Execute a command with security restrictions (only allowed commands) |
| secure_run_command_sequenceC | Execute multiple commands in sequence with security restrictions |
| get_allowed_commandsA | Get list of commands that are allowed to run in this project |
| add_allowed_commandB | Add a command to the project's allowed commands list |
| remove_allowed_commandB | Remove a command from the project's allowed commands list |
| run_custom_toolB | Execute a custom tool defined in project configuration |
| start_coding_sessionB | Start a new coding session for change tracking |
| end_coding_sessionA | End the current coding session |
| get_current_sessionB | Get information about the current coding session |
| get_session_historyA | Get history of all coding sessions and their commits |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 73 tools
Multiple tools have overlapping purposes, causing ambiguity. For example, 'git_diff' and 'enhanced_git_diff' both show git differences, 'preview_changes' and 'preview_changes_enhanced' both preview changes, and 'get_current_session' and 'get_session_info' appear to retrieve the same information. Tools like 'run_command', 'secure_run_command', and 'secure_run_command_sequence' also have unclear boundaries, making it difficult for an agent to choose the right one without trial and error.
Most tools follow a consistent verb_noun or verb_adjective_noun pattern (e.g., 'create_directory', 'analyze_code', 'docker_build'), with clear and descriptive names. However, there are minor deviations, such as 'npm_command' and 'pip_install' using different naming styles, and some redundancy in names like 'git_diff' vs. 'enhanced_git_diff', but overall the naming is readable and predictable.
With 73 tools, the count is excessive for a code-focused server, leading to bloat and potential confusion. Many tools could be consolidated (e.g., multiple Docker tools, redundant git and preview tools) without losing functionality. This large number suggests poor scoping and makes the toolset overwhelming for agents to navigate effectively.
The toolset provides comprehensive coverage for code development, including file operations, git management, Docker containerization, dependency installation, and session tracking. It supports full CRUD/lifecycle operations across these domains, with no obvious gaps. Agents can perform end-to-end workflows from project creation to deployment and cleanup.