Claude Code MCP
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 |
|---|---|
| bashC | Execute a shell command |
| readFileC | Read a file from the local filesystem |
| listFilesC | Lists files and directories in a given path |
| searchGlobC | Search for files matching a pattern |
| grepC | Search for text in files |
| thinkC | A tool for thinking through complex problems |
| codeReviewC | Review code for bugs, security issues, and best practices |
| editFileC | Create or edit a file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| generalCLI | General CLI prompt for Claude Code |
| codeReview | Prompt for reviewing code |
| prReview | Prompt for reviewing a pull request |
| initCodebase | Initialize a new CLAUDE.md file with codebase documentation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes, such as bash for shell execution, codeReview for analysis, and file operations like editFile, readFile, and listFiles. However, grep and searchGlob could be slightly confusing as both involve searching, though grep targets text content while searchGlob focuses on file patterns, which is clarified in descriptions.
The naming is mixed with camelCase (codeReview, editFile, readFile, listFiles, searchGlob) and lowercase (bash, grep, think), lacking a uniform pattern. While the camelCase tools follow a verbNoun style, the inconsistency in case usage reduces predictability across the set.
With 8 tools, the count is well-scoped for a code and file management server, covering essential operations like execution, review, file handling, and search. Each tool serves a clear purpose without feeling excessive or insufficient for the domain.
The toolset provides strong coverage for code and file workflows, including creation, reading, editing, listing, searching, and review. A minor gap is the lack of a deleteFile tool, which agents might need to work around, but core operations are well-represented.