droid-mode

Access MCP tools with progressive schema disclosure and on-demand hydration.

7|2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/Gitmaxd/droid-mode --skill droid-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: droid-mode
Source: https://github.com/Gitmaxd/droid-mode/tree/main/templates/skills/droid-mode
Command: npx skills add https://github.com/Gitmaxd/droid-mode --skill droid-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a way to access MCP (Model Communication Protocol) tools without loading their schemas into the LLM's context window, thereby saving tokens and improving efficiency.

Core Features & Use Cases

  • Progressive Disclosure: Discover MCP servers and their tools incrementally, reducing initial overhead.
  • On-Demand Schema Hydration: Fetch full tool schemas and type definitions only when needed.
  • Procedural Workflows: Execute multi-tool workflows using JavaScript scripts, enabling complex automation.
  • Token Efficiency: Ideal for MCP servers with many tools, preventing context window bloat.
  • Daemon Mode: Offers persistent MCP connections for reduced latency and improved performance.

Quick Start

Use the droid-mode skill to list available MCP servers by running the command dm servers.

Frequently Asked Questions about droid-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop MCP tool schemas from consuming my LLM context window?

To prevent MCP tool schemas from bloating your LLM context window, you can use progressive disclosure to load schemas on demand. This approach keeps tool definitions outside the context until needed, saving tokens and improving efficiency.

What is the best way to manage multiple MCP servers with large toolsets?

Managing multiple MCP servers with large toolsets is best handled through progressive schema discovery and on-demand hydration. This method fetches tool schemas only when required, preventing context overload while maintaining full access to complex toolsets.

Can I run multi-step MCP workflows without loading schemas into the LLM?

Yes, you can execute multi-step MCP workflows outside the LLM context window using procedural JavaScript scripts. This allows complex multi-tool automation to run efficiently without injecting schema definitions into the model's context.

How do I reduce MCP connection latency for frequent tool calls?

To reduce MCP connection latency for frequent tool calls, enable daemon mode. Daemon mode provides persistent MCP connections, significantly lowering latency and token overhead during continuous tool execution.

Do I need to load all MCP tool schemas before discovering available servers?

No, you do not need to load all MCP tool schemas before discovering servers. You can list available MCP servers using `dm servers` and incrementally discover their tools, fetching full type definitions only when explicitly needed.

Why does accessing MCP tools exhaust my token limit so quickly?

Accessing MCP tools exhausts token limits quickly because loading comprehensive tool schemas directly into the LLM context window consumes massive overhead. Shifting to on-demand schema hydration prevents this context bloat and preserves tokens.