Claude Code MCP Enhanced
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 |
|---|---|
| healthA | Returns health status, version information, and current configuration of the Claude Code MCP server. |
| convert_task_markdownB | Converts markdown task files into Claude Code MCP-compatible JSON format. Returns an array of tasks that can be executed using the claude_code tool. |
| claude_codeA | Claude Code Agent: Your versatile multi-modal assistant for code, file, Git, and terminal operations via Claude CLI. Use • File ops: Create, read, (fuzzy) edit, move, copy, delete, list files, analyze/ocr images, file content analysis └─ e.g., "Create /tmp/log.txt with 'system boot'", "Edit main.py to replace 'debug_mode = True' with 'debug_mode = False'", "List files in /src", "Move a specific section somewhere else" • Code: Generate / analyse / refactor / fix └─ e.g. "Generate Python to parse CSV→JSON", "Find bugs in my_script.py" • Git: Stage ▸ commit ▸ push ▸ tag (any workflow) └─ "Commit '/workspace/src/main.java' with 'feat: user auth' to develop." • Terminal: Run any CLI cmd or open URLs └─ "npm run build", "Open https://developer.mozilla.org" • Web search + summarise content on-the-fly • Multi-step workflows (Version bumps, changelog updates, release tagging, etc.) • GitHub integration Create PRs, check CI status • Confused or stuck on an issue? Ask Claude Code for a second opinion, it might surprise you! • Task Orchestration with "Boomerang" pattern └─ Break down complex tasks into subtasks for Claude Code to execute separately └─ Pass parent task ID and get results back for complex workflows └─ Specify return mode (summary or full) for tailored responses Prompt tips
|
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 3 tools
The three tools have clearly distinct purposes with no overlap: claude_code handles all code/file/Git/terminal operations, convert_task_markdown specifically converts markdown to JSON format, and health provides server status information. Each tool serves a unique function in the workflow.
The naming shows mixed conventions: claude_code uses snake_case but includes the server name, convert_task_markdown uses snake_case with a descriptive verb_noun pattern, and health is a simple noun. While readable, there's inconsistency in structure and verb usage across the set.
Three tools is reasonable for this enhanced code assistant server, though slightly minimal. The claude_code tool is comprehensive, covering multiple domains, while the other two provide essential supporting functions. A few more specialized tools might improve granularity, but the current count works.
The tool surface covers core code assistant workflows well through the comprehensive claude_code tool, with supporting tools for task conversion and health checks. Minor gaps exist in specialized operations like dedicated Git branch management or isolated terminal command execution, but agents can work around these using the versatile claude_code tool.