ecoclaw-mcp
OfficialServer 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 installed skills — both npm-installed ( |
| run_skillA | Get the full prompt/instructions for a skill so Claude can use it inline. Checks your user-local version first (~/.ecoclaw/skills/), then falls back to the npm-installed version. |
| tune_skillA | Apply plain-language feedback to a skill, permanently modifying how it works for you. This is the homomorphic heart — your feedback gets written into the skill's prompt and saved locally. The original npm version is never touched. Examples: 'always use a more casual tone', 'end every output with a P.S.', 'never mention competitors'. |
| fork_skillA | Create an independent copy of a skill under a new name. Use this when you want a specialized variant (e.g. listing-writer-luxury) while keeping the original unchanged. Both versions appear in list_skills. |
| contributeA | Share a skill improvement back to the community by submitting a GitHub PR to the upstream repo. Shows you the diff first. Uses the gh CLI (installed during EcoFiClaw setup). Completely optional — you choose when and what to share. |
| update_skillsA | Pull the latest npm versions of all installed skills. Skills with local customizations are skipped to protect your tuning — you'll see exactly what was updated and what was preserved. |
| discover_skillsA | Scan the current project and installed npm packages for available skills. Returns structured manifests with id, name, description, triggers, dataSources, byokKeys, and author. Looks in /skills/, node_modules/@gonzih/skills-/skills/, and node_modules/@ecoclaw//skills/. |
| build_skill_contextA | Build an instruction string for agent delegation from a list of skill names. Returns a string like "Make sure to use the following skills: 'arxiv', 'fred-economics'" that can be prepended to an agent task. |
| list_byok_keysA | Scan all discovered skills and report which BYOK API keys are present vs. missing in the current environment. Helps you know what to configure to unlock more skills. |
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 9 tools
Most tools target distinct actions: listing, discovering, running, tuning, forking, updating, contributing, and building context. The main potential confusion is between list_skills and discover_skills, but their descriptions differentiate installed skills from scanned available skills well.
Tool names mostly follow a consistent snake_case verb_noun pattern such as list_skills, run_skill, tune_skill, fork_skill, and update_skills. The exception is 'contribute', which breaks the pattern by being a bare verb without a noun.
Nine tools is a well-scoped set for a skill-management server. Each tool has a clear role in the discover, configure, customize, update, and share workflow, with no obvious bloat or redundancy.
The toolkit covers listing, discovering, running, tuning, forking, updating, contributing, and context-building, but lacks obvious install and delete/uninstall operations. Agents cannot fully manage the skill lifecycle when a user asks to remove or newly install a skill, though most customization workflows are supported.