mouse-mcp
Get started with mouse-mcp -- what it is, how to set it up, and how to use it
What this skill does
Guide the user through getting started with **mouse-mcp** (Disney Parks MCP Server).
## About
An MCP server that provides Disney parks data to Claude Code. Returns structured data for attractions (height requirements, Lightning Lane, thrill levels), dining (service type, reservations, character dining), and other park entities. Uses Disney Finder API with ThemeParks.wiki fallback and SQLite caching.
## Prerequisites
Check that the user has the following installed/configured:
- Node.js 20+ (`node --version`)
- No API keys required for basic usage -- data is sourced from public Disney APIs
- Optionally: an OpenAI API key for higher-quality embeddings (otherwise uses local Transformers.js)
## Setup
Walk the user through initial setup:
1. Install dependencies:
```bash
npm install
```
2. Build the TypeScript:
```bash
npm run build
```
3. Optionally copy and configure the environment file:
```bash
cp .env.example .env
```
The defaults work out of the box. Edit `.env` to change log level, database path, or embedding provider.
4. Configure the MCP server in Claude Code. Add to your MCP config:
```json
{
"mcpServers": {
"disney": {
"command": "node",
"args": ["/Users/cameron/Projects/mouse-mcp/dist/index.js"]
}
}
}
```
## First Use
Guide the user through their first interaction with the product:
1. Start in development mode for quick testing:
```bash
npm run dev
```
2. Or connect via Claude Code with the MCP config above and ask:
> "What are the thrill rides at Magic Kingdom?"
Claude will call `disney_attractions` with `destination: "wdw"` and `filters.thrillLevel: "thrill"`.
3. Try a fuzzy entity lookup:
> "Tell me about Space Mountain"
Claude will call `disney_entity` with `name: "Space Mountain"` and return height requirements, Lightning Lane status, thrill level, and more.
4. Use the MCP Inspector for direct tool testing:
```bash
npm run inspector
```
## Key Files
Point the user to the most important files for understanding the project:
- `src/index.ts` -- MCP server entry point and tool registration
- `src/tools/` -- Tool implementations: destinations, attractions, dining, entity, status
- `src/sources/` -- API clients: Disney Finder (primary), ThemeParks.wiki (fallback)
- `src/cache/` -- SQLite caching with FTS5 full-text search
- `.env.example` -- All supported environment variables with defaults
- `package.json` -- Scripts, dependencies, engine requirements
- `Dockerfile` -- Container build
- `docker-compose.yml` -- Docker Compose deployment
## Common Tasks
- **Development mode**: `npm run dev` (auto-reload via tsx watch)
- **Build**: `npm run build`
- **Type check**: `npm run check`
- **Run tests**: `npm test`
- **Full validation**: `npm run validate` (typecheck + lint + format check + tests)
- **Test with MCP Inspector**: `npm run inspector`
- **Run with Docker**: `docker compose up --build`
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.