claude-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_modelsA | List available models for Red Hat EnMaaS AI Gateway and GCP Vertex AI projects with cost and tier tags. INSTRUCTION: Call this tool FIRST to inspect supported models before generating a command with claude_prompt. Returns real-time models for EnMaaS (free GLM 5.3) and supported canonical Claude models (sonnet, opus, haiku, claude-sonnet-5, claude-opus-4-8) per Vertex AI project. |
| claude_promptA | Build a Claude CLI command with intelligent work-to-model mode defaults, gateway routing, and 3-tier failover cascade. INSTRUCTION: Call claude_models first to discover supported models before calling this tool. Supports Red Hat EnMaaS AI Gateway (free GLM 5.3) and GCP Vertex AI (canonical sonnet, opus, claude-sonnet-5, claude-opus-4-8) with shared-quota bypass and tertiary fallback. Returns JSON { command, cwd, description, block_until_ms } for agent shell execution. |
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 2 tools
The two tools have clearly separate roles: claude_models performs discovery/listing, while claude_prompt constructs a CLI command. The descriptions even encode an explicit call-order dependency (models first, then prompt), leaving no realistic path to misselection.
Both tools follow a consistent 'claude_<noun>' prefix convention, which is predictable and readable. The only minor weakness is that the names are noun-based rather than verb_noun, so 'claude_prompt' alone doesn't immediately convey that it builds a command rather than sends a prompt.
Two tools is a deliberately minimal surface, but each fills a genuine role (discover models, then generate a routed command). It is slightly under the typical 3-15 range, yet not padded with redundant operations.
The pair covers the full intended workflow: discover supported models and emit a JSON command payload for the agent to execute, with gateway/failover logic baked in. Minor gaps exist around validating or introspecting generated commands, but the core lifecycle is closed since execution is intentionally delegated to the shell.