mcp-server-code-assist
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 |
|---|---|
| list_directoryC | Lists directory contents using system ls/dir command |
| create_directoryD | Creates a new directory |
| create_fileC | Creates a new file with content |
| delete_fileC | Deletes a file |
| modify_fileC | Modifies parts of a file using string replacements |
| rewrite_fileC | Rewrites entire file content |
| read_fileC | Reads file content |
| file_treeC | Lists directory tree structure with git tracking support |
| git_statusC | Shows git repository status |
| git_diffD | Shows git diff |
| git_logC | Shows git commit history |
| git_showC | Shows git commit details |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| git-advanced | Handle advanced git operations with verification |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, create_file vs. modify_file vs. rewrite_file handle different file operations, while git tools target specific git commands. The descriptions make it easy to tell tools apart.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is predictable and readable, such as create_directory, list_directory, git_status, and modify_file, with no deviations in style.
With 12 tools, the count is well-scoped for code assistance, covering file operations and git commands. Each tool earns its place without feeling excessive or thin, aligning with the server's purpose.
The tool surface is nearly complete for code assistance, covering file CRUD and key git operations. Minor gaps exist, such as no git commit or branch management tools, but agents can work around this with the provided tools.