Code Whisperer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEWHISPERER_API_KEY | No | Your Code Whisperer API key. Get one at jeremyknox.ai/skills-library. If not set, the server runs in unauthenticated mode (dev/testing only). |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | List all available Claude Code skills with their slug, title, category, and description. Use get_skill to fetch the full SKILL.md content for a specific skill. |
| get_skillA | Get the full SKILL.md content for a specific Claude Code skill by slug. Use list_skills to discover available slugs. |
| list_templatesA | List all available CLAUDE.md templates with slug, title, and category. Use get_template to fetch the full template content. |
| get_templateB | Get the full CLAUDE.md template content for a specific project type by slug. |
| list_promptsA | List all available prompt patterns with slug, title, category, and tags. Use get_prompt to fetch the full prompt content. |
| get_promptC | Get the full prompt pattern content by slug. |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity. The 'get_' tools retrieve full content for specific resources, while the 'list_' tools provide overviews of available resources, creating a clean separation between metadata listing and content retrieval.
Tool names follow a perfectly consistent verb_noun pattern throughout. All tools use either 'get_' or 'list_' prefixes followed by plural nouns (prompts, skills, templates), creating a predictable and readable naming convention.
Six tools is well-scoped for a documentation/content retrieval server. Each tool earns its place with three resource types (prompts, skills, templates) each having both list and get operations, creating a complete but not overwhelming surface.
The server provides excellent CRUD-like coverage for its documentation domain with list and get operations for all three resource types. The only minor gap is the absence of create/update/delete operations, but for a read-only documentation server, this is reasonable and agents can work effectively with the provided surface.