clawskills-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
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 ClawSkills API integration skill docs. |
| get_skillA | Retrieve a ClawSkills skill doc by name (slug). Optionally specify a section (e.g. 'auth', 'rate-limits', 'recipes') to get just that part. |
| search_skillsA | Search across all skill docs for a query string. Returns matching excerpts with context. Useful when you don't know which skill to fetch. |
| list_playbooksA | List all available ClawSkills workflow playbooks. |
| get_playbookA | Retrieve a ClawSkills workflow playbook by name (slug). |
| search_playbooksA | Search across workflow playbooks for a query string and return matching excerpts with context. |
| search_clawskillsA | Search across both skills and playbooks. For workflow-shaped queries, playbooks are ranked ahead of generic skill matches. |
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 7 tools
Each tool has a clearly distinct purpose: list/get/search for skills, list/get/search for playbooks, plus a combined cross-search. No two tools appear to do the same thing, and the combined search is explicitly differentiated.
All tools follow a consistent verb_noun pattern: list_* for listing, get_* for fetching a single item, search_* for querying. The singular/plural usage is appropriate, and the combined search_clawskills fits the pattern.
With 7 tools, the server is well-scoped for a documentation lookup service. Each tool maps to a clear operation on one of two resource types, and there is no bloat or unnecessary duplication.
For a read-only knowledge base of skills and playbooks, the surface fully covers the core operations: list all, get one (with optional section), and search. No obvious gaps exist for the stated purpose.