mcp-server-creator
Use PROACTIVELY when creating Model Context Protocol servers for connecting AI applications to external data sources, tools, and workflows. Generates production-ready MCP servers with TypeScript/Python SDKs, configuration templates, and Claude Desktop integration. Includes testing workflow with MCP Inspector. Not for modifying existing MCP servers or non-MCP integrations.
What this skill does
# MCP Server Creator ## Overview This skill automates the creation of Model Context Protocol (MCP) servers—the standardized way to connect AI applications to external data sources, tools, and workflows. **Key Capabilities**: - Interactive requirements gathering and language selection - Project scaffolding with SDK integration (TypeScript/Python) - Server implementation with tools, resources, and prompts - Claude Desktop configuration generation - Testing workflow with MCP Inspector ## When to Use This Skill **Trigger Phrases**: - "create an MCP server for [purpose]" - "build a Model Context Protocol server" - "set up MCP integration with [data source]" - "generate MCP server to expose [tools/data]" **Use Cases**: - Exposing custom data sources to AI applications - Creating tools for AI models to call - Building enterprise integrations for Claude **NOT for**: - Consuming existing MCP servers (this creates new ones) - Non-AI integrations (use REST APIs instead) - Simple file operations (use built-in tools) ## Response Style - **Interactive**: Ask clarifying questions about purpose and capabilities - **Educational**: Explain MCP concepts and best practices - **Language-aware**: Support TypeScript and Python SDKs - **Production-ready**: Generate complete, tested configurations ## Quick Decision Matrix | User Request | Action | Reference | |--------------|--------|-----------| | "create MCP server" | Full workflow | Start at Phase 1 | | "TypeScript MCP setup" | Skip to Phase 2 | `workflow/phase-2-structure.md` | | "add tools to MCP server" | Implementation | `workflow/phase-3-implementation.md` | | "configure Claude Desktop" | Integration | `workflow/phase-5-integration.md` | | "test MCP server" | Validation | `workflow/phase-6-testing.md` | ## Workflow Overview ### Phase 1: Discovery & Language Selection Understand server purpose, target AI app, and choose SDK. → **Details**: `workflow/phase-1-discovery.md` ### Phase 2: Project Structure Generation Create project with dependencies and configuration. → **Details**: `workflow/phase-2-structure.md` ### Phase 3: Server Implementation Generate core server code with tools/resources/prompts. → **Details**: `workflow/phase-3-implementation.md` ### Phase 4: Environment & Security Configure secrets and security best practices. → **Details**: `workflow/phase-4-security.md` ### Phase 5: Claude Desktop Integration Generate configuration for immediate use. → **Details**: `workflow/phase-5-integration.md` ### Phase 6: Testing & Validation Verify with MCP Inspector and Claude Desktop. → **Details**: `workflow/phase-6-testing.md` ### Phase 7: Documentation & Handoff Provide README and next steps. → **Details**: `workflow/phase-7-documentation.md` ## Important Reminders 1. **STDIO = No stdout logging** - Use console.error or stderr only 2. **Build before test** - TypeScript requires `npm run build` 3. **Absolute paths only** - Claude Desktop config needs full paths 4. **Complete restart required** - Quit Claude Desktop entirely (Cmd+Q) 5. **Schemas matter** - AI uses descriptions to decide when to call tools 6. **Security first** - Never commit secrets, validate all inputs 7. **Test incrementally** - MCP Inspector before Claude integration ## Limitations - Only TypeScript and Python SDKs fully supported - HTTP transport requires additional security setup - Claude Desktop must be restarted for config changes - Cannot modify existing MCP servers (creates new ones only) ## Reference Materials | Resource | Purpose | |----------|---------| | `workflow/*.md` | Detailed phase instructions | | `reference/capabilities.md` | Tools, resources, prompts deep-dive | | `reference/troubleshooting.md` | Common issues and debugging | | `reference/language-guides/*.md` | TypeScript and Python best practices | ## Success Criteria - [ ] Project structure created with dependencies - [ ] Server implements requested capabilities - [ ] All tools have proper schemas and descriptions - [ ] Logging configured correctly (no stdout for STDIO) - [ ] Environment variables configured securely - [ ] Claude Desktop config generated with absolute paths - [ ] MCP Inspector testing passes - [ ] Server appears in Claude Desktop after restart
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.